What is the one language that has not changed since you learned it in college? SQL is definitely one of them. In fact,
SQL has only received minor updates over the past decade. For DBA's, this has been a luxury. Is
NoSQL positioned to change this stability? NoSQL does not change SQL or relational databases, it simply provides a non-relational repository alternative. The last
Twin Cities Java User Group presentation given by Perry Hoekstra provided a very good summary of NoSQL's advantages and disadvantages. Here is a recap:
Advantages
- Performance metrics have shown significant improvements vs relational access. For example, this performance metric compares MySQL vs Cassandra:
- Inexpensive. All NoSQL implementations except for Amazon's Dynamo are open source.
- Data types are dynamic (typically strings). However, each implementation defines their own data types.
- Scales very well.
Disadvantages
- Bleeding Edge (right now).
- Replication across a cluster is not guaranteed in real-time. Synchronization will happen. However, the "when" is currently documented as unknown.
- Third-party report tool (Business Objects, Cognos, etc.) integration is currently not available.
- Data redundancy is likely to occur without relational tables.
- The application code performs the SQL-like operations.
- ORM capabilities do not exist yet.
- Transaction capabilites do not exist yet. However, Cassandra will have this feature soon.
- No GUI editor tool support.
Early Adopters of NoSQL
Social media corporations are the primary trailblazers of NoSQL implementations. The list includes:
Resources
No comments :
Post a Comment