We live in exciting and worrying times. In serverless and containers, we have two amazing technologies that provide productive, machine-agnostic abstractions for engineers to work with. And yet, there seems to be an unbridgeable chasm between the two camps. If you have read anything I wrote in the last two years, you know that I am firmly in the serverless camp. But I was also an early adopter of containers.

In this article, Serverless computing (Functions as a Service), specificallyAWS Lambda for certain jobs is explored to explain the basics and reasoning for why it makes sense to use– with some example use-cases around OpsGenie. But first, let’s talk about the current cloud services available for running software.

Last week I attended ServerlessConf SF. This was the 8th and largest ServerlessConf to date with more than 550 attendees. The conference had an effective agenda with a strong slate of talks and an impressive presence of community thought leaders. Kudos to the ACloudGuru team for organizing the event!

Serverless compute services such as AWS Lambda offer many advantages to their customers, most notably the ability to reduce costs and minimise infrastructure. But serverless can also bring trade-offs that give rise to application performance issues.

Among other terms under the umbrella concept of cloud computing, we can find the Serverless technology which we have witnessed its growing popularity in the last three years. In principle, the cloud computing concept covers three levels of service: IaaS, Paas and SaaS.

Antoni Orfin, Chief Architect at Droplr, has years of hands-on experience building scalable web applications that serve traffic for millions of users across the globe. His journey started with bare-metal infrastructures. Then, he dove deep into cloud. Today, he’s responsible for making things run smoothly on state-of-the-art serverless architecture at Droplr.