Thinh Le — Legacy Java Migration to Event-Driven Microservices

common findings

Sound familiar?

These are the five things I hear most often on a first call.

scaleYour monolith can't scale the parts that actually get hot. One busy module drags down everything else.

releaseEvery release means downtime and a team on standby. Deploys are an event, not a routine.

costYou're still on Java 8 and the license bill keeps climbing. Nobody's found the time to plan the upgrade.

riskNobody dares touch the old code. No tests, no docs, and the person who wrote it is long gone.

cloudYou tried "lift-and-shift" already. The cloud bill went up. The problems didn't go away.

→ You don't need a rewrite. You need a plan.

why modernize

What this actually gets you

Not abstract "cloud native" promises — concrete outcomes.

Lower cost

Cut licensing, infrastructure, and incident costs. Estimated 3-year TCO reduction: ~30–40%.

Ship faster, safer

Go from one release every two weeks to shipping whenever you want — without a war room.

Stronger security & compliance

Close out end-of-life runtimes and license risk, and make audits easier to pass.

Scale without firefighting

Handle peak traffic on the parts that need it — without over-provisioning everything else.

What I go deep on

Legacy Java/Spring migration, event-driven architecture (Kafka, NATS), Saga, Outbox, idempotency, CQRS, Event Sourcing, JVM tuning, and AWS/Kubernetes delivery — the patterns that keep systems consistent under real production load.

How I start

Not with a rewrite. With a 2-week Migration Readiness Audit — a clear, decision-ready plan for what to refactor, replatform, or leave alone, and in what order.

not ready to talk yet?

Send a quick note instead

Tell me a bit about your system. I read every message myself — usually within a day.

Not sure where to start?

A 20-minute call is enough to tell you whether an audit makes sense — no pitch, no pressure.

Book a 20-min call