POSETTE 2024 is a wrap! 💯 Thanks for joining the fun! Missed it? Watch all 42 talks online 🍿
POSETTE 2024 is a wrap! 💯 Thanks for joining the fun! Missed it? Watch all 42 talks online 🍿
SaaS apps grow fast, and need to scale while still providing a snappy user experience. Citus shards Postgres transparently at the data layer. And Citus makes it easy to add nodes & rebalance shards. So you can scale out as your app grows, without giving up Postgres.
LEARN MORETime series workloads often need to grow beyond the resources of a single node. Capabilities such as the distributed query engine, columnar compression, parallel query, distributed DML… all combine to make Citus a good fit for time partitioned workloads.
LEARN MORESchema-based sharding allows distributing regular database schemas across many machines. This sharding methodology fits nicely with typical microservices architecture, where each microservice can have its own schema in a shared distributed database.
LEARN MORECitus distributes and parallelizes Postgres workloads—and is often used as a system of record for SaaS apps and microservices, and as a system of engagement for analytics dashboards and time series data. Often, teams use the Citus database for mixed transactional & analytics workloads, to avoid managing multiple different databases. Others use Citus for high-throughput transactional apps. What Citus users have in common: performance really matters to them.
SaaS teams choose Citus to shard Postgres, to avoid the costs of sharding at the application layer. Developers building analytics dashboards tell us that distributed Postgres is a game changer, especially for time series data. Citus is a fit for many types of data-intensive apps, including geospatial analytics with PostGIS—plus video, web, and operational analytics dashboards. And the Citus columnar feature enables you to achieve compression ratios of 3x-10x or more.
Watch Marco’s latest talk, inspired by SIGMOD
Learn how Citus works in this talk about Citus table types, the PostgreSQL extension APIs, the Citus query planner, and performance benchmarks comparing a
Customers ask how many weeks they have to wait for results, but with Citus it takes us roughly three minutes. The difference is so striking compared to our competitors, customers usually struggle to understand how we can do it.
Rasty Turek
@synopsi