Without knowledge of your domain, the tag would be something like "Customer" and the ID would be customer_456 (or a UUID) any reason you like to attach the account_123 upfront ? Looks like some kind of relation between account and customer.
On Tuesday, May 24, 2016 at 8:37:22 PM UTC+2, [email protected] wrote: > > yep multiple tags could be a good option, as it can give me more freedom > in the future if I decide to change replay logic. > > Olger, regarding your solution, for example if we take customer aggregate > root, tag should be "customer" and persistenceId should be something like > "account_123_customer_456" ? > > > > On Tuesday, May 24, 2016 at 8:35:21 PM UTC+3, [email protected] wrote: >> >> Hi all, >> >> I think the most convenient way consuming of persisted events is using >> eventsByTag, so I have a dilemma of tagging events, for example I see two >> options: >> >> 1. by bounded context (like inventory, customer etc) >> 2. by account id >> >> In the second case you can expect a lot of consumers, let's say 500 000, >> so I have some concerns about scalability..., do you see any problems with >> this approach specifically with cassandra or it's better use as less >> consumers as possible and then delegate replaying work to other code? >> >> Thanks. >> > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
