3 ms·
In my experience, NoSQL is almost never the right answer. And DynamoDB is worse than most. My prediction is that the future is in scalable SQL; CockroachDB or
by SomeCallMeTim 5y ago
In my experience, NoSQL is almost never the right answer.
And DynamoDB is worse than most.
My prediction is that the future is in scalable SQL; CockroachDB or Yugabase or similar.
NoSQL actually causes more problems than it solves, in my experience.
- deanCommie 5y agoThere are plenty of reasons when NoSQL is the right answer. The biggest is when you care more about predictable performance: https://brooker.co.za/blog/2022/01/19/predictability.html?s=09 https://brooker.co.za/blog/2022/01/19/predictability.html?s=...
- SomeCallMeTim 5y agoAs long as you consider "can just fail if it gets too busy" to be "predictable." Which I don't. I'd rather see reliable operation than "predictable except for when it fails outright" in almost every situation. If you've encountered that other situation, where failures are fine? Then great. But I still assert that's a tiny minority of real-life DB use cases.