> I’m wondering if Lambdas and DynamoDB would be competitive to this setup.
Depends, but it's important to know the details.
Lambdas are used for 2 things in AWS:
1) Glue for managing services and events. (Required for advanced AWS mgmt.)
2) User applications. Lambdas have improved over time, but initially had all kinds of limitations (startup time, database access, 15 minute job limits, etc.)
DynamoDB has also improved a lot. Initially hot keys could cost you a lot of money. Some companies have designed their applications to use it in a way that absolutely no administration is required, reducing DBAs and Ops people.
Dynamo is great. All new projects I work on that require a db use it. We're slowly moving away from SQL databases entirely. Far more scalable, no more horrible SQL issues, at the cost of not being as flexible. But that's alright in the context of micro-services that do one thing and do it well/fast.
Depends, but it's important to know the details.
Lambdas are used for 2 things in AWS:
1) Glue for managing services and events. (Required for advanced AWS mgmt.)
2) User applications. Lambdas have improved over time, but initially had all kinds of limitations (startup time, database access, 15 minute job limits, etc.)
DynamoDB has also improved a lot. Initially hot keys could cost you a lot of money. Some companies have designed their applications to use it in a way that absolutely no administration is required, reducing DBAs and Ops people.
Source: DBA.