Microservices in Logistics: How DDD and Event Storming Helped Us Find the Boundaries

In logistics, business logic is intertwined: orders, routes, statuses, payments. Mistakes in microservice boundaries lead to tight coupling and endless rework.

I'll show how Event Storming + DDD help analysts build systems that hit the target from the start.

In practice:

  • How to run Event Storming: events, commands, roles — an end-to-end process map on a single board.

  • How to derive Bounded Contexts from events — microservice boundaries for API and database design.

  • A real-world mistake: we merged "Order Management" and "Assignee Assignment" — and how we fixed it.

  • Artifacts for development: context map, aggregates, Ubiquitous Language.

Outcome: analysts get a requirements alignment tool. Developers get clear service boundaries with no rework.

For system analysts, architects, and developers.

Comments ({{Comments.length}})
  • {{comment.AuthorFullName}}
    {{comment.AuthorInfo}}
    {{ comment.DateCreated | date: 'dd.MM.yyyy' }}

To leave a feedback you need to

or
Chat with us, we are online!