3 ms·
I am involved in an ongoing discussion at work. The guys implementing the project want to go with a NoSQL / Angular / Node solution. I see a relational database
by collyw 13y ago
I am involved in an ongoing discussion at work. The guys implementing the project want to go with a NoSQL / Angular / Node solution. I see a relational database as being a better fit.
"Its so fast, even running on my laptop"
"you only have 3Gb of data just now"
"Its so quick to develop, just plug Angular straight into elsaticsearch, no schema,..."
The thing is, I just see lots of problems stored up for the future. Sure you have to define a schema up front if you go for a relational database, but changing it isn't such a big deal, not until you are in production with live data. Sure you might save time up front, but you are essentially cutting corners to achieve this, and storing work for the future.