> Reducing it to an issue of following license terms is short sighted
It's really not: the license terms are the root of the problem you are pointing out. We can either voice our (righteous, but ultimately pointless) anger or we can try to analyze what's happening and how to fix it. So let's do the latter.
Amazon offers a fully managed ElasticSearch service running on the core ES code because ElasticSearch was, up to this point, released under the Apache 2.0 license which fully supports Amazon's right to do this.
Amazon offers a fully managed MongoDB compatible database called DocumentDB. It is not based on MongoDB – Amazon reimplemented the core functionality but maintained the MongoDB API layer.
MongoDB Inc. makes the forceful point that it is not a drop in replacement[1] but a rather crippled product that lags behind what MongoDB can do and continues to diverge. This is likely very good marketing for MongoDB and probably helps their company succeed :)
Why did Amazon do this? Why would Amazon use the core ES code but go through a more difficult reimplementation for Mongo?
Because MongoDB's core was licensed under the terms of the AGPL3, but all the drivers that implemented the API functionality were implemented under terms of the Apache 2.0 license.
It's really not: the license terms are the root of the problem you are pointing out. We can either voice our (righteous, but ultimately pointless) anger or we can try to analyze what's happening and how to fix it. So let's do the latter.
Amazon offers a fully managed ElasticSearch service running on the core ES code because ElasticSearch was, up to this point, released under the Apache 2.0 license which fully supports Amazon's right to do this.
Amazon offers a fully managed MongoDB compatible database called DocumentDB. It is not based on MongoDB – Amazon reimplemented the core functionality but maintained the MongoDB API layer.
MongoDB Inc. makes the forceful point that it is not a drop in replacement[1] but a rather crippled product that lags behind what MongoDB can do and continues to diverge. This is likely very good marketing for MongoDB and probably helps their company succeed :)
Why did Amazon do this? Why would Amazon use the core ES code but go through a more difficult reimplementation for Mongo?
Because MongoDB's core was licensed under the terms of the AGPL3, but all the drivers that implemented the API functionality were implemented under terms of the Apache 2.0 license.
Beginning to see the solution?
[1]: https://www.mongodb.com/atlas-vs-amazon-documentdb