You were sold the promise of the cloud. The performance gains were going to make everything better. Costs would go down since you’d only be paying for the resources you were actually using. It sounded magical. You’d look like a star and save your company money. Unfortunately, when all was said and done, the cloud didn’t deliver.

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.

I’ve seen so many new types of infrastructure technologies impact the performance of the modern data center. All-flash technologies help consolidate systems, virtualization helps to deliver powerful workloads to a variety of users, and even convergence has helped remove legacy from the data center. Most of all, these solutions are all coupled with the cloud to really help an organization become agile and much more efficient.

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.