Andrew Johnson

Looks like [MultipleAggregateReadStoreManager:63](https://github.com/eventflow/EventFlow/blob/develop-v0/Source/EventFlow/ReadStores/MultipleAggregateReadStoreManager.cs#L63) causes this. However, the fix to this isn't as simple as just switching the order of the sort. The `MultipleAggregateReadStore` is used when a `ReadModel` is using...

The interface `IIdentity` to me intrinsically implies a globally unique identity due to the lack of typing/additional information within the interface. It quite literally is just a string value. If...

That aside, I couldn't quite deduce the exact reason you needed typing at the `IEventPersistence` level but something that could be of use would be to use pattern mathcing/reflection on...

> Note that I wrote that it should be the aggregate type that keeps events separate from each other. I'm inclined to disagree, in favor for the the Aggregate's identity...

Sorry for the delayed response! >Could you point me to any type of DDD-documentation that clearly supports your claim that all aggregates must have >unique identity values across aggregate types?...

Added a refactor of the query processor's IoC. Since this would be a breaking query change any, I feel like rolling them together would be good!

Nice! That seems like the better option for now! I'll refactor my branch over this week to get it in line!

@rasmus Finally was able to get back around to this! Not so many changes required and looks like it could be added to v0! Also added unit tests!

@rasmus Just giving you another ping to see if this can go into develop-v1 soon :D

SerializedCommandPublisher should have its method's fixed such that they are correctly spelled!