Where it started
A broadcaster wanted to make digital content available faster. For that, a system landscape that had grown over many years was to be replaced by microservices, including a migration path for the legacy data.
How the bottleneck showed
Every new digital offering had to go from the editorial team into IT development and from there through the grown system. Changes to it were costly, because a lot depended on a lot. New offerings therefore waited until the system allowed them.
Where it came from
The editorial team and IT development worked in separate silos. The system landscape had grown the same way: one big block that everyone depended on. A new system cut alone would have changed little as long as the collaboration stayed the same.
What we did
Organisation and process
We brought the editorial team and IT development into shared workflows. Only then did it become visible along which boundaries the new system should be cut.
IT
Within a few days there was a working prototype with Spring Boot, Docker and Camunda BPM. We defined the domain cut, the starting point and the architecture principles for the target system. The migration concept follows the strangler fig pattern: the old system is replaced piece by piece while it keeps running. We started the implementation.
What stays
We handed over to the team, with extensive training. The team continues the migration on its own.
