Do deep insight and dense content make books boring to read and inaccessible? I don’t think so! My books translate experiences from the trenches of large-scale architecture and transformation into effective decision tools and engaging anecdotes, allowing readers to strengthen their architectural thinking while enjoying the read. Many positive reviews on Goodreads motivate me to keep writing this way.
While knowing UML and architecture styles was sufficient a few years ago, modern architects are expected to transform the organization along with the technology while keeping up with the latest tech without being blindsided by buzzwords. These architects make a bigger impact by riding 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 will benefit from a book that distills two decades of working in both modern “digital” organizations and corporate IT into 41 engaging episodes. It prepares IT executives, enterprise architects, and software architects for a more exciting role or the next step in their career. 4.8 stars on Amazon!
Note: This book is an updated and expanded version of 37 Things One Architect Knows. It contains five new and several substantially reworked chapters.
When I developed a cloud strategy for a major public sector client, we found that most available books were either very high-level or product-centric. So, I wrote this book for anyone who wants to place decision discipline and transparency ahead of empty buzzwords.
This book condenses a decade of elaborating cloud and IT strategies into vendor- and product-neutral guidance that’ll allow you to rethink your current IT setup and your journey to the cloud. Emphasizing depth of thinking over arcane technical details makes the book approachable and valuable to a wide audience, ranging from architects to IT decision makers. Before you define your 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 highlights 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.