Workshop · Modernization · 3 days
Modernizing a system in daily use
Three days to turn a modernization nobody wants to touch into a plan of small, releasable steps.
- Duration
- 3 days
- Format
- On site at your office, in German or English
- For
- Developers, architects and technical leads responsible for a system in production
- Prerequisites
- Access to the code and build of the system to be modernized.
What your team takes away
- An inventory of your system's versions, end-of-support dates and risks
- Tests that pin down today's behaviour, so changes stop being a gamble
- A roadmap of small, releasable steps with checkpoints, instead of a rewrite
Agenda
- Day 1
Where the system stands
- Inventory: versions, end-of-support dates and dependencies
- Where the risk sits: untested areas and hidden coupling
- Tests that pin down today's behaviour before anything changes
- Choosing the first step
- Day 2
Upgrading in small steps
- Upgrade paths for Java, Spring Boot and Angular, one major version at a time
- Automated migration tools and where they stop
- Keeping feature work going alongside the upgrade
- Releasing each step on its own
- Day 3
Replacing parts while they run
- Replacing components step by step instead of a rewrite
- Migrating data and running processes
- Moving a process engine, such as Camunda 7 to CIB seven
- A roadmap for your system, with steps and checkpoints
Planned on your system
The workshop works on your codebase, not on slides. At the end, your team has a modernization roadmap for its own system: the order of the steps, the tests that secure each one, and the checkpoints in between.
Where this comes from
At gematik, nine backend services moved to Spring Boot 3 within nine days, and the frontends from Angular 11 to 19. At Gesundheit in Bewegung, the platform moved to Java 25, Spring Boot 4, CIB seven and Angular 21. Both systems stayed in use throughout.
Request this workshop
You receive an offer with proposed dates within two working days.