[1] http://dtrace.org/blogs/bmc/2004/08/28/the-economics-of-soft...
[1] http://dtrace.org/blogs/bmc/2004/08/28/the-economics-of-soft...
a. Proprietary is a non starter, since increasingly large customers will insist on the source being available.
b. Integration / Consulting is no longer viable since the cloud providers will likely offer a hosted / managed solution around a new OSS.
c. Licensing is difficult to enforce if you are giving your code away for free.
Will DBs join file systems and debuggers as pieces of the stack where the only way to build one is to be inside a megaco or as a side project? Am struggling a bit to understand how to monetize infrastructure software going forward. (I have ignored the option of raising $X M to build something and be acquired before shipping to a large customer base).
And you know DBs always need tuning.
https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
Sometimes it's best to start open source.
Open source is a business tool. It's not always the right tool, but in the long run it always is just because if you don't make your software open, then your competition will.
I posted the blogs.oracle.com link to your post -- it's very satisfying that it's still up there.
You still run it in AWS, Azure, Google.
I keep hearing that AWS Lambda has won serverless (Functions as a Service), but as a fellow K8S-bettor who abhors vendor lock-in and follows the news from CNCF friends, I'm not sold on that.
Azure has Brigade, Pivotal (Cloud Foundry) has Riff to compete with that, and I'd guess there are other solutions in the same vein that I haven't heard of; well both of these solutions at least are portable to anywhere you run your Kubernetes clusters.
As long as you don't leverage the other vendor SaaS APIs too heavily and keep as much of your control plane inside of Kubernetes as possible, you can always take the solutions you build there with you anywhere.
Those are open-source solutions built on SaaS platforms, and the fact that things like those exist... is pretty much the only reason I'd consider those platforms? Even potentially say that I'd prefer them over AWS (except that we're an AWS centered shop, where you can also run Kubernetes if it's your fancy, and that we do all of those lock-in things...)
[1]: https://docs.google.com/spreadsheets/d/1LxSqBzjOxfGx3cmtZ4Eb...
https://landscape.cncf.io/grouping=landscape&landscape=insta...