4 ms·
We went all in with Dynamo years back for an app because it was exciting. It went fine so we did it again, and again. Over time though (and in some cases not
by freedomben 4y ago
We went all in with Dynamo years back for an app because it was exciting. It went fine so we did it again, and again. Over time though (and in some cases not much time) we quickly realized that we were writing a lot of code to do sanity/safety checks, that was basically just re-implementing relational database features. As we'd hit bugs, we'd add more checking to our app, and eventually we just had a ton of relational DB features at the app level. I've just used postgres ever since.
- lightbendover 4y agoDynamo is almost never something you want to use as a "solution" to an open-ended I-don't-quite-know-my-requirements type of problem (which is almost all holistic problems). Sometimes I feel like it's the only tool anyone knows how to reach for, but it comes with dozens of ways to shoot yourself in the foot one way or another if you're trying to use it generally.
- ngc248 4y agoDynamoDB is amazing when you know all the access patterns for your data and the access patterns are not liable to change much. The performance it gives in such a case is superlative to just about anything else. But if you have changing access patterns and require flexibility in querying, then DynamoDB is not for you.