artem
Commanded: how do you send a command to all of the aggregates?
Hi all
I am implementing a small SaaS with Commanded and one of the areas I am trying Commanded with is counting credits. Every month a free account is going to get some credits which are to be expired within a month if not used.
For tracking it I’ve got a CreditStore aggregate that has buckets of credits with attached expiration time. Adding/using credits is as simple as processing commands AddCredits/UseCredits, but expirations and adding more credits every month (or whatever plan’s timeframe chosen) are more difficult.
Sure I can check credits on demand or via explicit command. E.g. when somebody logs in, I could auto send CheckUpdateCredits and it should work. However, I’d like these monthly expirations/additions happen at roughly correct timing so that I could send notifications like “you’ve got more credits now, go use them” and also have ability to do nice admin reports on what’s the situation right now.
What would be the way to have every single aggregate in the system process some command regularly?
Exact timing is not important, so it’s fine if it happens within an hour or so from the ideal moment. The best I was able to invent is forcing every aggregate have projection with own id and closest expiration time, then some cron-like utility every X minutes to check who needs to be checked and then send lots of CheckUpdateCredits commands to these.
Is this how periodic checks of all aggregates are usually done? Or is these some other [easy] way to schedule processing of all aggregates in the system once in a while?
First Post!
ouven
Hi,
I solved a problem with expiration time of marketplace offers - in a commanded system - by combining Oban scheduled jobs and single commands for every aggregate.
So, whenever the property expiration time changes, I create a new Oban job and maybe delete the old one directly from the execute callback.
Last Post!
tcoopman
In commanded (and EventSourcing) you would use a ProcessManager for this.
A process manager is responsible for coordinating one or more aggregates. It handles events and dispatches commands in response.
I haven’t read the full discussion yet, but this seems the way you should solve your problem.
Every month you would emit an event like CreditExpiryCheckRequested. The process manager listens to that event and the process manager sends commands.
Having said, think about your domain model, is this the best way to do this kind of thing? Are your aggregates modelled correctly, what are other options?
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #hex









