Marten & Wolverine

Wolverine training on your domain.

I teach Wolverine for .NET and Marten DB on your domain. Wolverine consulting and Marten consulting are the same JasperFx engagement: event sourcing, CQRS and the transactional outbox in .NET, hands-on for the team that will run it.

Talk about the workshop

On your bounded contexts

  • Marten in production

    Marten DB is the event store: documents, aggregates, projections, and the habits that keep event sourcing from becoming a second undocumented database.

  • Wolverine

    Outbox, cascading messages, and handlers without a boilerplate mediator. Wolverine is the messaging half of the same workshop, not a separate engagement.

  • Your domain

    No demo shop. I use the bounded contexts you already have, including the ones that are painful.

  • The week after

    Follow-up after the first production week, so the architecture holds when I am not in the room.

The same topics, written for the team: Marten event sourcing, Marten as a document database, CQRS in .NET with Wolverine, and the transactional outbox.

If you are weighing MediatR against Wolverine, the comparison is MediatR and Wolverine, compared .

Workshop plus follow-up after the first production week. On-site preferred.

If you want the design and not the workshop, that engagement is Marten, Polecat, and Wolverine architecture.