Hi Daniel!
I have a very similar situation, and here's what we did.
We have individual commands for adding/removing things, and in cases
where bulk updates are needed we support uploading CSV files to our
REST API, which goes through the file one line at a time and figures
out what to do (user missing->add, user existing->update), and then
issues the regular commands as if they were done one by one. In one
case we have an automated process figure out the list of items in a
collection and issues that as a single command/event, and then the
read model is updated by removing everything from the collection and
adding whatever was listed in the event, in order. From a concurrency
point of view we view it as "last one wins", as it is a very very rare
thing to happen in our case.
/Rickard
> --
> You received this message because you are subscribed to the Google Groups
> "DDD/CQRS" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
dddcqrs+u...@googlegroups.com.
> Visit this group at
https://groups.google.com/group/dddcqrs.
> For more options, visit
https://groups.google.com/d/optout.