I have often been asked when should someone go for a NOSQL solution over age old RDBMS. These are my recommendations for using NOSQL:
- You have data which is "poly-structured" in nature. By poly-structured data I mean data comes in various formats.
- Data comes in great velocity
- Data comes in great volumes.
- You require High Availability from your data store
- You want to control and have trade offs between Availability, Consistency and Partition Tolerance
- You want to write very quickly than reads ( since data comes in with great velocity and you would want to store it)
- You want to be able to process data in parallel, i.e. be able to run the very popular Map Reduce on the data that is stored on the data store
- You do not want to be tied down by a fixed schema but you want to have a schema which is free and flexible. You want your data store to support "Elastic Schema Strategy"
- Your data store would be able to support on demand horizontal scalability
- You want to be able to provide configurable replication capabilities
- You want to have distributed architectures which are autonomous and you do not have to spend time plumbing your application and system. but you get out of the box support from the nosql store.
- You want fast programmatic approach to your data and don't want to get stuck with ORM and their dependencies on Relational Data Stores.
- You want a low cost solution which is easy to maintain, has good monitoring and management capability and finally, enjoys support from open source.
No comments:
Post a Comment