The history of Alexandria illustrates how software systems, like cities, are built on existing foundations and evolve over time.
Legacy code often fails to communicate business intent and lacks automated tests, leading to a system nobody fully comprehends.
Legacy software often becomes a victim of its own success, as its original design cannot support exponential growth or business pivots.
A lack of clear ownership and the anti-pattern of putting technical debt in the product backlog prevents legacy systems from aligning with corporate strategy.
A REST API is not a universal solution and can lead to awkward command implementations or a distributed monolith.
Rewriting software in a new technology often just replaces known problems with unknown ones without providing immediate business value.
Instead of a full rewrite, you can add new software for specific use cases and use routing to gradually replace the legacy system.
Embrace polyglot persistence by choosing the right data store for each use case and defining a single canonical source of truth.
Migration costs are often inflated by unnecessary cleanup; focus first on making the existing code work in the new environment.
Small, self-contained systems can be rewritten easily, making extensive abstraction layers an unnecessary source of complexity.
New architectural patterns can be introduced incrementally for new features, building bridges to the legacy system without a full rewrite.
39:49Mustafa Toroman
21:39Johannes Hansen
58:52Hans Hosea Schäfer
24:52Hendrik Lösch
24:38Carola Lilienthal
28:17Hendrik Lösch
1:01:30Henning Schwentner
42:02Simon Lasselsberger
Jobs that call for the skills explored in this talk.
Detlev Louis Motorrad-Vertriebsgesellschaft
Hamburg, Germany
Saby New Compy
Karlsruhe, Germany
Peter Park System GmbH
München, Germany
