4 ms·
The only practical application of MongoDB I can justify to this day, is if you have a form builder, that allows users to build completely custom forms. Forms.io
by throw1234651234 6y ago
The only practical application of MongoDB I can justify to this day, is if you have a form builder, that allows users to build completely custom forms. Forms.io gives you the form schema in such a scenario as JSON out of the box. That gets matched with answers as JSON.
Saving this to MongoDB directly, rather than SQL seems to simplify things.
With anything else, at the end of the day, you are enforcing FK constraints anyway, so might as well use SQL.
I never had issues with MongoDB performance.
One caveat to this is that I am yet to see a project that needs database sharding in real life, and I have worked on projects with millions of entries in a table and hundreds of writes a minute.
- CodesInChaos 6y agoMost relational databases have some level of json support nowadays. So I'm not sure how much it simplifies in that case.
- throw1234651234 6y agoThere is appeal to the json being directly searchable in the database, ala MongoDB. Specifically for analytics/reporting. The problem is that most analytics/reporting/BI tools SAY they support MongoDB and then they tell you to write a "connector" for each entity, at which point it's easier to just move it to SQL.