Can Open Source and Corporate Interests Merge in the Cloud?
summary
Claims that major open source vendors adopt restrictive licenses and cloud providers ship API‑compatible managed services shape the reality here: AWS launches DocumentDB and Open Distro for Elasticsearch while open source projects pivot away from permissive terms; the company forks its code in 2016 to an open core model for clustering and later builds an entirely new multi‑tenanted, multi‑cloud SaaS platform with closed components; outcome is commercial uptake and hundreds of thousands of InfluxDB servers in the wild but less organic adoption than hoped, so SaaS‑first plus selective open source exhaust becomes the working strategy.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:40Pauls background
- 1:07Open Source Database business model under siege
- 2:33What happened in 2018
- 5:05What happened in 2019
- 5:41Amazon AWS
- 7:50Open Source vs Cloud
- 8:37Open Source Freedom
- 11:16Cloud Vendors Response
- 11:56The Economics of Cloud Vendors
- 12:56My Prediction
- 13:32How It Played Out
- 14:42Less Adoption
- 15:07Hosted Competition
- 15:39The Platform
- 16:31Open Source vs SaaS
- 18:58Cloud Vendors
- 21:52New Open Source Project
- 24:01Competition
- 25:11Elastic and MongoDB
- 26:09Conclusion
related talks
33mHow Cloud is Changing Open Source
10mOpen Source vs Open Core
50mOpen Source as a Business: Strategy, Struggle & Success
42mOpen Source at a Crossroads
15mOpen Core vs Open Source
32mMastering Enterprise Open Source for Cloud and Vendor Independence
25mLicensing Tradeoffs in Open Source Startups
10mThe Future of Open Source