Selection Criteria for NoSQL Database part iii

Selection Criteria for NoSQL Database part iii

In the first part of this blog series we discussed about the reasons in support of NoSQL databases vis-à-vis relational databases. The second part  grappled with the various types of NoSQL databases. Here we are back again, with the third and concluding part that will delve deep into the ‘Selection Criteria for NoSQL Database.’

 





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.

9 Responses to “Selection Criteria for NoSQL Database part iii”
  1. Dinesh P on

    Good article. All the three parts were good and easy to understand

    Reply
  2. leon shlimak on

    Great 3 blog posts. Helped me get my head around NoSQL. thanks :))

    Reply
  3. ichard on

    Nice set of articles that introduces a newbie to NoSQL…

    Reply
  4. Anshul Sharma on

    Hey Girish,

    Excellent work compiling these resources and very informative blog.

    I am SSE in an MNC and as the trend goes, am breaking down a huge monolith in smaller micro-services. I am responsible for a use case, which involves user-management for the enterprise level solution. User-management in terms of CRUD of the users, and their access-control (roles and permissions – something like an RBAC solution). We have close to 12M users in production and ours is a read intensive application. User writes are typically, few thousands every day and user read tends to be in order 10M-12M everyday. App is distributed in 50 different clusters across the world.

    I am trying to select a new database here for the micro-service and as per my use-case, “audit logging” is really important to me. Is there any of the database, which supports auto audit logging and versioning.

    PS: I am heading towards couchbase DB for the implementation and I read that it always creates a new version of the record. But I was hoping if some DB could do it neatly. Using couchbase will involve reading of lot of older version records.

    Thanks in anticipation.

    Best,
    Anshul
    anshulsharma1208@gmail.com

    Reply
  5. djamila_st on

    Thank you very much for these great, practical ideas. Like others who have commented, I need to create/revamp some portfolio examples. This article is very timely.

    Reply
  6. djamila_st on

    Beautiful article, Thank you!

    Reply
  7. Mariya Mariya on

    Thank you for the post.

    Reply
  8. Ziane on

    Great post.Thank you .

    Reply
  9. http://virtuelcampus.univ-msila.dz/facsegc/ on

    Thaks for this post.

    Reply
Leave a Reply