3 ms·
Look up mongodb licensing
by dralley 8y ago
Look up mongodb licensing
- jessaustin 8y agoOK, I can understand what MongoDB are thinking with SSPL: make the open source license so onerous (using this software requires you to open source your entire stack) that any ASP has to come to them for a commercial license. That makes sense for them, and probably for several other firms. However MongoDB were previously using AGPL, which specifically does not allow AWS to close their modifications. It's probably an open question as to whether Amazon can purchase enough judges to make the point moot, but the license itself is at least trying to keep the software free. In the long run if AWS abides by the license and releases all updates to their Mongo fork it will strengthen AGPL. Admittedly, I've been unable to find the repo through which that's happening now, so maybe my hopes are already dashed...
- _msw_ 8y agoDisclosure: 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...