Not just data, but concurrent operations per second for writes and reads involving seperate transactions. Eg: Scaling concurrent write transactions on different shards with minimal write lock contention.
You seem to have missed the final sentence beginning with "Note:" in my original comment. Nobody said you can't do this with postgres.
> Most people don't even get that right. And they're going to suddenly get it right and implement efficient indexes?
What most people get right is not my concern. If you find building a thin wrapper layer for your application as hard, clearly this may not be applicable to you.
Not just data, but concurrent operations per second for writes and reads involving seperate transactions. Eg: Scaling concurrent write transactions on different shards with minimal write lock contention.
> Who actually needs this scale?
Many do including Uber https://www.uber.com/us/en/blog/schemaless-part-one-mysql-da...
> You can just do this with postgres.
You seem to have missed the final sentence beginning with "Note:" in my original comment. Nobody said you can't do this with postgres.
> Most people don't even get that right. And they're going to suddenly get it right and implement efficient indexes?
What most people get right is not my concern. If you find building a thin wrapper layer for your application as hard, clearly this may not be applicable to you.