Dave

@CumpsD that's correct! I'm leaning on serde to do a lot of the heavy lifting throughout this crate.

It is under consideration for after v0.3 is released, but it's an area that can go a lot of different directions depending on what we want to support. More likely...

Hi @kubehe, in my experience the sagas in Axon framework tend to be too rigid for many rapidly changing situations such as adding many upcasters or changes around the business...

Support for different serialization formats has been a topic since the beginning of this project, primarily to support [protocol buffers](https://protobuf.dev/) for improved speed and lower storage requirements. I think the...

Hi @lambdalisue , it's quite possible that they've diverged at some point. Can you point to any specific places? Note that the documentation can be found [here](https://github.com/serverlesstechnology/cqrs/tree/main/docs/book/src).

Yes, PRs are ideal where you find these.

@paulkre this is a fine idea. This functionality is almost always needed and, at least for the queries I've built, gets added after the fact. It would be good to...

That's certainly not the design here. This is probably more of a naming problem since 'framework' implies you might handle multiple aggregates.

With two aggregates you'll need two different `Query` implementations, but these can absolutely work on the same backing store.

``` struct BankAccountAggregate; struct CustomerAggregate; struct MySharedQuery {} impl Query for MySharedQuery { ... } impl Query for MySharedQuery { ... } ```