Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

A Complete History, Analysis and Comparison of NoSQL Databases

DZone's Guide to

A Complete History, Analysis and Comparison of NoSQL Databases

· Java Zone
Free Resource

Learn how to troubleshoot and diagnose some of the most common performance issues in Java today. Brought to you in partnership with AppDynamics.

This recent article from Alexey Vasiliev at Leopard Blog titled "World of NoSQL" takes a very broad look at NoSQL - not only SQL, says Vasiliev - and the many forms it takes. Starting with an overview and history of relational databases and the history of NoSQL as a concept, Vasiliev breaks NoSQL down into its core components and analyzes each, exploring history, purpose, advantages, disadvantages, and specific examples of each type of database. Key sections include:

  • Document Stores
  • Graph Databases
  • Multimodel Databases
  • Multidimensional Databases

And quite a few more. The post would be an excellent primer for anybody new to or unfamiliar with NoSQL, but more importantly, it presents a larger context for the various technologies we discuss and work with every day. Vasiliev's analysis of the various types of NoSQL databases is concise and educational as well, and explores a number of more obscure databases that one might not hear much about otherwise.

Anybody interested in learning more about NoSQL as a whole, along with the larger context into which it fits, should take a look at the full post.

Understand the needs and benefits around implementing the right monitoring solution for a growing containerized market. Brought to you in partnership with AppDynamics.

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}