MyPage is a personalized page based on your interests.The page is customized to help you to find content that matters you the most.


I'm not curious

How do I compare NoSQL databases?

0
Started on: 31 July 14
Participants: 2
We are considering implementing a NoSQL database in our company so that we can begin to store and process a lot of unstructured data that we receive each day. I'm looking at MongoDB, but I'm not sure how to compare it to others that are available, such as Hbase, etc. What are the parameters I should be evaluating and comparing when selecting a NoSQL database? We mostly need to process raw text from emails.
We are considering implementing a NoSQL database in our company so that we can begin to store and process a lot of unstructured data that we receive each day. I'm looking at MongoDB, but I'm not sure how to compare it to others that are available, such as Hbase, etc. What are the parameters I should be evaluating and comparing when selecting a NoSQL database? We mostly need to process raw text from emails.

This challenge is listed under Data & Information Management Community

Initiator

Mario
Mario
  Follow

Business technology consultant

More posts by: Mario Lewis

Please to reply this post
Important:
  • We hope the conversations that take place on MyTechLogy.com will be constructive and thought-provoking.
  • To ensure the quality of the discussion, our moderators may review/edit the comments for clarity and relevance.
  • Comments that are promotional, mean-spirited, or off-topic may be deleted per the moderators' judgment.

2 Suggestions

  1. 14 August 14
    0

    Filter all the DB by the type of documents they are most suited for.

    Find out what kind of querying is available - maybe you need just access by ID or you plan to write full blown queries doing complex selects.

    Indexing - what kind of indexing is available (if required)? Is it IDs only, or you can index any attribute in you document?

    That's my main points.

    After that: speed, scaling and replication (not in this order).

  2. 08 August 14
    0

    As a starting perspective, NoSQL databases are classified largely according to the type of data and type of storage they offer. These are Key-Value, Columnar, Document stores, graph-oriented, object databases, XML databases, and so on. MongoDB is good for documents, so from that point of view it would be fine for your purposes.

    Beyond that, a NoSQL database would be evaluated pretty much on the same parameters as a relational database. The difference, however is that a NoSQL database is typically used for big data and unstructured data, so the additional parameters for evaluation would be those relating to the databases ability to scale.

    When considering scaling needs, there are three key considerations, ie, consistency/atomicity, availability and partition tolerance. Different databases score differently on these parameters, and so depending on which of these is most important in your usage scenarios and circumstances, combined with the type of storage required (documents) you can go use these as the key considerations when doing your evaluation.

Awards & Accolades for MyTechLogy
Winner of
REDHERRING
Top 100 Asia
Finalist at SiTF Awards 2014 under the category Best Social & Community Product
Finalist at HR Vendor of the Year 2015 Awards under the category Best Learning Management System
Finalist at HR Vendor of the Year 2015 Awards under the category Best Talent Management Software
Hidden Image Url

Back to Top