loading...

re: When to choose NoSQL over SQL? VIEW POST

FULL DISCUSSION
 

Very good comparison, some really useful information. One thing I'd like to point out - these techs are usually treated as an "either or" situation, as in, you must only use one of these approaches in an application. I find that they work pretty well I'm conjunction. I use NoSql for the real-time current data layer of an app (something like firebase for example). Then for any retained not realtime data, such as logs/errors/transaction history ( anything that isn't going to be real-time data layer ) I use more of a traditional relational SQL style storage.

 

I think that using their strengths for compatible situations is how you can provide the best value when creating a solution.

It is not by accident that all major (cloud) platforms provide both SQL and non-SQL database technology.

Mix-n-Mash to optimize your value!

 

I very much go along with Kyle & Edwin's points. Both DBs have their own pros and cons, and we are mostly interested in utilizing their best in our apps. I've also worked on apps that uses a hybrid of both databases, i.e. as u too specified. And it works perfectly. It's all engineering practices and this is how industries work.

Code of Conduct Report abuse