5 ms·
This is awful advice. The tooling for things the author describes as harmful are as mature as the "stable technology"... It's easy to forget the time and effor
by tfolbrecht 8y ago
This is awful advice. The tooling for things the author describes as harmful are as mature as the "stable technology"...
It's easy to forget the time and effort to accumulate the knowledge for fighting the limitations to a technology you've familiarized yourself with.
- A SOA approach requires less stack knowledge overhead and $$$ for actual deployment and use than monolithic applications.
NoSQL vs SQL? Not everything fits on a spreadsheet. Just because you've gotten good at wiggling things into one doesn't mean that you're right.
> Posted 4 times in twelve days.
Who is upvoting this?
- JamesBarney 8y agoOne of the reasons I prefer SQL is it seems to be better are representing non relational data than NoSQL is at representing relational data. ( Not to mention the decade head start on tooling)
- SomeCallMeTim 8y agoWhy make it either-or? I prefer NoSQL when there are scaling needs, because it _can_ scale horizontally. Sometimes it's just easier to use, too, and there are times when the feature set maps _much_ better onto the problem at hand. Not all of your data access needs to scale horizontally, though, and if you have relational data you should use a relational database unless your scaling needs are extreme.
- tfolbrecht 8y agoI don't disagree except for the tiny edgecase where graphs are useful. The SQL/ NoSQL tradeoffs are well documented, saying NoSQL is hyped and volatile is silly.