3 ms·
Disclosure: I work at AWS, but I do not directly work on DocumentDB, and I have no personal experience with MongoDB's server code. But I am familiar with the fa
by _msw_ 7y ago
Disclosure: I work at AWS, but I do not directly work on DocumentDB, and I have no personal experience with MongoDB's server code. But I am familiar with the facts regarding how AWS provides services that include open source code.
AWS has never used the AGPL licensed MongoDB code as part of a service, therefore the license change from AGPL to SSPL has nothing to do with AWS. There is no "Mongo fork" as you stated above.
See more in MongoDB's FAQ about the triggers for changing the license, in particular "international cloud vendors". https://www.mongodb.com/licensing/server-side-public-license/faq#what-we-sell https://www.mongodb.com/licensing/server-side-public-license...