Will serverless be the future of enterprise application development?

Serverless is currently one of the hot topics out there in software architectural patterns. Like many other terms or trends in software engineering, serverless also doesn’t have a clear definition of what it is. In this post, I’ll walk-through a basic overview of serverless and a few examples around it. Further, this will explore the potential of serverless and discuss on some of the debatable points around serverless.

What is serverless

As per MartinFowler.com,

Serverless architectures refer to applications that significantly depend on third-party services (knows as Backend as a Service or “BaaS”) or on custom code that’s run in ephemeral containers (Function as a Service or “FaaS”)

In simple terms as I see, if you are not maintaining or managing your own infrastructure to run your application and you pay as per your usage (never pay for idle), while getting required level of high availability, scalability and fault tolerance automatically from your vendor, from your point of view you are running a serverless application. As an owner of an application which runs on a serverless environment, you can put your 100% focus on your application business logic without worrying about the infrastructure that it runs on, and other non-functional…