41–50 of 103 posts
What are people/companies using currently to make their postgres database distributed these days? Currently running my app + db on Heroku in the EU and would like to scale out since latency is abysmal for users in Australia and Asia.
Earlier quoted context omitted.
there used to be citus but now it's part of microsoft Azure
True, it is developed by Microsoft and available as a service on Azure. It is also open source, actively maintained and improved, and it's a PG13-compatible Postgres extension that adds both distributed database capabilities and columnar storage. :) https://github.com/citusdata/citus (Citus engineer)
So not (IBM-System-)R-compatible, then?
What are the differences between this and YugobyteDB?
What are the differences between this and YugobyteDB?
Looking at their code tree, this is based on 11.2 ( https://www.postgresql.org/docs/11/release-11-2.html ): https://github.com/alibaba/PolarDB-for-PostgreSQL/blob/maste... So this is code from two years ago missing stability fixes from upstream up to 11.12, at short sight.
“high availability through Paxos based replication”. I thought Paxos is supposed to be a CP system.
All you need is that in the event of a failure the clustered system can still recover quickly enough (to a well-defined state!) that the application layer can deal with the transient failure without significant impact on users, maintaining the illusion of availability.
Earlier quoted context omitted.
How do you think the next dominant Database platform will start? Is your expectation that innovation requires polish before hitting the (free open source) “marketplace”?
My expectation is that the next dominant platform will offer something unique which creates enough value that I'm willing to overlook the unfinished parts that deduct value. When Neo4j and other graph databases went big in the past decade, they value they created: "finally! I don't have to faff around with RDBMS tables and Cobb purists to store and query my non-relational object-graph!" - despite the fact that Neo4j…
That’s pretty compelling, if it delivers.
“high availability through Paxos based replication”. I thought Paxos is supposed to be a CP system.
HA isn't really about 100% availability. Any single system that promises such is extremely likely to be misleading you somehow. Your in-flight query is going to get interrupted no matter how fancy your clustering is, and I struggle to even come up with hypothetical use cases where this is something you can't afford to have happen, ever. All you need is that in the event of a failure the clustered system can still rec…
a rocket is using this query to adjust their trusters ;)