5 ms·
Right, those are compulsory steps for every upgrade. Yet in the particular case of Citus, history (so far) has shown a) that they update the extension regularl
by ahachete 4y ago
Right, those are compulsory steps for every upgrade.
Yet in the particular case of Citus, history (so far) has shown a) that they update the extension regularly and fast, so by the time you want to upgrade to a newer major version you already have Citus updated too; b) they are going exactly in the opposite direction of "freemium", they actually open sourced even the previous proprietary bits; c) as OSS, it can always be forked and if one day closed source, being such an important project, it would be definitely forked.
(I don't have any stakes on Citus)
- Keyframe 4y agoCitus is Microsoft for quite awhile now. Take what you will from that.
- threeseed 4y agoThe "you can always fork Citus" argument is not workable. Scaling databases is an expert skill that is far out of reach for almost everyone. Far easier just to pick another database that includes HA and horizontal scalability out of the box.
- ahachete 4y agoSharding databases is not such a dark, magic art. Citus relies on Postgres for many key features; and Citus does the rest. It's already quite "feature complete". If Citus would become proprietary overnight, my main concerns of maintaining a fork would be around the codebase and the language expertise more than the sharding concepts. Note that sharding is different from a purely distributed database. The latter is an entirely different class (and more complex system).
- threeseed 4y agoThe more likely scenario is that Citus simply disappears entirely and becomes an internal feature of Azure.