- Más nuevo
- Más votos
- Más comentarios
Hi,
Option 3. is probably the way to go if you consider other aspects: Lambda does the "undifferentiating heavyweight lifting" for you (scaling, resiliency, runtime patching, etc.). Additionally, it allow very granular security (per lambda - It is harder to do with any Java AS like Tomcat)
So, you get more time to focus on our application.
Also, Lambda is pure pay-as-you go model: if unused, you don't pay. It would not be the case for Tomcat.
When you get to a high-load steady state, then you may start thinking about going back to a traditional AS-based architecture to optimize your costs via EC2 with FaaS.
Finally, on the number of Lambdas, it is not an issue if you implement from start the right Infra-as-Code tools like CloudFormation or even CDK. CDK will allow you to have a very sophisticated and fully programmatic approach to resource definitions.
Best,
Didier
Hi,
Thanks for your reply. This means that my idea from point 3 is a common approach? Our AWS infrastructure is managed with Terraform Enterprise, so creating the Lambdas is not the problem.
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años