[nickstefan12]

I love the idea of citus. An abstraction on top of sharding sounds amazing. The docs are clear. Their learning material is solid and actually gave me plenty of ideas.

I was really excited about citus... until I saw the price! Hosted citus is expensive. The estimator estimated thousands of dollars per month, splitting to just two small Db machines with limited ram and CPU.

For now, just spending all that money on a huge vertically scaled rds box with lots of ram and CPU made way more sense. Hopefully native Postgres eventually ties more parallel ability to take advantage of bigger and bigger rds boxes.

If we scaled past 1 big box, I'm guessing we would just do classical sharding instead.

[ssutch3]

I think a lot of projects would probably be OK with Citus Community: https://www.citusdata.com/product/community (as long as you don't mind being unmanaged)

[craigkerstiens]

Thanks for the candid feedback.

What we've seen is that it's not an apples to apples comparison of single node Postgres to a Citus cluster. Often times customers that migrate over can use less resources because of the sharding and parallelism under the covers than they do on a single node Postgres and get better performance.

Our plans do absolutely start at a higher level than say a really small RDS, but if you have a very small amount of data then that's absolutely the right place to start there is no need to invest in sharding your data at that time. Later when you start to get to larger instances is very much our sweet spot and we have some tools that make migration a smoother process without requiring dump/restore to address the questions that come up there.