Can NoSQL (e.g. MongoDB) replace Data Grid solutions, for example. Oracle Coherence

Question

I am looking for an opinion on replacing an existing data grid (e.g. Oracle Coherence) with another alternative to document storage, for example. NoSQL MongoDB. I thought about the most important pros and cons and came up with:

NoSQL

Pros:

• No additional database
• No ORM mapping required
• Although better query performance can be achieved by searching by ID, other queries can be satisfied by map / reduce queries

Minuses:

• It is quite difficult to achieve data consistency when updating multiple collections or even multiple rows in a single collection.
• Slower response time? (I suspect Coherence's response time might be better)
• A read operation may return old data

Data grid

Arguments

• Using a data grid seems more convenient to maintain data compatibility, for example. the data network becomes SOR (recording system)
• As the data grid becomes SOR, all data must always be available in the grid
• Remote Artists

vs

• An additional database means additional overhead and system / application requirements.
• With lots of data and outlines in place, any queries can take a long time.

Answer 1

Couchbase Server is a very good replacement for Oracle Coherence, especially for enterprise-class applications. Orbitz is a great example when a large number of Coherence nodes have been replaced by 70 Couchbase nodes.

Here you can learn more about replacing Coherence: http://gigaom.com/cloud/balancing-oracle-and-open-source-at-orbitz/

Slides from Orbitz's presentation on Couchbase are also available here: http://www.slideshare.net/Couchbase/t1-s6-oww-usescouchbase

Pros:

• High availability of nodes using replication and fault tolerance (avoid cold cache scripts)
• Secondary sub-million delays (built-in memcached object-level cache)
• High read / write bandwidth (very low granularity of locking) ( http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/white_paper_c11-708169.pdf )
• Strong consistency at the document / item level
• TTL / Validity per document / item

Minuses:

• It is difficult to achieve consistency between updates to multiple documents. Can be achieved using sentinels. ( http://www.amainhobbies.com/FromTheCEO/2012/09/09/invalidating-couchbase-cache-entries-with-sentinels/ )

Answer 2

He can, but it can be a pen and a paper system.

The question is whether this would be an acceptable replacement. It completely depends on the situation. In some cases, the NoSQL solution is faster, more scalable, than the relational solution, but in some situations it is important to have some support for longer transactions and relational restrictions.

It depends.

Answer 3

You have already given the pros and cons in detail ... as Ivain said, it depends on ...

What are the queries that the existing relational system is forcing?

we know that splitting on nosql db is simpler than on realtional db ... Therefore, if you switch to mongo, you can increase the performance of your system cheaper and faster ...

if people are happy in your oracle system right now. do not touch him:)

Answer 4

Yes - NoSQL can replace it. But a lot depends on what you are trying to do. If you just need a simple document repository with convenient search keys - NoSQL is no problem.

If you need an enterprise-class solution with support fees and features such as user aggregation, input processors, etc. etc. Perhaps Coherence is what you want.

I've seen people create custom NoSQL solutions on top of Coherence - this is a very expensive affair.