Earlier quoted context omitted.
I’ll never understand why we collectively wag our fingers at individuals or companies that try to keep the likes of Amazon from building a profitable service off of their hard work then contribute back little-to-nothing. Would redis, mongodb and dgraph have even considered alternate licensing if companies like Amazon had thrown them a minuscule amount of funding and patches? We can’t know because they didn’t. And the…
The bigger concern should be that databases like MongoDB and Redis are part of an older breed. The newest databases, built to handle the most demanding load, like DynamoDB, Aurora, or CloudSpanner, are intimately tied to the cloud providers they're deployed on, for legitimately necessary reasons. As the world gets more complex and demanding, this old model of "I've got a server, lets put a database on it" just doesn'…
The API is very much a part of the product. It's effectively the UI for the service.
Small companies like Mongo and Elastic can't compete on scale but they can compete on interface design.
If it's ok for the giant providers to just take their interface design and rip it wholesale then you are cutting off the market for new database engines.
Aurora and DynamoDB have been around for ages. If it's objectively superior, then why did they feel the need to make a MongoDB compatibility layer?
Because despite being 'superior', people were still using MongoDB.
A database engine is more than just the backend. The developer-facing side is just as important - if not more so.