@johnbywater@SKleanthous@RagingKore That was a long interesting thread :) and there are many things to discuss here.
After discussion with Eric and other DDD practitioners, the tactical patterns are very concrete, but come from more abstract ideas.
@johnbywater@SKleanthous@RagingKore The aggregate is implemented as a class that references other entities and value objects to maintain consistency. But the more general description is that this is something that is defined by a consistency boundary. What is inside is consistent, what's outside *doesn't have to*
Jul 10, 2020 • 9 tweets • 2 min read
After several discussions about event sourcing today, I think it's time to clarify things. Thread ⬇ 1/8
When talking about Query eventual consistency, views autorebuild with 0 downtime deployment, snapshots, automatic failover, we're in the Advanced Non Functional Requirements column with high availability, low latency, distributed systems, so infra is advanced and non obvious 2/8