For years we’ve been focused on making Citus the best solution for scaling out your database. We’ve seen customers attain up to 100x performance when compared on the same hardware to vanilla Postgres. Of course you don’t always need to scale out to get good performance–if you have 10 GB of data a single node Postgres can work great. But at data sizes of 100 GB and up, the need to scale out may exist.
Today, with the release of Citus 5.2, it’s now easier to get started earlier so you don’t have to worry about when that moment comes where you won’t be able to scale up further.
It has been several months since the launch of Citus Cloud, and we’d like to share one part of its design with you. In particular, the fundamental unit of organization for our hosted service on top of AWS is concurrent state machines. In what follows...
Whether you’re building marketing analytics, a portal for e-commerce sites, or an application to cater to schools, if you’re building an application and your customer is another business then a multi-tenant approach is the norm. The same code runs for all customers, but each customer sees their own private data set, except in some cases of holistic internal reporting.
Early in your application’s life customer data has a simple structure which evolves organically. Typically all information relates to a central customer/user/tenant table. With a smaller amount of data (10’s of GB) it’s easy to scale the application by throwing more hardware at it, but what happens when you’ve had enough success and data that you have no longer fits in memory on a single box, or you need more concurrency? You scale out, often painfully.
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.
Since Postgres started supporting NoSQL (via hstore, json, and jsonb), the question of when to use Postgres in relational mode vs NoSQL mode has come up a lot. Do you entirely abandon traditional table structures, and go with documents all the way? Or do you intermingle both? The answer unsurprisingly is: it depends. Each newer model including hstore, JSON, and JSONB has their ideal use cases. Here we’ll dig deeper into each and see when you should consider using them.
At Citus we want to enable you to build real-time applications across large amounts of data with ease. One part of that is Citus makes it simple for you to shard your data and use scale-out capabilities to leverage all your processing power. Another part is Citus Cloud: our managed, hosted offering of Citus running on AWS.
Today taking advantage of Citus becomes even easier with Citus Cloud going into general availability. You can read on to discover what’s included with Citus Cloud or sign-up to get started right away.
PG Conf Silicon Valley is happening again this year in November and we’re looking to make it even better and more informative than last year. To do that we’re looking to you, both as an attendee and to come speak. We’ve already received a lot of great...
PostgreSQL is known for its great extensibility and powerful plugins. One particular category of extensions is Foreign Data Wrappers or FDWs. FDWs allow us to interact from within Postgres directly with other data stores such as hdfs, columnar stores, mysql, etc. Combined with Citus’ scalability features, we can even leverage them to help us scale out those data stores where might otherwise be quite difficult.
Page 1 of 8