The client can use the ‘register interest’ API’s to receive events from the server when a matching key is updated. The events can be delivered with HA and durability guarantees, very much like a messaging system. Another option is to use Continuous Queries to receive events based on a predicate clause evaluated on the server.
The strong consistency guarantee applies to the geode cluster—clients and remote WAN sites do not participate in synchronous replication to preserve availability and latency. See https://geode.apache.org/docs/guide/12/developing/events/how_client_server_distribution_works.html. Anthony On Jul 8, 2021, at 6:49 AM, Sarath Prabath Redlapalli Jaya <harrysarath2...@gmail.com<mailto:harrysarath2...@gmail.com>> wrote: Hi, Since Geode clients try to cache keys locally to save network trips & given the model of strong consistency, how does it handle key updates / deletes / sooner expirations ? Regards
