Re: [infinispan-dev] Ditching ASYNC modes for REPL/DIST/INV/CacheStores?
On Jan 31, 2014, at 10:59 AM, Sanne Grinovero <sanne(a)infinispan.org> wrote:
Generally I like the systems designed with SYNC_DIST + async shared
cachestore.
It's probably the best setup we can offer:
- you need a shared cachestore for persistence consistency
- using SYNC distribution to other replicas provides a fairly decent resilience
- if your cachestore needs to be updated in sync, your write
performance will be limited by the cachestore performance: this
prevents you to use Infinispan to buffer, absorbing write spikes, and
reducing write latency
+1. I would add to that that the async store also shields the user from e.g.
database's availability or slowness: if the write to the database takes time then
entries are queued up in memory and written when the backend can handle it.
But I agree we should investigate on removing duplicate
"asynchronizations" where they are not needed, there might be some
opportunities to remove thread switching and blocking.
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)