Keeping an event-driven microservices platform current
Client context
A state government transport agency delivering a digital licence product on a cloud microservices platform spanning 83 repositories: AWS EKS for compute, Terraform for all infrastructure (a family of 20+ single-purpose modules plus multi-environment stacks), Confluent Cloud Kafka as the event backbone with Avro schemas and Debezium change-data-capture, Helm base charts, an API integration layer, and services in .NET and Java 17.
The problem
Two engagements, two problems. In the initial delivery: build the platform’s infrastructure foundation as part of the core team. Three years on: the platform had aged in place. EKS worker nodes needed a major version upgrade through four environments with gated pipelines, CI workflows across platform components were out of date, and engineers had no single place to discover services, ownership, builds, and documentation.
What was built
- EKS node and worker upgrades through the Terraform-driven multi-environment pipeline, including drain handling, dry-run gates for the promotion pipeline, and IAM role fixes.
- An upgrade CLI that operationalises the process: SSO auth, EKS kubeconfig, component version discovery, and working auto-upgrade of EKS components reading the platform’s nested Terraform variables, handed over with docs, screenshots, and a walkthrough video.
- A Backstage internal developer portal proof of concept, demonstrated at a platform showcase: a software catalog generated from existing documentation linking components to Kubernetes clusters, TechDocs, GitHub integration, and a framing deck on why an IDP.
- CI modernisation across platform components including the audit log forwarder and metrics exporter integrations.
Outcomes
- Auto generated upgrade pull requests significantly reduced the manual effort of keeping component versions aligned across four environments.
- Staying current on EKS reduced infrastructure cost through cheaper support.
- The Backstage proof of concept did its job as an exploration of what an internal developer portal could offer, shown at a platform showcase to open the conversation rather than to commit a build.