I like to write because it forces me to straighten out my thoughts and because it scales well. Packaging vendor-neutral, real-life advice into short episodes allows readers to gain architectural insight while enjoying the read.
If you enjoy my books, I appreciate a review on Goodreads.
The role of architects has fundamentally changed. While knowing UML and architecture styles was sufficient a few years ago, modern architects reduce friction, align technology and organization, and chart a credible transformation journey. All while keeping up with the latest tech without being blind sighted by buzzwords. These architects ride the Architect Elevator to connect the organization’s penthouse, where the business strategy is defined, with the engine room, where the enabling technologies are implemented.
This new type of architect needs a new type of resource. This book summarizes years of working in both modern “digital” organizations and corporate IT in 41 episodes targeted at IT executives, enterprise architects, and software architects who are preparing for a bigger role or the next step in their career.
Note: This book is an updated and expanded version of 37 Things One Architect Knows. It contains five new chapters and several substantially reworked chapters.
This book came about because I was tasked with articulating the cloud strategy for a major customer. Our strategy was intended to be more than buzzwords and ambitions, and instead focus on principle-based decision making. Sadly, I couldn’t find a good book as a “baseline” for the formulation of our strategy—much of the available material was either high-level or product-centric. So, I wrote one.
This book translates a decade of defining cloud and IT strategies into vendor- and product-neutral guidance. A successful cloud journey starts by rethinking your current IT and laying out a set of meaningful decisions. The book favors depth of thinking over technical product detail and is hence approachable and valuable to a wide audience from architects to IT decision makers. Before you define a strategy, read this book first!
As the digital economy changes the rules of the game for enterprises and their IT, the role of architects also fundamentally changes. Having been virtually declared obsolete just a few years ago in the wake of agile methods, architecture is more critical than ever in the context of digital transformation. It’s a different kind of architecture, though: rather than focusing on technical decisions alone, architects need to combine organizational and technical knowledge to effect change in the organization’s structure and processes along with the technical platform. They ride the Architect Elevator to connect the penthouse, where the business strategy is defined, with the engine room, where the enabling technologies are implemented.
Packed with anecdotes from real-life IT transformation, this book prepares IT leaders, architects, and lead developers for a more rewarding, but also more ambitious role in the enterprise that spans all the way from the penthouse to the engine room and answers questions like: What’s expected of architects up in the penthouse? How to get there in the first place? What’s to be done at the individual floors? And how does one get back down?
Still relevant 17 years after publication, EIP established the base vocabulary for most modern message bus and API gateway software. It highlight the complexity of building distributed, asynchronous solutions but at the same time offers an intuitive visual pattern language to aid with their design. Like all good patterns books, it harvests the learnings and pitfalls from real-life experience and structures them into a cohesive language.
While the patterns also apply to microservices and serverless applications, the examples are at best of historic value. I therefore posted contemporary examples. Also, the long-time-in-the-making Conversation Patterns are available as work in progress.