I think an Async Event queue is what you want to use. Geode doesn't have an implementation of BlockingQueue, but if you are concerned about latency I think a push model like the aync event queues should be just as good as a polling model like a BlockingQueue. Async event queues do provide redundancy and balancing data across the cluster.
-Dan On Tue, Jul 26, 2016 at 8:41 AM, Chaudhary, Sushil (CONT) < sushil.chaudh...@capitalone.com> wrote: > Hi Anthony, > In our case, we want to avoid even a milliseconds of latency ( that could > happen because of Async way of Messaging communication). We need to use > IMDB as Queue, not necessary a blocking Queue. Unbounded/bounded Queue > should be have persistence in the same way, Geode does for regions/map. > > - In case of node failure, it should be backed up by redundant copy on > other node. ( same as region) > - Application process will poll object from Queue, instead of being pushed > by Async Event. The only reason is to avoid latency. Will Async call not > add any latency in the complete operation. > - it should balance the cluster in the same way, as geode does for regions. > > > Hope this give clarity on the use case. Let me know your thoughts. > > Sushil Chaudhary > Email: sushil.chaudh...@capitalone.com > > > > > > > On 7/26/16, 11:13 AM, "Anthony Baker" <aba...@pivotal.io> wrote: > > >Geode has been used in a lot of applications that involve event delivery. > > What is your use case? > > > >j.u.c.BlockingQueue can be useful but in the context of a distributed > >system there are important semantics to consider: > > > >- What happens when a node fails? Are the unacknowledged entries > >redelivered? What about missed entries if a client disconnects? > >- Are there any delivery guarantees provided such as ³At least once², > >³Once and only once², or ³Best effort but you will lose data under > >certain conditions²? > >- Can it load balance across a cluster and handle 1000¹s of connected > >clients? > > > >I wonder if the BlockingQueue is the best abstraction to capture all > >those ideas. > > > >Anthony > > > >> On Jul 25, 2016, at 8:31 PM, Chaudhary, Sushil (CONT) > >><sushil.chaudh...@capitalone.com> wrote: > >> > >> Thanks. Any update on Queuing? > >> > >> Sushil Chaudhary > >> Email: sushil.chaudh...@capitalone.com > >> > > > > ________________________________________________________ > > The information contained in this e-mail is confidential and/or > proprietary to Capital One and/or its affiliates and may only be used > solely in performance of work or services for Capital One. The information > transmitted herewith is intended only for use by the individual or entity > to which it is addressed. If the reader of this message is not the intended > recipient, you are hereby notified that any review, retransmission, > dissemination, distribution, copying or other use of, or taking of any > action in reliance upon this information is strictly prohibited. If you > have received this communication in error, please contact the sender and > delete the material from your computer. > >
