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

extensible brokers and backend? #97

Closed
palanglung opened this issue Aug 27, 2016 · 3 comments
Closed

extensible brokers and backend? #97

palanglung opened this issue Aug 27, 2016 · 3 comments
Labels

Comments

@palanglung
Copy link

current implementation for broker and backend are with factory that use connection prefix as backend selector and i think is not posible to extend the broker or backend? CMIIW how about
database/sql style backends and brokers?

@RichardKnop
Copy link
Owner

@palanglung To implement a new broker or backend, you just need to follow these interfaces:

The current factory is not very flexible, I agree. That is one of the things I would like to refactor.

Instead of prefixes I would like to instead make config object more robust so you can define connection details there without custom connection string formats.

@mdouchement
Copy link

I have made a prototype with Postgres here that works well.

The relevant points are:

  • As @RichardKnop said, its a bit difficult to use external implementation with the current factory
  • SQL databases do not fit well for tasks' broker because you need to poll the data

@RichardKnop
Copy link
Owner

@mdouchement If you'd like to improve / refactor to make it easier to add custom external implementations, PRs welcome :)

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

No branches or pull requests

3 participants