Re:Ask HN: Pain Points of Serverless Architecture
by ufarooqi on Friday December 13, 2019 @11:40AM
(#21783085)
Well there are definitely some advantages of serverless i.e.
- you don't have to create docker images and complex CI/CD pipelines.
- You don't need to worry about deployments (using Heroku, AWS ECS or Kubernetes) and scaling.
- you don't need to write a lot of unnecessary boilerplate code which you do in the case of micro-services.
- You pay per invocation and resources used for that invocation.
But then serverless comes with all the issues which I have described in original post. I think serverless is good for quick prototyping but for production use, we should still be using micro-services. It'd be idea if we can create a new layer of abstraction which has good things of both micro-services and serverless architectures.
- you don't have to create docker images and complex CI/CD pipelines. - You don't need to worry about deployments (using Heroku, AWS ECS or Kubernetes) and scaling. - you don't need to write a lot of unnecessary boilerplate code which you do in the case of micro-services. - You pay per invocation and resources used for that invocation.
But then serverless comes with all the issues which I have described in original post. I think serverless is good for quick prototyping but for production use, we should still be using micro-services. It'd be idea if we can create a new layer of abstraction which has good things of both micro-services and serverless architectures.