Modernizing a national tax platform without stopping it

Key takeaway

Architecture readiness and organizational readiness are different findings, and the second one is what actually stops programmes. Both must be assessed, and the mitigation plan belongs next to the finding.

3M+
user base · 500K+ daily transactions · 10K peak concurrent

Programme scale

20+
domain microservices architected

Delivered

Blueprint
full architecture blueprint, delivered first

Delivered

Business problem

A national tax platform, a mature monolith serving 3M+ registered users, had to move to cloud native microservices without interrupting revenue collection. The constraint was not “rewrite it”; it was “modernize a system the state depends on, daily, at scale, while it runs.” Before any traffic could shift, the environment had to be proven ready to host the containerized monolith and the emerging services alongside the legacy platform.

Intervention

Lead architect for the modernization strategy. The first intervention was the full architecture blueprint, proven against reality by running the monolith containerized before any commitment. It continued as a structured readiness assessment across infrastructure, platform services, security, operations, people and risk, followed by rapid-response architecture wherever findings demanded it: migration and data-integrity controls, Zero Trust security design, enterprise integration standards, and the governance framework that held the whole programme together.

Architecture / approach

  • Strangler fig migration sequencing: 20+ domain microservices with explicit service boundaries, domain and event driven design, and API-gateway-based traffic splitting between monolith and services.
  • Migration safety: dual write synchronization, reconciliation and validation controls across legacy and target systems.
  • Target platform: on-premises Kubernetes (RKE2), service mesh with default strict mTLS east-west, an event-streaming backbone with enforced schema contracts, centralized identity, secrets management, change-data-capture from the legacy database, and GitLab CI/CD.
  • Zero Trust architecture spanning identity, workload security, data protection and secure integration, incorporating national data-privacy requirements.
  • Governance: formal ADRs covering 30+ technology selections; open-source-first and least-cost-of-tax-collection principles codified as decision criteria; financial and risk governance with phased approval gates across a five-phase plan.

Business outcome

  • Architecture and deployment plan assessed as complete, with no architectural show-stoppers.
  • Design-level readiness flagged as not yet empirically validated, so a structured validation programme was defined (load testing, failover drills, independent penetration testing, each with go/no-go criteria before any production traffic shift).
  • Developer readiness identified as the genuine show-stopper: the team was too small and too new to the stack to run both platforms in parallel; a training programme and staffing ramp-up were designed in response.
  • RKE2 + GitLab CI/CD proof of concept delivered: the legacy monolith running containerized, validating the platform before commitment.
  • Engineering staff mentored in cloud-native architecture, Kubernetes, DevSecOps and CI/CD, with capability transfer treated as a deliverable, not a side effect.
  • The programme is ongoing: validation, team ramp-up and the phased migration are in active delivery, with this architecture practice engaged through them.

Details limited by confidentiality requirements; this summary reflects only what can be shared publicly. Programme scale and structure are as published in the initiative’s own documentation.