3 ms·
A) Postgres easily scales to billions of rows without breaking a sweat. After that shard. It’s definitely negotiable.
by scosman 2y ago
A) Postgres easily scales to billions of rows without breaking a sweat. After that shard. It’s definitely negotiable.
- threeseed 2y agoSo does a text file. Statements like yours are meaningless when you aren't specific about the operations, schema, access patterns etc. If you have a single server, relational use case then PostgreSQL is great. But like all technology it's not great at everything.
- scosman 2y agoThe use a text file. In all seriousness, calling Postgres’ scalability “not-negotiable for most use cases” is wild.
- threeseed 2y agoWhat's wild is you misrepresenting what I said which was: "built-in, supported, proven scalability and high availability" PostgreSQL does not have any of this. It's only good for a single server instance which isn't really enough in a cloud world where instances are largely ephemeral.
- tristan957 2y agoDo you mean ephemeral clients or Postgres servers?
- g8oz 2y agoIf multiple nodes are needed, then why MongoDB and not a Postgres compatible distributed product like CockroachDB or YugabyteDB?