3 ms·
> Why use a relational store? If you’re working with a system that will only be read and written by an object based language? Why keep converting back and forth
by liability 7y ago
> Why use a relational store? If you’re working with a system that will only be read and written by an object based language? Why keep converting back and forth between a relational model and an object oriented model?
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.
- scarface74 7y agoIf your data store is behind an API you modify the API. You’re often using a different database for your OLAP and OLTP anyway.
- xchaotic 7y agoI 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?
- Spivak 7y agoIf 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?
- scarface74 7y agoHow 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.
- irishsultan 7y agoA 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.