3 ms·
IANAL but from what I know about Mongos current license (Server Side Public License) the restrictions of section 13 only apply if you are making a service with
by eudoxus 5y ago
IANAL but from what I know about Mongos current license (Server Side Public License) the restrictions of section 13 only apply if you are making a service with the express interest in providing DB functionality directly to your customers/users. IE: If you are making a Database as a Service platform, similar to Mongo Atlas or AWS RDS.
If you are just using mongo as a backend DB to fulfill some other internal requirement in your application, like general CRUD operations, then you are fine.
- dataraptor 5y agoI suggest to differentiate between selling MongoDB as a service (which would break the SSPL) using MongoDB as a database in your solution where you bind your application to the MongoDB driver that are licensed under Apache 2 (and which is the reason the knock offs can use MongoDB drivers and state they are MongoDB whatever compliant and be not because their stuff has nothing to do with MongoDB server but I digress). Nothing prevents you from utilising MongoDB Community in your own project/solution as DB backend.
- danhab99 5y agoArite, now the tally is even. I've heard the same number of people say to me that it's safe to use Mongo to power an app so long as I don't expose it, as have told me that I can't because I have to opensource all of my code that interacts with Mongo.
- alittletooraph 5y agoEuxodus is right. As long as you’re not building a product where the primary value of it is just delivering MongoDB as a service, you’re fine. There’s an FAQ that addresses that and more here https://www.mongodb.com/licensing/server-side-public-license/faq https://www.mongodb.com/licensing/server-side-public-license...