All projectsCloud Migration

Enterprise Engagement

Migration architecture

Cloud Platform Modernization

Designing a phased transition from a legacy estate to cloud services and domain-oriented data.

System overview
Legacy estate01
Transition02
Cloud platform03
Recovery paths04
ModernizationLegacy and cloud
Migration approach
Phased
Coexistence by design
Legacy + cloud
Integration pattern
Outbox

The challenge

Move the platform without a big-bang rewrite.

A domain-heavy legacy stack cannot cut over in one step. Data and writes have to move without stopping the business.

Product & engineering

What I delivered

Architecture for a phased migration from a legacy application and database estate to a cloud platform.

  1. 01

    Target platform

    Target-cloud and data design.

  2. 02

    Domain boundaries

    Domain boundaries and coexistence of legacy and new systems.

  3. 03

    Transition & recovery

    Shadow mode, transition bridge, outbox and dead-letter handling.

System design

How the pieces connect

Legacy and cloud
  1. 01

    Legacy estate

    Existing applications, data and writes.

  2. 02

    Transition

    Domain boundaries, bridge and shadow mode.

  3. 03

    Cloud platform

    Java services and AWS data architecture.

  4. 04

    Recovery paths

    Outbox and dead-letter handling.

Architecture & decisions

Strangler-style coexistence rather than a single big-bang rewrite. Java, PostgreSQL and cloud delivery, with domain-oriented data boundaries.

Outcome & evidence

What the work produced

Delivered outcome

Migration architecture and integration patterns are defined.

Scope & context

Internal programme and client names are omitted. The case focuses on migration architecture.