I read the Japanese edition of Architecture Modernization by Nick Tune et al. (originally published by Manning).
The book frames "modernization" not as a closed technical task — refactoring legacy code, replacing infrastructure — but as a sociotechnical activity that treats technology, organization, and strategy as a single thing. The intended readers extend beyond engineers and architects to development leaders, managers, and executives.
Main topics covered:
- Modernization that starts from business goals, with frameworks like BVSSH for evaluating the value it delivers across multiple dimensions
- Understanding the current state via listening tours and mapping
- Visualizing strategy and stages of evolution with Wardley Mapping
- Product taxonomies
- Big-Picture EventStorming for surveying the domain
- Redesigning domain and team boundaries using DDD and Team Topologies as the spine
What stands out is how it threads together methods that are usually told as separate stories — DDD, EventStorming, Wardley Mapping, Team Topologies — and shows how to combine them for the single purpose of modernization. Even if you've read each method on its own, the seams between them are often where you get lost, and the book is useful as a map across them.
This is not a "replatforming plan" book. It is a book about how to read the organization, product, and market you have today, and where to first put the knife in. For anyone involved in decisions around legacy modernization, it is a useful piece for building shared vocabulary.
