Apache Ignite - Near Cache consistency

[Arnaud Lescaroux <al...@kyriba.com>]

Hello,

I am evaluating Apache Ignite to check if it fits our company's need. So far so good. Now i am trying to understand how the near cache feature works in terms of consistency.

We currently have several micro-services with one Ignite configured in client mode in each. All these instances are connected to several Ignite servers in a cluster. For some use cases (reads>>>writes) it seems reasonable to use a near cache in front of the cache servers. I have checked and it seems to automatically invalidate "stale data" on all instances in case of write, which is good.

My question: is there any documentation beside the one on the official site that explains how it works? In particular i would like to understand if any subsequent read requests (after the write one) to any other instances will get the updated data (no eventual consistency).

Thanks!

Re: Apache Ignite - Near Cache consistency

[Denis Mekhanikov <dm...@gmail.com>]

Correct.
Strong consistency is guaranteed for atomic caches as well, including near
cache entries.

Denis

пн, 5 нояб. 2018 г. в 11:21, ales <al...@kyriba.com>:

> Thanks Denis for the answer.
>
> Actually i am using "ATOMIC" atomicity mode (ie no transaction).
> I have been told that it may be linked to the backup synchronicity mode
> (FULL_SYNC would ensure consistency between nodes and eliminate stale
> data).
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Apache Ignite - Near Cache consistency

[ales <al...@kyriba.com>]

Thanks Denis for the answer.

Actually i am using "ATOMIC" atomicity mode (ie no transaction).
I have been told that it may be linked to the backup synchronicity mode
(FULL_SYNC would ensure consistency between nodes and eliminate stale data).



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite - Near Cache consistency

[Denis Mekhanikov <dm...@gmail.com>]

Arnaud,

There is a short note on the following page about near cache consistency:
https://apacheignite.readme.io/docs/near-caches
Here is its text:
> Near caches are fully transactional and get updated or invalidated
automatically whenever the data changes on the servers.

Near cache entries take part in the transactions, just like regular
backups. So ACID consistency is preserved.

Denis

пт, 2 нояб. 2018 г. в 16:17, Arnaud Lescaroux <al...@kyriba.com>:

> Hello,
>
> I am evaluating Apache Ignite to check if it fits our company's need. So
> far so good. Now i am trying to understand how the near cache feature works
> in terms of consistency.
>
> We currently have several micro-services with one Ignite configured in
> client mode in each. All these instances are connected to several Ignite
> servers in a cluster. For some use cases (reads>>>writes) it seems
> reasonable to use a near cache in front of the cache servers. I have
> checked and it seems to automatically invalidate "stale data" on all
> instances in case of write, which is good.
>
> My question: is there any documentation beside the one on the official
> site that explains how it works? In particular i would like to understand
> if any subsequent read requests (after the write one) to any other
> instances will get the updated data (no eventual consistency).
>
> Thanks!
>
>