Queued updating subscribers
Two events published from the same publisher thread will be delivered to all subscribers in that exact order.
Event ordering allows a consistent view of the system to all subscribers.
Publishers are abstracted from availability or the speed of individual subscribers.
Both the key and the value may be any Serializable object (for Java) or Data Serializable objects.
Maximum queue sizes for subscriptions are configurable on a server wide basis.
Geode provides ordering of events at the publisher thread level.
Subscribers may choose to receive all events published on a channel or may request only for a subset based on some filtering criteria.
Publishers and subscribers are loosely coupled to each other.In this article we explore the juxtaposition of a Pub/Sub fan-out pattern and a Queue based pattern and why both are sometimes needed.