
Be the first to like this
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Scribd will begin operating the SlideShare business on December 1, 2020 As of this date, Scribd will manage your SlideShare account and any content you may have on SlideShare, and Scribd's General Terms of Use and Privacy Policy will apply. If you wish to opt out, please close your SlideShare account. Learn more.
Published on
Citus scales out PostgreSQL through using the extension APIs. To do this, Citus shards and replicates data, performs distributed deadlock detection, and parallelizes queries across a cluster of machines.
This talk describes the distributed systems challenges we faced at Citus and how we addressed them. In particular, we'll talk about three problems we tackled when scaling out Postgres:
 Three strategies to high availability and disaster recovery in Postgres
 Using Postgres' extension framework to route and parallelize queries across a cluster of machines
 The relationship between distributed consistency and locks; and how to resolve distributed deadlocks
Finally, we'll talk about open challenges around scaling out Postgres. We'll then conclude the talk with Q&A.
Be the first to like this
Login to see the comments