Well yes, but it also changes the replication semantics just a tad :-) I would look at RxJava operators that can turn synchronous operations into Observables [1].
Anthony [1] https://github.com/ReactiveX/RxJava/wiki/Async-Operators > On Dec 23, 2016, at 11:47 AM, Kirk Lund <[email protected]> wrote: > > Changing the Region scope to DISTRIBUTED_NO_ACK makes all of the region > operations be non-blocking, right? > > -Kirk > > > On Fri, Dec 23, 2016 at 9:55 AM, Anilkumar Gingade <[email protected] > <mailto:[email protected]>> wrote: > Hi Mike, > > When you say "non blocking" operation; are you expecting a cache operation to > return immediately to client,without waiting for the operation to be > completed on the server cluster...I could see cache modification operation to > be non-blocking but how get/fetch/query falls into this category... > > You could perform put/destroy without waiting for the operation to complete > by using Geode function service. By setting "hasResult" on function, it > returns back to the client immediately...You could also execute get/query > operation on the function and write it to some temp region for later > consumption. > > -Anil. > > > > On Fri, Dec 23, 2016 at 9:40 AM, Anthony Baker <[email protected] > <mailto:[email protected]>> wrote: > Hi Mike, > > Currently basic data operations in Geode such as put/get are blocking > operations. You could look into half-sync / half-async patterns to bridge > the gap. > > I’d love to add support for reactive patterns in Geode :-) > > Anthony > > > On Dec 21, 2016, at 9:07 AM, Mike Youngstrom <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi Geode Users, > > > > I'm looking at creating an application using netty as the server and Geode > > as a major part of the backend store. However, It is difficult for a netty > > application server to consume blocking backend solutions. Does Geode > > provide any kind of non blocking interface I can use to access basic > > functions like create, destory, and get? Or any way I can get something > > like a CompletableFuture for those types of actions? > > > > Looking through the Javadocs I couldn't find anything but I thought I'd ask > > just in case. > > > > The application I'm writing is not complicated so I'm more than willing to > > trade significant api complexity for an efficient non blocking solution > > when consuming Geode. > > > > Thanks, > > Mike > > >
