Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore Reactive extensions and support for applicable Apache Geode capabilities. [DATAGEODE-256] #305

Open
spring-projects-issues opened this issue Nov 2, 2019 · 1 comment
Assignees
Labels
in: api in: core type: enhancement

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Nov 2, 2019

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...

Implement the Reactive Streams API for Aapche Geode CQ Support.

For example, Pivotal GemFire's [Continuous Query

(CQ)|http://gemfire.docs.pivotal.io/latest/userguide/index.html#developing/continuous_querying/chapter_overview.html] would be a good fit to implement the Reactive Streams API, using Reactor or RxJava backed by CQs, and wrapping a CQ Listener with Reactive types (e.g. Flux).

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:

  1. AEQ (Listener)
  2. CQ
  3. Function Execution (by first adding support for Streaming Results)
  4. From Repositories
  5. 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


Reference URL: https://jira.spring.io/browse/SGF-377

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Nov 2, 2019

John Blum commented

Also note DATAGEODE-36

@spring-projects-issues spring-projects-issues added type: enhancement in: core in: api labels Dec 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: api in: core type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants