What I Talk About When I Talk About Running During one of the September days at 5:20 AM, after tying my shoes and enabling music and fitness app, I started my usual run. After running three kilometers in the city, I turned left and entered the pretty much-deserted road. It is a secondary technical road close to the highway, I like running there in the morning because in the afternoon there are plenty of people on bikes and rollerblades.
I’d like to share a simple and short case study about pragmatic approach to delivering new features to existing, very big software product. Let’s start with some background. There is an existing product, working nicely on production. We want to extend it with new features, fix bugs and experiment in A/B environment. This sounds very typical and I have already been working in such projects more that dozen times. Even though it is so typical and ever-present, I would say that I’ve rarely seen it working well.
On the beginning… I wrote this blog post for myself. Myself from 10 years ago, to be precise. This is a post I wish I could send back in time and show to myself. I’m sure it would change my direction and career. If you have heard about Erlang but are not sure if it is worth giving it a try…or you just love Erlang and would like to hear my praise for it, please read on.
Introduction I assume that almost everyone heard about the Jenkins. Many of you heard about the Kubernetes. In the world of infrastructure as a code in many cases, we set up Jenkins server in an automated fashion. There are plenty of solutions which we can leverage - starting from Jenkins Job Builder, through job-dsl and ending with Jenkins Pipelines. However, here comes a tricky question: how many of you automated Jenkins setup on Kubernetes?
Introduction There is a saying that every single year a couple of small businesses or growing startups are going to die around the same time. The carnage happens close to the end of the November each year. Amazon Web Services organize an event called re:Invent, where they announce significant changes in their ecosystem and platform - including new services and extensions for existing ones. Jokes aside, keeping up with the pace of the changes across the year is incredibly hard.
Introduction and Problem definition If you have worked with containers and AWS for sure you have heard about Amazon Elastic Container Service, called in short ECS. It is a workhorse for your AWS infrastructure, mainly if you use containers and do not use Kubernetes. Operating this service in most cases is an enjoyable experience. However, there is one caveat which you need to be aware. The problem surfaces when you would like to downsize your cluster, but you want to preserve certain machines from being removed.
Today I would like to show you how to build Slack Bot using serverless approach on AWS infrastructure. We are going to support our efforts using AWS Chalice framework. Our Slack Bot is going to be a dummy one. It will respond with a message we send to it. However this article is not about implementing sophisticated bot behavior. We want to setup whole stack which will be a foundation for further development.
Motivation You may have noticed the first part here. If not, it is more or less a business case for serverless computing. I have explained there the what and whys behind serverless, but also talked about the architectural, economic and operational impact that it has on your systems and products. We have left a fascinating question there, wondering if the first word in FaaS acronym (function as a service) means something, for the functional programmers.
Yet another tutorial? Some time ago I’ve been asked to setup authentication for a Spring Boot-based REST application. “Easy-peasy” I said to myself. I’ve been coding in Java for many years. I’ve been using Spring framework since the very early version when you had to love the XML. I took into account all the requirements and proposed a solution with OAuth 2 as an authentication framework. I was happy to start a development.
Motivation Can we use a functional programming language with AWS Lambda? Someone in our team, a year ago It is incredible how a single question can direct you into an exciting place. Journey through that rabbit hole turned out to be a crazy, but excellent chance to build know-how which we can leverage for our clients. Today I do not tell you how much yak-shaving is required to use our beloved functional languages in serverless.