4 ms·

> The underlying issue here in this one is that people (apparently so far!) want to use AWS/GCP/etc more than they want to use mongo, redis, cockroach, or any p

by btown 7y ago

> The underlying issue here in this one is that people (apparently so far!) want to use AWS/GCP/etc more than they want to use mongo, redis, cockroach, or any particular technology. No license change will fix that. That's a really extreme way to think about this. Consider this example: I lose 1 Utility Point for every new provider I need to contract with, set up monitoring for, set up billing etc. This balloons to losing 2 UP if that provider's in a different public cloud, but since many let you choose an AWS region, this is probably not a problem. I gain 5 UP from using Cockroach, because it saves me engineering time. And I gain 1 additional UP from using latest Cockroach because they're making real optimization breakthroughs. So pre-license-change, AWS Cockroach that tracks the latest release might net 6 UP, and Cockroach Cloud run by the company might only net 5 UP because of that cost of a new provider. But post-license change, Cockroach Cloud would be tied, because now I'm comparing the cost of a new provider against the cost of latest developments. And every single blog post I see about Cockroach developments pushes me in that direction. It's a really great move, though kind of a loss to open source. I wish the Cockroach folks the best.

DannyBee 7y ago
"That's a really extreme way to think about this." I would argue this is probably how most CTO's think about it unless forced at gunpoint to do otherwise.
kelnos 7y ago
There's another angle to it post-license-change: AWS Cockroach continues tracking the latest release and pays a licensing fee for the privilege of doing so. Your costs to use it might go up a tiny amount, but AWS would likely eat most of it, and, bonus: CockroachDB's development gets more funding. It's hard to put a price tag on knowing that an open source project your business depends on is well-funded enough that it's unlikely to disappear or be difficult to support.

by btown 7y ago

DannyBee 7y ago

"That's a really extreme way to think about this." I would argue this is probably how most CTO's think about it unless forced at gunpoint to do otherwise.

kelnos 7y ago

There's another angle to it post-license-change: AWS Cockroach continues tracking the latest release and pays a licensing fee for the privilege of doing so. Your costs to use it might go up a tiny amount, but AWS would likely eat most of it, and, bonus: CockroachDB's development gets more funding. It's hard to put a price tag on knowing that an open source project your business depends on is well-funded enough that it's unlikely to disappear or be difficult to support.