AGPL? This is dead in the water :( It will never be integrated into PG. What a shame. It should have been a 2 clause BSDL. Sigh.
Citus Unforks from PostgreSQL, Goes Open Source
31–40 of 156 posts
Re: Citus Unforks from PostgreSQL, Goes Open Source
#32This 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.
nit: Postgres doesn't scale horizontally, it only scales vertically.
Re: Citus Unforks from PostgreSQL, Goes Open Source
#33Earlier quoted context omitted.
We've been running CitusDB for a couple years now at CloudFlare for serving aggregated analytics to customers (cf. https://blog.cloudflare.com/scaling-out-postgresql-for-cloud... ). 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. :-)
Are there any limitations you have run into? E.g. can you still use all index types that Postgres offers or are there any special distributed index types that CitusDB adds perhaps?
My recollection from the last time I played with it, some bits from core postgres are unsupported; things like sequences and recursive CTEs. Maybe all CTEs?
Re: Citus Unforks from PostgreSQL, Goes Open Source
#34Unforking is a very smart decision. Postgres also has gained a lot of favour since MySQL was bought by Oracle. Altogether Citus has earned a lot of kudos for that move, at least with me, for all that may count!
Re: Citus Unforks from PostgreSQL, Goes Open Source
#35Earlier quoted context omitted.
No, it means if you make changes to the code and use it over a network you have to be AGPL too (think "network" as "distribution" in the GPL sense).
Nope. https://www.devever.net/~hl/agplunenforceable
This is a really bad argument, probably wouldn't stand up in court, and in any case doesn't have precedent.
Hint: How did you (the developer) originally acquire a _copy_ of the AGPL'd sourcecode?
Re: Citus Unforks from PostgreSQL, Goes Open Source
#36If anyone from Citus is reading this: how does this affect your business model? I remember when I asked at Strata conf a couple of years ago why isn't your stuff Open Source, the answer then was "because revenue". So what changed since then?
My hunch is that the two are not really related. Companies of any appreciable size will be happy to pay for support if they choose to make Citus a part of their critical infrastructure. And the industry reached an inflection point where there are enough companies want as much of their infrastructure to be open source as possible, that you can run a company where most of your stuff is open source, while still making a…
I know Red Hat is making a ton of money. But, CoreOS and Docker, are they at the "making a ton of money" stage, or merely well-funded by investors?
Re: Citus Unforks from PostgreSQL, Goes Open Source
#37I want it to be called citrus, which is what I always read it as....
Re: Citus Unforks from PostgreSQL, Goes Open Source
#38So this sounds similar to Pivotal's Greenplum which is also open source, can anyone compare the two?
Re: Citus Unforks from PostgreSQL, Goes Open Source
#39AGPL? This is dead in the water :( It will never be integrated into PG. What a shame. It should have been a 2 clause BSDL. Sigh.
might be intentional
Re: Citus Unforks from PostgreSQL, Goes Open Source
#40Earlier quoted context omitted.
Nope. https://www.devever.net/~hl/agplunenforceable
This is a really bad argument, probably wouldn't stand up in court, and in any case doesn't have precedent. Hint: How did you (the developer) originally acquire a _copy_ of the AGPL'd sourcecode?
Not only that: running the app requires copying it into memory; editing files requires making copies; deploying it to your production servers requires making copies.