Skip to content
CephalonEngine

Migration

Migration is hard. The goal of this section is to make it boring: each playbook lists the smallest reversible diff you can ship, the risk for each step, and a rollback path that doesn’t lose state.

Move in

From plain ASP.NET Core

Convert a Program.cs-style ASP.NET Core app into a Cephalon host. Module-by-module migration plan.

Open the playbook Move in

From a modular monolith

Lift an existing modular monolith (MediatR, Modular Architecture-style) onto CephalonEngine.

Open the playbook Move in

From microservices

Consolidate a microservice estate behind CephalonEngine. Decide what stays a microservice and what moves into a modular monolith.

Open the playbook Versions

Version upgrades

Move between CephalonEngine versions. Per-minor playbooks with before/after diffs.

Open the matrix .NET

.NET versions

Move between .NET 10 and .NET 11. Current readiness lane: assessment-only.

Open the matrix Reference

Breaking changes

Every breaking change in CephalonEngine history with the before/after snippet.

Open the changelog

Migration philosophy

Section titled “Migration philosophy”
  • Smallest reversible step. Every migration playbook is structured as a sequence of small, reversible commits. You can stop at any commit and ship.
  • Run two stacks side-by-side. Where possible we describe how to run the old and new stack in parallel until you trust the new one.
  • State migrations are explicit. Schema changes, queue topology changes, and identifier changes always come with a dedicated migration step.
  • Telemetry tells the truth. Each playbook ends with the telemetry you should add to verify the migration worked.

Required reading before any migration

Section titled “Required reading before any migration”