+1 on Jelte's sentiment, Marco's blog post about Citus 11 covered much more perspective and shared many more details than in the commit that was shared previously.
347 karma · joined March 21, 2017
+1 on Jelte's sentiment, Marco's blog post about Citus 11 covered much more perspective and shared many more details than in the commit that was shared previously.
+ Implementation of the UK Coronavirus Dashboard running on Citus and Postgres, a post co-authored by the technical lead of the dashboard, Pouria Hadjibagheri: https://www.citusdata.com/blog/2021/12/11/uk-covid-19-dashbo...
+ Architecting petabyte scale analytics using Postgres and Citus, based on an interview with the user, Min Wei: https://www.citusdata.com/blog/2019/12/07/petabyte-scale-ana...
+ Video of a customer talk about scaling a SaaS application on Citus by Jonathan Denney at ConvertFlow: https://youtu.be/PzGNpaGeHE4
Side-note, I had a bit of fun with the pronunciation & spelling challenges of working on Postgres and Citus here: https://twitter.com/clairegiordano/status/150378415161432064...
What we've done is add a Columnar storage feature into the Citus open source extension to Postgres, as part of Citus 10.
One way to think of it: Citus 10 now gives Postgres users (those who are also using the Citus extension) a columnar compression option, for use on a single node and/or a distributed Citus cluster.
When I read this post, I find the HammerDB TPROC-C benchmark results in Figure 1 to be super interesting, too. When you compare Citus 9.4 performance with distributed tables and distributed functions vs. Citus 9.4 with regular Postgres tables and regular Postgres functions (on a single node) -- then the multiplier is an even more impressive ~19X. :)
There's a Citus Public Slack for q&a, and a pretty useful Citus technical newsletter to stay informed (monthly) about what's new.
This is how open source should be done.