Discover and read the best of Twitter Threads about #eventStorming
Most recents (3)
one of the best parts of development, even more fun than solving algorithmic riddles, is
discovering and turning new or hidden concepts into objects, along with the relationships between it and other objects (pieces of data and behaviors on data)
#ddDesign
discovering and turning new or hidden concepts into objects, along with the relationships between it and other objects (pieces of data and behaviors on data)
#ddDesign
or as E.Evans put it in the blue book - making implicit concepts implicit
it's fun, but it takes effort from devs and subject matter experts collaboration to make it happen. takes a culture of patience, curiosity, flexibility to mine for these implicit concepts out of the ubiquitous language
Indu Alagarsamy on the intersection of #DDD as a software discipline with Messaging as a technology counterpart. @Indu_alagarsamy
infoq.com/presentations/…
infoq.com/presentations/…
highlights:
👏🏾 in order to capture, understand, implement domain nuances, separate the unified model into new ones in it's own bounded context
👏🏾 in order to capture, understand, implement domain nuances, separate the unified model into new ones in it's own bounded context
👏🏾 decompose models/contexts
- by teams' makeup/composition
- by transactional consistency
- by business processes/ behaviors
- by teams' makeup/composition
- by transactional consistency
- by business processes/ behaviors
⏱️Why Event-Based systems Rock 🤘 [in 5 tweets].
Designing systems from domain events instead of columns in a database, endpoints on an API, or components in a view, has so many benefits.
#ddd #eventstorming
Designing systems from domain events instead of columns in a database, endpoints on an API, or components in a view, has so many benefits.
#ddd #eventstorming
[Communcation] Thinking in terms of domain events is the closest we can get to expressing what happens in the real world. Features can be communicated by non-technical folk as a series of domain events.
UserRegistered -> EmailVerificationSent -> EmailVerified
UserRegistered -> EmailVerificationSent -> EmailVerified
[Auditing & Reasoning] When we represent a system using events, we can reason about the way that the system changed over time since the current state is computed by applying all of the domain events that ever occurred. In some domains, this is mandatory for audits.
