3 ms·
Haven’t used them in production because their license doesn’t allow operating as a service. I have used an alternative.
by rad_gruchalski 4y ago
Haven’t used them in production because their license doesn’t allow operating as a service.
I have used an alternative.
- tluyben2 4y agoWhat does that mean? What service do you have that is disallowed? We are evaluating it and are finding the license page confusing. Yugabyte seems friendlier but it seems even less talked about.
- powerhour 4y agoCockroachdb uses the BSL which means you can't host it as a service for others. It's more of a "source available" license (that eventually converts to Apache, after a few years).
- rad_gruchalski 4y agoI used YugabyteDB. License was one thing: database is Apache 2 licensed and no strings attached, you can operate it as a service yourself. Not so with CockroachDB, what powerhour said. Other reasons: it’s Postgres code under the hood, not a rewrite, so you can use existing extensions. I have even contributed the support for FDWs, which I use in production. More here https://gruchalski.com/tags/yugabytedb/ https://gruchalski.com/tags/yugabytedb/ and here https://github.com/radekg/yugabyte-db-multi-tenant-paas-demo https://github.com/radekg/yugabyte-db-multi-tenant-paas-demo.
- tluyben2 4y agoThank you for that feedback!
- sean0- 4y agoTo be clear, you can use CockroachDB if you're a service. What is prohibited, however, is you can't take CockroachDB and try and offer a hosted CockroachDB-as-a-Service to external organizations. But if your organization has a DB-as-a-Service offering internally, you can totally add crdb to the mix (this is pretty common, as a matter of fact). If your org offers a service and its backed by crdb, you can totally do that, too.