Application modernisation
Decompose monoliths into services, serverless functions, or containers on Amazon EKS — guided by Well-Architected reviews and a cost model, not fashion.
Approach
Strangler
Incremental extraction, never a big-bang rewrite.
- Basis
- Fixed price per milestone
- Pattern
- Strangler fig
- Risk
- Reversible per slice
What we deliver
Extract, don't rewrite.
Each slice ships independently and can be reversed independently. The monolith shrinks; it is never switched off in one move.
Domain decomposition
Service boundaries drawn along real business seams, not org charts.
Containers or serverless
EKS for stateful services, Lambda where the workload is genuinely event-shaped.
Event backbone
EventBridge and SQS decoupling the extracted services from the remaining core.
Delivery pipeline
Independent build and deploy per service, from the first extraction onward.
Observability
Tracing across the seam so you can see the monolith and the services together.
How it runs
One slice at a time.
We start with the slice that carries the most operational pain and the least coupling — an early, visible win that funds the rest.
Map the domain
Identify seams, data ownership, and the order of extraction.
Build the seam
Introduce the routing and event layer the extractions will run through.
Extract & ship
Move one bounded context at a time, in production, behind a flag.
Retire the core
Shrink and finally decommission what is left of the monolith.
Technology
What we build it on.
- EKS
- Lambda
- EventBridge
- API Gateway
- Aurora
- X-Ray
Cost & AWS pricing
Priced per milestone so each extraction is independently justifiable. Run cost is modelled before the first slice, because modernisation that raises your bill is not modernisation.
See funded AWS programmesNext step
Start with the slice that hurts most.
Discovery comes first — a short, bounded review that ends in an architecture, a scope, and a price. You keep the output either way.