On Wednesday, December 31, 2014 12:49:06 PM UTC-5, Greg Young wrote:
>
> To be fair if you are selling 100k distinct items per second of the same
> product you will most likely have much larger operational issues than
> making sure it's consistent. I'm imagining your delivery and warehousing
>
To be fair if you are selling 100k distinct items per second of the same
product you will most likely have much larger operational issues than making
sure it's consistent. I'm imagining your delivery and warehousing
infrastructure (physical not software). Of course I'd imagine at 100k sales per
Greg,
Thank you for responding. I wanted some validation about my design and the
selection of my components for the implementation.
Based on Andrew's and your response I assume that my basic domain model is
correct and I'm moving in the correct direction.
On Tuesday, December 30, 2014 1:03:
Andrew,
Many thanks for your time and detailed response. This is very helpful as it
gives me the direction I want to proceed.
I'm aware that with CQRS I get eventual consistency. The scenario and
requirements are artificial to provide a working use case. My main goal is
see how far can I tak
Firstly, your proposal is to use event sourcing and CQRS. Using
akka-persistence to implement this approach necessitates you being
comfortable with eventual consistency - i.e. there's no guarantee that your
views (the Q in CQRS) will be up to date with the domain model (stored as
events with cu
