3 ms·
> that you wish you had just gone the monolith route Going from hundreds of lambdas to a monolith is overreacting to one extreme by going the other one. There'
by viraptor 3y ago
> that you wish you had just gone the monolith route
Going from hundreds of lambdas to a monolith is overreacting to one extreme by going the other one. There's a whole spectrum of possible ways to split a project in useful ways, which simplify development and maintenance.
- Spivak 3y agoAnything in between is all the downsides of both approaches. Once you have the flow for deploying always running hot application(s) with autoscaling the benefits of lambda are basically gone. Low volume scale to zero is just another route. No 15 minute limit, no having to marshal data through other AWS services because that's all lambda talks to, no more eventbridge for cron, no more payload size limits and having to use S3 as buffer, no more network requests between different parts of the same logical app, code deploys are atomic you're either at v1.x or v1.x+1 but never some in-between state. I really do like Lambda but once you're at the spend where it's the same as some dedicated always-on compute the value drops off.