this post was submitted on 16 Sep 2026
30 points (100.0% liked)
Programming
28548 readers
363 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Mongodb is proprietary.
Postgres is open source, and then there is documentdb which adds a mongodb compatible layer on top.
But it would probably be better just to use postgres + jsonb directly for that case.
Actually, MongoDB is webscale.
But I agree, I'd generally recommend a relational database like Postgres, especially for something that needs to be searchable quickly like an index.
Redis is apparently open-source again, now under AGPL (and two other proprietary licenses). But yeah, can also recommend the fork that spawned when they went proprietary: https://en.wikipedia.org/wiki/Valkey
When did Mongo go proprietary?
Edit: I'm actually wanting to make my entire project open source. MongoDB's current license, requiring all infrastructure to be open, might actually be for me.
No, the license is not a real OSS license.
The short version is that the requirement of all infrastructure being open, could potentially apply to parts of the stack where you don't have access to the source code, like the management engine or network card firmware.
It hasn't been tested in court yet, and because this is unclear, the SSPL is a hot potato nobody wants to touch or test. The possibility of the requirement for closed source firmware to be open, makes the SSPL effectively unusable.
The SSPL is neither Open Source Initiative nor Free Software Foundation approved: https://en.wikipedia.org/wiki/Server_Side_Public_License
Currently, SSPL licensed code is best treated as source available, but proprietary code.