I also think it makes sense to explore additional Apache Geode features and capabilities that may be possible to wrap with a Reactive API (i.e. Reactive types and Reactive behavior (where possible)), including, but not necessarily limited to:
AEQ (Listener)
CQ
Function Execution (by first adding support for Streaming Results)
From Repositories
Etc.
Function Executions is perhaps less apparent in its path to Reactive, but if there were a fire-and-forget (i.e. async) method to invoke a Function, then it would be possible to execute a Function in a Reactive context. I think wrapping the ResultCollector would give you that async/Reactive-like behavior. Additionally, a StreamResultCollector implementation could be wrapped with a Flux.
Additional thoughts and ideas will be added in comments
John Blum opened DATAGEODE-256 and commented
This is a R&D task to explore possible Reactive extensions and support for applicable Apache Geode capabilities.
Initially, this JIRA ticket was opened to explore whether it was possible to...
I also think it makes sense to explore additional Apache Geode features and capabilities that may be possible to wrap with a Reactive API (i.e. Reactive types and Reactive behavior (where possible)), including, but not necessarily limited to:
Function Executions is perhaps less apparent in its path to Reactive, but if there were a fire-and-forget (i.e. async) method to invoke a Function, then it would be possible to execute a Function in a Reactive context. I think wrapping the
ResultCollector
would give you that async/Reactive-like behavior. Additionally, aStreamResultCollector
implementation could be wrapped with aFlux
.Additional thoughts and ideas will be added in comments
Reference URL: https://jira.spring.io/browse/SGF-377
The text was updated successfully, but these errors were encountered: