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

Support different event store engines #11

Open
gap777 opened this issue Oct 12, 2022 · 1 comment
Open

Support different event store engines #11

gap777 opened this issue Oct 12, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@gap777
Copy link

gap777 commented Oct 12, 2022

Is your feature request related to a problem? Please describe.

Your docs mention the capability of specifying a different underlying store engine. Is that supported yet?

Describe the solution you'd like

To enable event propagation to non-rails clients via Redis pubsub, while still using the Rails-y usage pattern of AES

Describe alternatives you've considered

Different event buses

Additional context

@gap777 gap777 added the enhancement New feature or request label Oct 12, 2022
@palkan
Copy link
Owner

palkan commented Oct 18, 2022

We extracted the basic functionality (RES-independent) into another gem: https://github.com/bibendi/downstream

It support using custom message bus implementations, check it out.

P.S. The plan is to migrate active_event_store to downstream (eventually) as a RES adapter. But for now we have two almost identical libraries 🤷‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants