We’ve both been developers for over 10 years. We started with our first computers in the 90s, developing our first Pascal and BASIC functions and even went to programming competitions. But everything changed when the Web appeared. We immediately started building our first web applications and web pages playing with static HTML and CSS. When JavaScript and jQuery became the new standard, we switched almost immediately (even though, one was still playing with Flash and ActionScript). With the appearance of Node.js, it was natural to switch from languages we used such as Python and C#. Even though we're still sometimes writing a few functions in those languages, our switch to Node.js was permanent.

Approximately three years ago, we turned our attention to serverless. Gojko Adzic introduced AWS Lambda to us with his initial work on Claudia.js as a deployment tool. We were amazed how fast and how easy was it to develop and deploy serverless applications, and how easy was it to scale them, and we began working together with him on creating Claudia Bot Builder.

From one day to another, our whole perspective on building and maintaining web applications completely changed with serverless. Backend services got replaced by serverless functions and instead of writing bash scripts, logging into our servers, and planning our capacity, we stopped caring about those issues and focused more on business logic and application value.

We published our first serverless web applications into production, and developed hundreds of chat bots. Our production increased almost five-fold. It was incredible. The months spent learning how to configure and maintain application servers with bash, ssh, rsync, and so on were no longer important. Everything changed. From our starting point, the serverless ecosystem went a long way -- the serverless providers are easier to use, and there are more and more serverless app components available each year (with Amazon re:Invent).

It went so fast and a huge number of things happened -- we’ve made serverless our career. We started giving talks about serverless, holding workshops, and giving serverless consultations. We tried to gather our experience and knowledge, combined with multiple other sources and bring it together in an easy-to-learn and easy-to-follow format.