Architecture concept for the cloud migration of a core business application
A core business application handling sensitive personal data ran as a monolith on Java EE and Struts. TEQABLE worked out the target architecture and migration paths for a cloud-native architecture with Spring Boot and Angular and supported the decision.
Situation
The application processes sensitive personal data and was built as a monolith on Java EE and Struts. The existing documentation was partly badly outdated and largely did not reflect the current state of the application. The demands on architecture, security and operations were correspondingly high.
Goal
An architecture concept for the migration to a cloud-native architecture with Spring Boot and Angular, with options and costs, so that the business department could decide on solid ground. Alongside, the internal development team was to be supported with an offline-capable client application and its cloud-based backend.
Solution
TEQABLE drew up an overview of the existing architecture from the source code, worked out options for the target architecture as well as migration options and paths, and estimated effort and cost for each. The result was a basis for decision, and TEQABLE advised the business department in choosing the option.
For the offline-capable client application, TEQABLE designed and implemented the interface to the backend system, the data synchronisation and the update mechanism, and supported the internal team with problems and bugs.
TEQABLE provided the right person at very short notice.
Outcome
- Existing architecture documented anew from the source code
- Basis for decision on target architecture, migration and costs
- Business department decided on a migration option
- Interface, synchronisation and updates of the offline client implemented
- Follow-up contract to implement the architecture concept
Reto Maduz
Member of the Executive Board