Data Exchange Platform / case study
I built the migration harness.
A reusable framework that orchestrated Spring → Quarkus migration across many microservices.
What I built
Reusable AI migration harness
One governed workflow, applied service by service.
AI EXECUTION ENGINEClaude Sonnet 5Assisted conversion & checks
HUMAN APPROVALDevelopersContext, evidence & approval
Swipe or use arrow keys to explore stages
01 / Harness rulebook
The harness encoded the migration path once.
Rules, checks and environment gates made the workflow reusable.
02 / AI-assisted execution
Claude Sonnet 5 converted the service locally.
The harness directed the work; developers supplied service context.
03 / Evidence before promotion
Checks ran before every environment gate.
Developers reviewed the evidence and decided whether to advance.
04 / Safe comparison
Spring and Quarkus were validated together.
The replacement was tested while the existing service remained available.
05 / Approved change
Humans approved the cutover and scale-down.
Only the proven Quarkus service remained after approval.
Harness boundary — reusable execution pattern