Geek Answers Handbook

When In-Memory-Data-Grid Gains Advantage Over NoSQL / NoSQL + Distributed Cache

Objective: . Imagine a high simultaneous environment when both statements are true:

  • You want to immediately respond to a user on a user event. To do this, you need to get some data from the data warehouse + process it;
  • Your system is intensively read / written, and it is very important to have data consistency.

Let it be a popular hotel reservation system .

IMDG:

As I understand it, IMDG should be used when we need to process a lot of data right away (on a user event, service request, etc.). Thus, it looks like an ideal option for the popular hotel reservation system.

IMDG vs NoSQL (+ distributed cache):

IMDG has one drawback - costs. RAM is more expensive, and IMDGs are also far from open source. In addition, there are articles claiming that you do not need IMDG, and NoSQL is good enough.

Question:

So, I would really appreciate your experience in how to determine when NoSQL starts to get stuck and you need to take a Data Grid into memory?

+4
source share
1 answer

Full disclosure: I work for Alachisoft.

, IMDG Open Source. . IMDG . , " .NET" NCache Data-Grid Java TayzGrid. Open Source 10 !

, , IMDG vs NoSQL (+ ). Relational vs. NoSQL IMDG . , Distributed Cache IMDG, .NET.

, IMDG , NoSQL Relational. , . , .

IMDG , , .

+2

More articles:


All Articles