4 ms·

Why use a non-FOSS database at all?

by dzogchen 3y ago

maxloh 3y ago
There is FerretDB. But they are not fully compatible to Mongo yet. https://www.ferretdb.io/ https://www.ferretdb.io/
romanovcode 3y ago
Also, but main point for MongoDB 10 years ago was the JSON. But now?
malermeister 3y ago
Isn't mongodb open source? https://github.com/mongodb/mongo https://github.com/mongodb/mongo Edit: ah it's source-available, not open source.
JackMorgan 3y ago
My question exactly. No sense building a house on someone else's land. Too many projects I've worked on were shattered because of technology that stopped being offered or got too expensive to justify.
nemo44x 3y ago
Because just about no one cares and I want to burn down a backlog quickly and often mongo enables that. Developer productivity is far more valuable that open source purity.
- KronisLV 3y ago
  > Developer productivity is far more valuable that open source purity. I mean, at least you get access to MongoDB source code, so that is something. I remember working on a project that used Clusterpoint years ago and the problem was that it was basically an abandoned piece of software due to the company behind it no longer releasing new versions. It was running, yes, but getting data out of it and migrating to something else sure took work and was very annoying because a lot of functionality had been built around it. So in regards to something so critical as databases and data storage solutions, I'd err on the side of picking things that are open source, or have compatible alternatives with permissive licenses. If someone were to build their own business around MongoDB (say, offering it as a service) and then SSPL came along, they'd be done for, even if just because of getting caught up in things going on between the org and large cloud vendors or something. Same with how you have to be careful with AGPL, so something like MinIO might be a non-starter in some cases.
  - nemo44x 3y ago
    Yeah if your goal is to offer it as a service then you’re out of luck. But if you plan on building anything else then you’re fine. Mongo is a thriving database so I’m not worried about it being abandon.
    - KronisLV 3y ago
      > Mongo is a thriving database so I’m not worried about it being abandon. With this, I can totally agree! And as long as it's not AGPL, you should be fine using it for most regular development stuff, even for closed source projects.
- deleted 3y ago
  [deleted]
- riku_iki 3y ago
  > Developer productivity is far more valuable that open source purity. that's until provider starts abusing power: increasing rates, close source completely, etc.
  - nemo44x 3y ago
    Yeah sure I guess but that’s not a real problem, at least not now or in the near future. Good chance it won’t even be a project I need to budget for by then. I’m really more interested in getting shit done today rather than worrying about 100000 possible future cases. This is how you succeed.

Why use a non-FOSS database at all?

maxloh 3y ago

There is FerretDB. But they are not fully compatible to Mongo yet. https://www.ferretdb.io/ https://www.ferretdb.io/

romanovcode 3y ago

Also, but main point for MongoDB 10 years ago was the JSON. But now?

malermeister 3y ago

Isn't mongodb open source? https://github.com/mongodb/mongo https://github.com/mongodb/mongo Edit: ah it's source-available, not open source.

JackMorgan 3y ago

My question exactly. No sense building a house on someone else's land. Too many projects I've worked on were shattered because of technology that stopped being offered or got too expensive to justify.

nemo44x 3y ago

Because just about no one cares and I want to burn down a backlog quickly and often mongo enables that. Developer productivity is far more valuable that open source purity.

KronisLV 3y ago
> Developer productivity is far more valuable that open source purity. I mean, at least you get access to MongoDB source code, so that is something. I remember working on a project that used Clusterpoint years ago and the problem was that it was basically an abandoned piece of software due to the company behind it no longer releasing new versions. It was running, yes, but getting data out of it and migrating to something else sure took work and was very annoying because a lot of functionality had been built around it. So in regards to something so critical as databases and data storage solutions, I'd err on the side of picking things that are open source, or have compatible alternatives with permissive licenses. If someone were to build their own business around MongoDB (say, offering it as a service) and then SSPL came along, they'd be done for, even if just because of getting caught up in things going on between the org and large cloud vendors or something. Same with how you have to be careful with AGPL, so something like MinIO might be a non-starter in some cases.
- nemo44x 3y ago
  Yeah if your goal is to offer it as a service then you’re out of luck. But if you plan on building anything else then you’re fine. Mongo is a thriving database so I’m not worried about it being abandon.
  - KronisLV 3y ago
    > Mongo is a thriving database so I’m not worried about it being abandon. With this, I can totally agree! And as long as it's not AGPL, you should be fine using it for most regular development stuff, even for closed source projects.
deleted 3y ago
[deleted]
riku_iki 3y ago
> Developer productivity is far more valuable that open source purity. that's until provider starts abusing power: increasing rates, close source completely, etc.
- nemo44x 3y ago
  Yeah sure I guess but that’s not a real problem, at least not now or in the near future. Good chance it won’t even be a project I need to budget for by then. I’m really more interested in getting shit done today rather than worrying about 100000 possible future cases. This is how you succeed.