5 Rules for Adopting NoSQL Databases
David McGoveran[1] interviewed by Intelligency in Software:
I suggest considering a NoSQL solution if any of the following are true:
- First, when discovery of relationships is more important than consistent processing and specific data results.
- Second, if the data processing is meant to be inductive (e.g., suggestive) rather than deductive (i.e., precise).
- Third, when the application is changing very fast, data complexity is great (variety or amount).
- Fourth, if physical issues, like big data or a high degree of parallelism, are more crucial than data integrity. You must be willing to throw away data consistency in favor of performance and scalability.
- Fifth, if you have a mission-critical one-off application for which a fixed data organization is ideal, in which case the costs and risks may be lower than licensing a vendor’s RDBMS or trying to force an open-source RDBMS to fit the need.
Original title and link: 5 Rules for Adopting NoSQL Databases (©myNoSQL)
via: http://www.intelligenceinsoftware.com/feature/expert_insight/yes_or_no_on_nosql/index.html
