Citus Blog

If you're looking at Citus its likely you've outgrown a single node database. In most cases your application is no longer performing as you’d like. In cases where your data is still under 100 GB a single Postgres instance will still work well for you, and is a great choice. At levels beyond that Citus can help, but how you model your data has a major impact on how much performance you're able to get out of the system.

At Citus we want to make dealing with large amounts of operational and analytical workloads easier. Data ingestion speed is key, being the necessary first step in working with any new database. Moreover ingestion is something you'll do repeatedly in testing and development so the bulk-loading user experience is important as well. With the release of Citus 5.1 the experience in loading data is much better all around, and we’ve managed to sneak in a few other improvements as well. Read more below or give it a try today.

Product search is a common, yet sometimes challenging use-case for online retailers and marketplaces. It typically involves a combination of full-text search and filtering by attributes which differ for every product category. More complex use-cases may have many sellers that offer the same product, but with a different price and different properties.

When we started working on CitusDB 1.0 four years ago, we envisioned scaling out relational databases. We loved Postgres (and the elephant) and picked it as our underlying database of choice. Our goal was to extend this database to seamlessly shard

With the Citus extension, you can use PostgreSQL to build applications that interactively query large data sets, for example analytical dashboards. At the same time, you can keep adding new data at high rates and use PostgreSQL's powerful indexing...