-
-
Notifications
You must be signed in to change notification settings - Fork 11
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 for Commanded 1.0 #13
Comments
As a followup for those who might run across this same issue/PR - I switched over to using Oban for my particular use case. My Elixir chops aren't quite good enough to create this PR on my own. |
Hi, @slashdotdash I love commanded but I noticed that Thanks for the response |
@Sgiath I don't have any current plans to upgrade it. Using Commanded v1.x would allow a separate Commanded application and event store to be used for scheduling which would make it more self-contained. That is a worthwhile upgrade. |
@slashdotdash In Commanded 1.0 apps you build, do you have some new method for handling timeouts if not this scheduler? I am finding myself rebuilding something kinda like the scheduler to handle these -- timeouts for reservations seem like a relatively common pattern in the world of eventual consistency. Maybe the answer is something like 'just use schedex / rihanna / oban'? |
Yes, I would just use an external job queue such as Rihanna which has |
Upgrading to v1.0 breaks commanded_scheduler with the following error:
PR incoming with a naive patch, I'm not sure what the right pattern is for supporting multiple applications but it does work for a single application. I'd love feedback on how to do this right.
The text was updated successfully, but these errors were encountered: