3 ms·
> but there are thousands of production PostgreSQL instances out there have solved them Great. Can you provide the details on exactly how they did that. Ensuri
by threeseed 3y ago
> but there are thousands of production PostgreSQL instances out there have solved them
Great. Can you provide the details on exactly how they did that. Ensuring of course that it doesn't rely on anything proprietary e.g. Citus.
Because with every other database I can just go to the officially supported and maintained documentation.
- simonw 3y agoOK, you've attracted my interest. What are some examples of official database documentation pages that do a great job of covering these advanced deployment topics? It's important to note that "boring technology" doesn't mean the official documentation will answer all of your questions: it means that there is enough experience out there in the user community that you can find the information if you go looking for it.
- lmm 3y agoHow is it an "advanced" topic? Having multiple instances so that you don't have a SPOF is table stakes for any service you care about, and something any half-serious datastore like Cassandra, Kafka or even MongoDB (for all of which "clustering, replication and high availability" are boring things that you would naturally set up without making a fuss about it) will do out of the box. I'm constantly baffled that when it comes to RDBMSes people suddenly decide that single points of failure are fine now actually.