Given these primitives, do you think one solution to the problem is just what we see here, a new licensing structure for some types of open source? Elastic's move here, attacking the issue through licensing, is one way that this sort of business model is becoming more robust over time and would be instructive for other founders looking to create revenue generating software that is also open source.
As a developer, the main reason I _love_ open source is that I help patch issues or inspect the code to get a better understanding. Which is great because the changes Elastic are making to their license are orthogonal to the value prop for your average developer.
Honestly, I think the biggest issue with Elastic-style licenses moving forward is API compatibility. It is just a question of how much money is at stake for a company like Amazon to go from just operationalizing ElasticSearch to running and maintaining an API-compatible fork, just as they've done with Mongo. It would actually be a bit hilarious if Amazon open-sourced said fork with a more permissive license, given that their buck is usually made off of ops.