Exploring the Different Types of NoSQL Databases Part ii

In our previous post titled ‘Just Say Yes to NoSQL’, we cited the CAP theorem, did a point-by-point comparison between RDBMS and NoSQL and explored in-depth, the various characteristics of NoSQL which make it the most reliable database solution available today.

In this second part of the 3-part series we will focus exclusively on the different types of NoSQL databases.


To access more of this article, please provide the following information.

Girish Kumar

Girish Kumar

Technical Lead

Girish Kumar is a Technical Lead at 3Pillar Global and the head of our Java Competency Center in India. He has been working in the Java domain for over 8 years and has gained rich expertise in a wide array of Java technologies including Spring, Hibernate and Web Services. In addition, he has good exposure in implementation of complete SDLC using Agile and TDD methodology. Prior to joining 3Pillar Global, Girish was working with Cognizant Technology Solutions for more than 5 years. Over there he has worked for some of the biggest names in the Banking and Finance verticals in U.S. & U.K.

Girish’s current challenges at 3Pillar include getting the best out of Apache Hadoop, NoSQL and distributed systems. He provides day-to-day leadership to the members of the Java Competency Center in India by enforcing best practices and providing technical guidance in key projects.

16 Responses to “Exploring the Different Types of NoSQL Databases Part ii”
  1. BD on

    Very helpful. Thanks!

  2. Rohit on

    Good Consolidation at one page and neat read.

  3. Mohammed on

    Thank you so much for this article,
    I have a little question about Graph databases , why u don’t talk about OrientDB or Neo4j ?
    I know that the goal of your artcile is just explain the difference between each model (type) of nosql database. But what u think about this two technologies ?

    Thank you.

  4. Manas on


    Good article on NoSQL databases.

    I have one query: What are differences between Document databases and Key-Value pair databases?

    • sandeep on

      The data which is a collection of key value pairs is compressed as a document store quite similar to a key-value store, but the only difference is that the values stored (referred to as “documents”) provide some structure and encoding of the managed data

  5. Angel Banuelos on

    Very helpful!.

    Well Distributed with nice examples and comparisons.


  6. Santosh Sahrma on

    Hey Girish,

    It’s really very helpful article.
    Thank you so much for such a great, neat and easy to understand comparison.


  7. masoud on

    But in example of BigTable, I think the json is not correct,
    There must be a ‘address’ key between line 2 and 3

  8. Priya on

    Very nice artical ?
    I have a query : document database and schema less database are same type of NoSql database??

  9. Harsh Gupta on

    There is a difference between column-oriented and wide column store. Cassandra is not column-oriented but is a wide column store.

  10. F00dBall on

    Great overview about NoSQL-Databases. But what do you think about key-value stores for multi-dimensional data like https://github.com/shojinishimura/Tiny-MD-HBase or https://github.com/jnidzwetzki/bboxdb ?

  11. Deepak pandey on

    the information is really effective. very clear way to define NoSQL database. really good.

  12. Satish on

    Excellent Article

  13. Donald on

    Nice article, thanks !

    Can you add a link to the previous and next articles in the series (part I and III)?

Leave a Reply