#tech
You might have heard this term being thrown off quite often in the wild. "Serverless Architecture", "Let's go Serverless" etc etc. What exactly is serverless? Does it mean no servers at all? How would the app be able to serve itself then? Does it mean the maker is serving his app all by himself sitting in his garage?
On the contrary, it actually means the opposite. The "Serverless" aims to represent the loss of control to the servers. The servers are not directly managed by the application developers. All that infrastructure, provisioning, maintaining, scalability of the application is handled by the big cloud providers - who actually have the means and hugely built data center to do that. f
We only have to tell the cloud providers to host this application and the ball's in their court now. Serverless is also based on a pay-as-you-go model. That means you only pay for the services you use. If there's low traffic on your application, you only pay for the amount of services used for the particular time the user was on your website. This makes it an economical option for startups or developers who currently have low traffic but are anticipating scaling their app. It however gets a bit costlier on scale and when there are a million users to manage (image the scale of facebook or google), but there are options to do some cloud cost cutting - that is a discussion for another time.
This is a quick overview of serverless - I hope it helps!