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

Asynchronous Adapter Dispatch #2

Open
zmoshansky opened this issue Oct 5, 2015 · 1 comment
Open

Asynchronous Adapter Dispatch #2

zmoshansky opened this issue Oct 5, 2015 · 1 comment

Comments

@zmoshansky
Copy link
Owner

I believe putting each adapter's dispatch into an async job queue would be best; but, I'm not sure how to best go about this in the idiomatic way (GenServer/GenEvent?, External Job Queue Module?, Something like Resque?). I've outlined a few desirable aspects:

Goals

  • Ideally do this without any external (to elixir) dependencies (ex. Running a Redis server, RabbitMQ stack, etc. -- I'm not closed to this, but I'd love to keep it simple)
  • The ability to incorporate retries, back-offs, etc, and log when all tries exhausted
  • Persistence so that jobs don't disappear on App restart/server reboot
  • Not incorporate all the async code directly into echo, but have it easily pluggable.
@zmoshansky
Copy link
Owner Author

mnesia would handle the basics...

  • no dependencies
  • persistence

Although something that handles the rest of the code would be really nice, like jobs - erlang, honeydew or perhaps just bite the bullet and look at rabbitmq.

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

No branches or pull requests

1 participant