Why not have both? That's exactly what DynamoDB offers, and people want the SQL equivalent promise of "it'll keep up no matter what scale you're at". The point

Why not have both? That's exactly what DynamoDB offers, and people want the SQL equivalent promise of "it'll keep up no matter what scale you're at". The point is: You don't want to need to switch technology at a later stage, you'd like to build with the right technology from the get-go. I almost always go for DynamoDB first, since for small projects it's essentially free, and for huge projects I do not have to worry about the ops overhead that follows normal SQL databases. A lot of people also have traffic patterns that go: - Very high volume during the day - Almost no or little volume during the night when your users are sleeping Aurora Serverless v2 gets us closer to this for SQL, but does not scale to 0 so it's not too nice for the initial phases of projects.