- What is EventStorming?
- EventStorming is a workshop technique, devised by Alberto Brandolini, in which business and development rebuild a domain by lining up the events that happen in it. It is used at three levels of detail: Big Picture for the whole flow, Process Level for a single process and Design Level for the design of the software. In one session it brings out disagreements and implicit rules that would otherwise surface in the code, much later.
- How is this service different from an EventStorming workshop?
- A workshop leaves a shared map, and its value depends on what happens next. As well as facilitating it, we work with your team in the code to turn that map into bounded contexts, modules and tests, and we support the architecture and organisation choices that follow.
- Is Domain-Driven Design useful if we don't want to move to microservices?
- Yes. Bounded contexts are logical boundaries and work inside a monolith too, which with explicit boundaries becomes a modular monolith. In many systems that is the best choice, and microservices remain an option to assess when a context needs independent releases or independent scaling.
- Do you offer Domain-Driven Design training?
- Yes, targeted training. We build it around your domain and your code, at the start of the engagement or within the ongoing work. We don't run off-the-shelf courses, because DDD is learned by applying it to a problem the team knows.
- Who should take part in the EventStorming?
- People who know the business and people who write the code, together: product managers, domain experts, developers and whoever decides on architecture. If one side is missing, the map tells only half the story of the system.
- Which technologies do you work with?
- We're stack-agnostic and adopt the languages, frameworks and tools your team already uses. Domain-Driven Design is about how the parts of a system are divided and named, and it applies in any technology.