2 ms·
EDIT: this was meant to be in reply to ct4ul4u. Agree. There are still cases where assembly language is the appropriate choice. That doesn't mean those gener
by ams6110 17y ago
EDIT: this was meant to be in reply to ct4ul4u.
Agree. There are still cases where assembly language is the appropriate choice. That doesn't mean those generalize to "business" use cases.
Sure there are cases where a "nosql" approach makes sense. But the examples cited (Google, Digg) bear little similarity to a typical "business" use case, and I'd claim that for "business" applications RDBMS is generally the best solution.
- milestinsley 17y agoAlthough, you could argue that the business use defines the technology use case which, in turn, informs the decision to use "nosql". For example, key/value DB's have enabled me to better implement features of a enterprise web app I am working on. The lack of a defined schema, in particular, was a strong business case for deciding to use key/value DB's. This document-based app can now store arbitrary fields on a per user basis (which was a headache with SQL!), which is a key USP for the app. Although, I agree, these points are tech-related. It would be nice to see the article mention true business use cases, such as transactions (i.e for financial, sensitive data applications).