Skip to content
19th October 2026Rebuilding Projections Without DowntimeWolverine 6.51 adds a warm-up node role for blue/green deployments: spin up the new release's nodes with no messaging at all, let them rebuild the new versions of your Marten or Polecat projections off to the side, and only cut over once they've caught up. Here's how that fits together with Marten's versioned projections, Wolverine's capability-based agent assignment, and the new side-effect gate, and why a client with a very large system and a habit of revising projections needed all of it.
15th October 2026Wolverine's Agent Assignment at ScaleHow Wolverine's leadership election and agent assignment subsystem grew up: why it exists, what 512 databases and 18,000 agents taught us about reassignment swarms and hysteresis, how we test it now, and a preview of dedicated warm-up nodes for blue/green projection deployments.
21st September 2026Every Lever Marten Gives You for Scaling a Big Event Sourcing SystemA tour of everything in Marten and Wolverine for scaling large event sourced systems: Quick Append, hot/cold event archiving, stream compacting, binary event serialization, read replicas, per-tenant partitioning, database per tenant and sharding, ancillary stores per module, projection lifecycles, strongly consistent async projections, partitioned projection data, and Wolverine-managed projection distribution.17th July 2026Ordered Messaging Without the Locks: Wolverine's Global Partitioning and Re-SequencerStrict message ordering usually means single-threaded consumers, distributed locks, or a lot of hand-rolled bookkeeping. Wolverine's global partitioning and re-sequencer give you ordered processing across a cluster while still scaling out — no explicit locking required.
Scalability
Posts tagged Scalability
19th October 2026Rebuilding Projections Without DowntimeWolverine 6.51 adds a warm-up node role for blue/green deployments: spin up the new release's nodes with no messaging at all, let them rebuild the new versions of your Marten or Polecat projections off to the side, and only cut over once they've caught up. Here's how that fits together with Marten's versioned projections, Wolverine's capability-based agent assignment, and the new side-effect gate, and why a client with a very large system and a habit of revising projections needed all of it.15th October 2026Wolverine's Agent Assignment at ScaleHow Wolverine's leadership election and agent assignment subsystem grew up: why it exists, what 512 databases and 18,000 agents taught us about reassignment swarms and hysteresis, how we test it now, and a preview of dedicated warm-up nodes for blue/green projection deployments.21st September 2026Every Lever Marten Gives You for Scaling a Big Event Sourcing SystemA tour of everything in Marten and Wolverine for scaling large event sourced systems: Quick Append, hot/cold event archiving, stream compacting, binary event serialization, read replicas, per-tenant partitioning, database per tenant and sharding, ancillary stores per module, projection lifecycles, strongly consistent async projections, partitioned projection data, and Wolverine-managed projection distribution.17th July 2026Ordered Messaging Without the Locks: Wolverine's Global Partitioning and Re-SequencerStrict message ordering usually means single-threaded consumers, distributed locks, or a lot of hand-rolled bookkeeping. Wolverine's global partitioning and re-sequencer give you ordered processing across a cluster while still scaling out — no explicit locking required.