A few weeks ago we rolled out Citus 7, a big milestone in our journey to make it so SaaS businesses never have to worry about scaling their database again. Citus 7 includes distributed transactions, savepoints, multi-value inserts, distributed deadlock detection, Rails & Django goodness, and of course Postgres 10 support. Citus 7 is our best yet. Read Ozgun’s Citus 7 post →
Want to see the playbook for migrating from single-node Postgres (like RDS or Heroku Postgres) to a distributed Citus database cluster? Craig Kerstiens shares his best practices on steps to follow as you plan your migration. Read Craig’s migration guide →
With podyn, you can automatically replicate the schema, data, and changes in your DynamoDB tables to Postgres. Once your data is flowing into Postgres, you can start using a wide array of features including views, indexes, rollup tables, and advanced SQL queries. Read Marco’s post on podyn →
At Citus, we love Postgres. So we implemented Citus as an extension to Postgres. Often on our blog we talk about how to use Citus, but this “how it works” post is a bit different: we walk through how Citus shards the data all the way to how the Citus executors run queries. Read Craig’s post on how it works →
During the development of Citus 7, Marco Slot created an FAQ for our engineering team on locks, deadlocks, and distributed deadlocks. It was so useful we decided to share it on the blog. We love tackling tricky distributed systems problems. And sometimes it’s equally fun to share our learnings, too. Enjoy. Read the FAQ →
What are the different approaches to sharding and which type of sharding is right for you? Yes, sharding by customer (or tenant) is on the list. Because we care a lot about SaaS applications that are multi-tenant. Learn more →
Want to talk about Citus or Postgres or whether our brand of scale-out relational database is right for you? Join our slack channel, check out our documentation, or let us know if you want to book a demo.