Geek Answers Handbook

Is there a NoSQL Solutions comparison (which is better in certain situations?)

I am trying to learn more about NoSQL as I am building a key-based archiving application in the Linux / PHP architecture. Can someone explain the differences between the main solutions (CouchDB / MongoDB / etc) regarding the advantages / disadvantages for each? The links would be great, although it's hard for me to do research using only Google.

+8
php mongodb couchdb nosql
source share
9 answers

google "nosql comparison" - in fact, there are many related blogs and documents.

Here is one of them: http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis

+8
source share

This link compares several databases regarding their capabilities:

http://www.vineetgupta.com/category/databases/

+4
source share

This link contains some information about nosql systems.

http://www.rackspacecloud.com/blog/2009/11/09/nosql-ecosystem/

+3
source share

Take a look at this nosql comparison mechanism. http://nosql.findthebest.com

+1
source share

http://aphyr.com/tags/Jepsen this series is excellent if you want to see how many databases handle network problems:

We learn about distributed consensus, discuss the implications of the CAP theorem, and demonstrate how different databases behave under a section.

+1
source share

Some bloggers posted a visual answer to this question about a month after this question was posted on stackoverflow.

Interesting, since he positioned various available solutions in relation to the CAP theorem.

I would just add that Cassandra can fit on either side of the “P” if you always ask for a quorum or not.

http://blog.nahurst.com/visual-guide-to-nosql-systems

Note. The author arbitrarily places RDBMS and data storage solutions on the CA side of the triangle. I know that accessible, not compatible with sections, inconsistent, but it is not.

0
source share

here is a comparison of MongoDB, Cassandra, Riak, CouchBase 2.0, HBase distributed on HDFS using ZooKeeper, Berkeley db 11g (java Ed HA) and Oracle NoSQL 11g

The author basically scanned all of his documents and cited areas describing their behavior in the following five categories:

  • Internal splitting
  • Automatic flexible data distribution
  • Hot Swappable Parts
  • Replication style
  • Automatic strategy for switching to another resource

and then provided short quotes for each of them.

see http://www.kammerath.co.uk/nosql-on-the-spot.html

0
source share

I think that it is also appropriate to take a look at the clustering functions of various solutions, because the main use case of NoSQL is scalable. Here is an overview with links to information provided by the supplier:

  • Couchbase - each node comes with a cluster manager, there is no central cluster coordination component. The provider says the Couchbase server scales linearly with each node added to the cluster. There is also an XDCR feature that provides replication at different geographic locations. CouchBase Cluster Overview
  • MongoDB - offers a delineated architecture in which the data is split into fragments, there is a configuration server that maps the data to the fragments, and a Mongo instance that delivers the data to the client application (clients do not have direct access to the fragments). The seller notes that scalding is a very difficult operation. MongoDB Cluster Overview
  • Open Source Redis - A cluster feature is under development, currently in the Alpha release, will offer live reconfiguration, fault tolerance, and pub / sub. The provider announced that some Redis commands will not be supported in cluster mode - complex multi-key operations. Establish connections or intersections of types, as well as all operations when keys are not available in the same node. Cluster Features Features
  • Redis Cloud (commercial) - a cloud service with the function of working clustering. The supplier says they can scale on demand, dynamically add more shards, and support all Redis operations. Redis Cluster Review
  • Riak - clustering is built-in, data is automatically shared between Riak nodes. Nodes can be added and removed dynamically from the cluster, and Riak will redistribute the data accordingly. The supplier says that the product is intended for distribution, and basic operations, such as reading / writing and displaying / decreasing, actually become faster when more nodes are added. Riak Cluster Overview
0
source share

NoRAM DB => "If it does not fit into RAM, I will die quietly for you"

Negotiations about Kassandra, Riak, Radish, MongoDB, Hazelcast, Neo4j, VoltDB, CouchDB, etc.

-one
source share

More articles:


All Articles