Re:Homebrew removes MongoDB from core formulas
by xchaotic on Monday September 02, 2019 @10:27PM
(#20863267)
I think you got it backwards. A relational schema change is required and probably a data reindex or reload when you change a data model so relational is the least flexible as opposed to something like Mongo nosql?
Re:Homebrew removes MongoDB from core formulas
by Spivak on Monday September 02, 2019 @11:02PM
(#20863419)
If you’re just talking about storing and retrieving documents in a hierarchy with a semi-fixed format then aren’t you asking for a filesystem?
Re:Homebrew removes MongoDB from core formulas
by scarface74 on Monday September 02, 2019 @11:20PM
(#20863483)
How do you propose that you query a filesystem? In this context, we are referring to a “document” as a structured JSON document. You still have a semi known structure with fields that you can index and query.
Re:Homebrew removes MongoDB from core formulas
by irishsultan on Tuesday September 03, 2019 @08:47AM
(#20865949)
A schema change can handle changes needed to existing data, if you don't do that then sure Mongo is easier, but then you've broken data in your system.
Re:Homebrew removes MongoDB from core formulas
by scarface74 on Monday September 02, 2019 @09:13PM
(#20862951)
If your data store is behind an API you modify the API. You’re often using a different database for your OLAP and OLTP anyway.
Well I can't tell you what the right choice in your system is, but in the general case I think going with a relational model by default generally makes sense because it's rather future proof. By that I mean a relational model gives you the most flexibility in the future to evolve your system in ways you couldn't/didn't anticipate when the system was initially designed.