Link Dump #235
I bet you already read something good this week. But is there any reason to not read more?
Latest
Software Architecture
Keep it together or split it? Making boundary decisions under uncertainty
You’ve explored the domain and defined boundaries - but what if you’re still not sure where to draw the line? Learn how to decide whether to keep responsibilities together or split them when uncertainty is unavoidable.
Ambivalent feelings about details in domain modeling
Knowledge reveals complexity - and improves Architecture
Software Architecture must evolve - or it becomes the Problem
Domain Types: Build, buy, or outsource? (Part 2)
Domain Types: Identifying core, supporting, and generic domains (Part 1)
Ubiquitous Language: Structuring knowledge into domains (Part 3)
Event Storming
Event Storming Big Picture: Turning insights into action (Part 6)
Big Picture Event Storming doesn’t end with the timeline. Learn how its outcomes - hot spots, pivotal events, swimlanes, actors, and systems - help assess project risk, define system boundaries, and decide which processes to explore next.
Event Storming Big Picture: Keeping the workshop on track (Part 5)
Event Storming Big Picture: Choosing the first event (Part 4)
Event Storming Big Picture: Enforcing the timeline (Part 3)
Event Storming Big Picture: Exploring the chaos (Part 2)
Event Storming Big Picture: The big picture workshop explained (Part 1)
Event Storming Foundations: Facilitating beyond the basics (Part 4)
Domain-Driven Design
Domain Types: Build, buy, or outsource? (Part 2)
Architectural decisions evolve with knowledge. Domain classification provides direction, helping teams balance building, buying, and outsourcing as the system and market change.
Domain Types: Identifying core, supporting, and generic domains (Part 1)
Ubiquitous Language: Structuring knowledge into domains (Part 3)
Ubiquitous Language: Words that reveal domains (Part 2)
Ubiquitous Language: Stopping the translation game (Part 1)
