Just Say Yes to NoSQL Part i

As the popularity of data virtualization continues to rise, companies are increasingly relying on data storage and retrieval mechanisms like NoSQL to extract tangible value out of the voluminous amounts of data available today.

This first blog in a 3-part series will explain why we believe NoSQL is among the best database technologies for sorting vast amounts of data. The second part will explore the different categories of NoSQL databases, and the final part will focus on how to zero in on the best NoSQL database solution.


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.

7 Responses to “Just Say Yes to NoSQL Part i”
  1. Adlen G. on

    Great article, it really helped us to switch to NoSQL

  2. Santo on

    Great article.. thanks for putting the details together

  3. Vivek Sharma on

    Nice Article…but am a bit confused on CAP Theoram. As per my understanding, for any distributed architecture, Network is not in our hand and therefore, Partition Tolerance has to be one of the factor. With P as a mandatory rule, any distributed architecture can achieve either of Consistency or Availability. If everything is working fine, all the three requirements CAP can be met. However, in case of a Network failure, C or A are the only options left. RDBMS’ enforce Consistency and NoSQL enforce Availablity.

    Please correct me if I am wrong.


  4. Manish on

    So based on this, can it be said that No SQL would not be best for banking transactions or for stock market transactions?

  5. Munish Bansal on

    Very well put together the details which could be quite complex to understand otherwise. Thanks.

  6. Anirudh Khanna on

    Nice content. Very Informative. Thanks for sharing.

Leave a Reply