Citus Unforks from PostgreSQL, Goes Open Source
citusdata.com
Citus Unforks from PostgreSQL, Goes Open Source
1–10 of 156 posts
Re: Citus Unforks from PostgreSQL, Goes Open Source
#2Re: Citus Unforks from PostgreSQL, Goes Open Source
#3Re: Citus Unforks from PostgreSQL, Goes Open Source
#4Can you publish competitive positioning of Citus vs Actian Matrix (nee ParAccel) and Vertica? I'd love to compare them side by side - even if it's just from your point of view :-)
Re: Citus Unforks from PostgreSQL, Goes Open Source
#5Re: Citus Unforks from PostgreSQL, Goes Open Source
#6Re: Citus Unforks from PostgreSQL, Goes Open Source
#7My guess is that Citus is making enough money from consulting that they don't need to keep this code closed source when they can profit from free community-driven growth while they are expanding their sales pipeline through consulting.
"for customers with large production deployments, we also offer an enterprise edition that comes with additional functionality"
Re: Citus Unforks from PostgreSQL, Goes Open Source
#8This is fantastic news! Postgres does not have a terribly strong High Availability story so far and of course it also does not scale out vertically. I have looked at CitusDB in the past, but was always put off by its closed-source nature. Opening it up seems like a great move for them and for all Postgres users. I can imagine that a very active open-source community will develop around it.
It's a good product, and it was even fairly easy to do a major version upgrade / cluster relocation. At least as easy as such a thing can be. :-)
Re: Citus Unforks from PostgreSQL, Goes Open Source
#9AGPL license if anyone's curious: https://github.com/citusdata/citus/blob/master/LICENSE
Re: Citus Unforks from PostgreSQL, Goes Open Source
#10> With the release of newly open sourced Citus v5.0, pg_shard's codebase has been merged into Citus...
This is fantastic, sounds like the setup process is much simpler.
I wonder if they have introduced the Active/Active Master solution they were working on? I know before, there is 1 Master and multiple Worker nodes. The solution before was to have a passive backup of the Master.
If say, they released the Active/Active Master later on this year. That's huge. I can pretty much think of my DB solution as done at this point.