4 ms·
My point is that I dont need to do plain text queries or need to make queries simpler or worry about what I just did to a row when I am using NoSql Whereas I h
by vmception 6y ago
My point is that I dont need to do plain text queries or need to make queries simpler or worry about what I just did to a row when I am using NoSql
Whereas I have all those concerns with DMBS, the ORMs want to help but just add more problems
- beagle3 6y agoHaving used ORMs, SQL and NoSQL, My experience is that NoSQL is basically never the right choice for anything. It saves you minutes in the beginning in return for hours within a week’s time, then hours in return for days, then it just keeps costing. Especially since Postgres supports JSON properly, I’ve found no reason to use anything else except perhaps when you want eventual consistency, which couchdb may do better out of the box, but is a whole big can of worms. Added: I find DALs are the only acceptable layer over relational data, and other than BLOBs (which unfortunately no database seems to deal with nicely, and are thus relegated to the file system), everything that fits into a NoSQL fits at least as well into a modern RDBMS (e.g. Postgres)
- vmception 6y agoyes, I’ve encountered that in other people’s projects with increasing scope I architect my own projects to not need more than a simple data store and scrap ideas that dont fit that archetype