Offers
One real process runs event-based in production
First model the domain together, then take one real process event-based into production — not as a prototype, but in operation.
“We have been talking about event sourcing for months and not one line of it is in production.”
- Duration
- Phase 1: 2–4 weeks · Phase 2: 8–12 weeks
- Who it is for
- Product and platform teams whose domain depends on history, corrections and provability
- Price frame
- Phase 1 from €12,000 fixed price, phase 2 from €45,000
- Technology partner
- the native web
Typical symptoms
- Requirements have been discussed for months without a shared picture emerging.
- Business and engineering use the same words and mean different things.
- The history of a case matters to the domain but does not exist in the data model.
- There is a feasibility study on event sourcing, but nothing of it runs in production.
- Nobody can say which increment should ship first, and why.
Outcome
- Event model of the core processes with commands, events and read models
- Slicing into deliverable increments incl. sequence, risks and effort ranges
- Reference slice live on EventSourcingDB: write path, projections, rebuild
- Operational picture: observability, recovery, handling schema change
- Handover to your team: patterns, decisions as ADRs, joint delivery instead of a lecture
How we work
Phase 1
Model and decide
Business and engineering model the flow together on a timeline: commands, events, read models and the places where it gets unclear. We run this phase together with the native web, the creators of EventSourcingDB. The model turns into deliverable increments with sequence, risks and effort ranges. Stopping here is a good outcome if the model shows event sourcing does not carry.
Phase 2
Ship to production and hand over
One real process goes live event-based: write path, projections, rebuild from the event stream, tests and fallback. No parallel system for the drawer. Observability, recovery and schema evolution are practised, not described. Afterwards your team delivers the next increments itself.
Frequently asked
- Do we have to book both phases?
- No. Phase 1 stands on its own and ends with a decision paper an internal team or another partner can work from.
- Why EventSourcingDB?
- Because it is built for exactly this purpose and keeps operations simple. But we work technology-agnostically: Axon, PostgreSQL or an existing solution are equally possible when they fit better.
- What is the role of the native web?
- the native web is our technology partner for event modeling and EventSourcingDB. In phase 1 we model together; in phase 2 we own delivery and operations.
- What does it cost?
- Phase 1 at a fixed price from €12,000, phase 2 from €45,000 based on the scope from phase 1.
Often combined with
Background in the article Event modeling is an adoption tool.
30 minutes, no slide deck. Afterwards you know whether and how we start.