Serverless Architecture
What is Serverless Architecture
Serverless do require servers but the servers will be managed by Vendor. We need not worry about the infrastructure and its maintenance. This is a one step forward to PaaS (Platform as a Service) which is called as FaaS (Function as a Service) or BaaS (Backend as a Service).
Pros:
- Cost efficient - The provider charges for resources utilized not for the server instance
- Less time to market
- The focus should be on functionality development, not the infrastructure
Cons:
- Not suited for high-performance computing
- Cryptojacker's paradise
- DoS your self
- Startup latency (cold start)
Major Service Providers:
- AWS Lambda - Node.js, Java, C#, Python and Go
- Google Cloud Functions - Node.js
- IBM OpenWhisk - Node.js, Java, Python, Swift
- Microsoft - Node.js, Java, Python
I think the most important pro is for developers. Developers can now build complex systems very quickly by composing and combining different services together in a loose orchestration and spend most of their time focusing on their core business problem. These serverless systems can scale, grow and evolve without solution architects or developers having to worry about remembering to patch that web server yet again. eg: SLAppForge
ReplyDelete