The Client
A leading Western European smart-metering provider needed to modernise its legacy integration platform, which managed the ingestion, validation, and distribution of smart-meter data across the national energy network. Built on JBoss Fuse ESB with Apache Camel, ActiveMQ, and CXF web services, the system had accumulated significant technical debt: business and integration logic were tightly coupled inside OSGi bundles, horizontal scaling was impossible, deployments took hours and carried high rollback risk, and test automation and documentation were virtually nonexistent.
The Solution
Intway was engaged to assess the existing system, define a migration strategy, and design a target architecture. Due to missing documentation, the engagement began with a structured reverse-engineering exercise which includes: mapping all message flows, domain models, and integration endpoints, culminating in a comprehensive system landscape document, integration flow catalogue, and gap analysis. From this foundation, Intway designed a modern cloud-native architecture decomposing the monolith into domain-aligned Spring Boot microservices covering meter reading ingestion, command management, event processing, and device lifecycle. The design incorporated shared platform services for authentication, logging, monitoring, distributed tracing, and GitOps-based CI/CD on OpenShift, along with a detailed phased migration plan and a fully estimated delivery backlog.
The Result
The engagement delivered everything the client needed to move forward with confidence. Where there had previously been an undocumented, poorly understood legacy system, there was now full visibility into every integration flow, data contract, and technical dependency. The reverse-engineering deliverables alone represented a significant asset, giving the client’s internal teams and any future implementation partners a solid foundation to build on.
The target architecture and migration strategy provided a clear, low-risk, and fully costed roadmap for replacing the legacy platform incrementally, without disrupting live operations. By designing for container-based scaling on OpenShift, event-driven communication, and modern observability tooling from the outset, the architecture positions the client for faster deployments, improved resilience, and long-term maintainability.
