Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
I'm very unsure If I understand...
Maintenance Checklist - you have a set of options.
You want to use mongodb because the options are dynamic?
Is parsing of the JSON document necessary - to eg create an aggregation?
myss45542yNot sure if I got it right, but if I got, many to many relations model should solve this.
This sounds like a relational data set to me.
Where's MongoDB come into this?
irene34582yPostgres can do both json and relational data. Why not use that?
Any modern database can.... Yes. Even SQLite. ;) *evtl laugh*
irene34582y@C0D4 Oh I didn’t know. I basically haven’t dealt with it since it was called MySQL. And not all modern database stuff is equal. MS SQL Server was a requirement for a previous project hosted in OpenShift and we got stuck with MS licensing fees if we wanted to use a pod’s whole resources. We couldn’t scale to more than two pods without problems with read write. Distributed DB problems in excess.
So now the philosophy is “we know that Postgres scales, can be distributed, and does what we need”. Generally we don’t mess around with other DB engines unless the customer dictates a technical decision.