Link Dump #203

In today's world it is hard to predict what happens next. But you can decide what you will read next:

Understanding the Problem and Solution Spaces

Last time, we briefly explored various types of boundaries that should be considered when making architectural decisions for your application. Today, I want to share insights about the Problem and Solution Spaces.

This understanding will support you in defining more effective boundaries — both at the level of services and within the code itself.

Link Dump #202

Today is a good day. With so many new articles to read it cannot be different:

The Secret Geometry Behind Your Architecture

In software architecture, we often talk about boundaries — and for good reason. Boundaries provide valuable insight into various aspects of our systems: cohesion, dependencies, complexity, and more.

Today, I want to walk you through several types of boundaries that should be considered when designing software architecture. Broadly speaking, they fall into two categories:

• Knowledge-specific: These are shaped by business knowledge, requirements, and policies.

• Technical: These are defined by technical constraints and non-functional requirements.

Link Dump #201

Best starter kit for Friday: sun, warm coffee, and articles worth reading. 

From Event Storming to Microservices: A Living Repository

For the past year, I've been quietly crafting something I’ve wanted for a long time—a repository that brings together many of the architectural and development practices I teach, use, and often write about. It’s not a demo for a talk. It’s not a throwaway “hello world.” It’s a living thing: full of decisions, trade-offs, experiments, and structure.

📦 Explore the repository

Inside, you’ll find examples of using:

• Saga, Outbox, Event Sourcing, and CQRS (within services and between them),

• EDA, Ports and Adapters, Strategic & Tactical DDD, Event Storming on all three levels,

• Plus CI, static analysis, testing strategies, ADR, and even some AI usage.

I’ve started also writing blog posts to explain how and why I approached certain problems the way I did — all of them are or will be also linked in the Readme.md. But it will take time to describe everything. If you’re curious, you don’t have to wait. Just dive in.

If you think something’s missing — or you think I got something wrong — tell me. Let’s talk. That’s how we all get better!

After the Big Picture: Turning Insights into Action

Now that you understand what Big Picture Event Storming is, how to facilitate it, and how to overcome common challenges as a facilitator, I believe the series of articles we’ve explored — walking through its steps and possibilities — demonstrate that the knowledge gained by everyone involved truly justifies the time invested in the workshop.

That said, the objective is to cover various stages of developing a Training Center application, to illustrate how techniques like Event Storming, microservices, event-driven architecture, sagas, and many others can work synergistically to improve product quality, architecture, and code. So the natural next question is: what comes after the Big Picture?