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

Separating the backends #88

Closed
jwoertink opened this issue May 5, 2024 · 0 comments · Fixed by #90
Closed

Separating the backends #88

jwoertink opened this issue May 5, 2024 · 0 comments · Fixed by #90

Comments

@jwoertink
Copy link
Collaborator

We have a few now.

  • Dev
  • Redis
  • Legacy Redis
  • Postgres (requested)
  • NATS (requested)
  • LavinMQ (reqeuested)

At this point, I think we should remove all backends from Cable, then make them each a separate shard. You include cable and the backend you want with it. Then other people could create new backends later. To do this, I think there's a few bits in #79 that could be abstracted out first.

jwoertink added a commit that referenced this issue May 6, 2024
Co-authored-by: Jamie Gaskins <jgaskins@hey.com>
jwoertink added a commit that referenced this issue May 19, 2024
Big refactor to make the backend registerable and swappable
jwoertink added a commit that referenced this issue May 26, 2024
* Initial reworking without any redis baked in. Closes #88

* Only testing against Crystal 1.10 and up now

* adding cable-redis as a dev dependency for testing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant