Application Modernization
Application modernization is not a wholesale rebuild in newer technology. It reconstructs dependencies across code, data, integrations, and delivery, then selects a treatment and phased transition path that makes the system changeable again.
From assessment to phased cutover and operations
Begin with the assessment and transition roadmap, continue to the NKS case for layer-by-layer implementation, then use the ownership article to decide who carries the next modernization wave.
Where should application modernization start? Map the transition before the rewriteApplication Modernization · July 18, 2026A practical guide to modernizing legacy applications without a big-bang rewrite: assess the current estate, choose retain, replace, replatform, refactor, or rearchitect, then design phased cutover and outcome metrics.→
Why did one person fix in three days what eight people couldn't?Application Modernization · July 3, 2026An eight-person SI project ended with core issues unsolved; alone, I fixed them in three days. Talent alone does not explain the gap, so I examine communication paths, diffused responsibility, decision structure, and the ownership gaps around re-architecture.→
From a monolith to NKS: rebuilding the stack in four layersApplication Modernization · May 30, 2026We moved a service locked into a single deployment and external CI onto NKS on Naver Cloud. How we split it into infrastructure, DB, API, and frontend — and made Git the single source of truth with Terraform, managed Cloud DB, and ArgoCD GitOps.→
Common application modernization questions
Does modernization mean rebuilding the entire system?+
Is modernization complete after moving to the cloud?+
Can modernization work when the service cannot stop?+
Explore Application Modernization for assessment across code, data, integrations, and delivery, followed by target and intermediate architectures and hands-on transition waves.
Explore Application Modernization →Put this work into practice.
An engineer reviews your environment and constraints first, then uses a 30-minute technical conversation when it helps define the execution scope.