(Ozgun, Citus co-founder) That's a good point. Sharding has an interesting trade-off. Early on, you don't need it and there's an overhead to distributing work

(Ozgun, Citus co-founder) That's a good point. Sharding has an interesting trade-off. Early on, you don't need it and there's an overhead to distributing work across multiple machines (you're taking an additional network hop). Later when/if you need it, sharding becomes painful to introduce. You may need to change your data model for performance and move data. For years, I also cautioned against introducing sharding as a premature optimization. Recently, we changed our approach and also introduced sharding on a single VM. I think that offers a pretty good trade-off. If you're interested in this topic, I’d be curious to hear what you think. https://www.citusdata.com/blog/2021/03/20/sharding-postgres-on-a-single-citus-node/ https://www.citusdata.com/blog/2021/03/20/sharding-postgres-...