Serverless Architecture Explained
Earlier, software companies and individuals used to buy and manage software and hardware such as data storage, network infrastructure, and servers. These were high responsibilities and required highly skilled teams and individuals for these responsibilities. Then companies started to outsource some of these responsibilities, and cloud technologies came with services such as IaaS, PaaS, and CaaS. These technologies allow companies to do more outsourcing, and it helps to focus more on business logic rather than software and hardware.
In present, we can hear the word serverless very often, which is the next step of evolution. Serverless makes server-side headaches disappear. If I define serverless, it is a native architecture of the cloud that enables you to shift more of the operational responsibilities to someone else (AWS, Google, etc.), increasing our agility, innovation and focus on the important stuff. Simply serverless allows us to build and run applications and services without worrying about servers. We don’t need to worry about infrastructure, scaling, availability, maintenance.
Developers write Lambda functions, which triggered by the client app user’s requests come through the API Gateway. AWS Lambda provides functions as a service.
Pros
Less server-side work, which leads to better creations. Also, it reduced cost because we have to pay as the usage (economy of scale). Reduce risk and increase efficiency. Cloud providers maintain and optimize their services.
Cons
Managing state is relatively complex. We have to use specific architectures for serverless. Another thing is we have to highly depend on the service provider. So it can be a disadvantage too.
There are many advantages of going serverless also a few drawbacks. The world is changing fast. In the future, there will be better technologies. Also, read my article about Serverless Framework. Keep updating your self.
Happy Coding Folks 👽
