Continuous Architecture in Practice: Software Architecture in the Age of Agility and DevOps (Addison-Wesley Signature Series (Vernon))

Reading this book, at least as someone who lives and breathes architecture at work, it’s easy to read and then focus on the myriad of complexities and realities in the real world. I found myself reading the text, seeing some bullet points, and immediately focus on some reality at work. I often wondered if I missed some piece during the presentation. The final chapter really brought the material together and assured me that I read the book as intended. If architecture was about choosing amongst three or four patterns, then there would be more architects. Reality is FAR more complex. The authors do a good job of exploring this complexity, unabashedly highlight there is no magic elixir nor fairy dust, and provide realistic suggestions. I commend the authors for being practitioners in a field where often the choice is amongst the most difficult, the enterprise must live with this choice for years if not decades, and people must content with realities they cannot control.

I needed an introduction in Software architecture and an insight on what a software architect does. The book offers this information and I found it interesting. I am not an expert in the field as I am a senior software developer, so I think the book may be more useful to architects. My gain from it is that it gave me ideas, but isn't this the point of every good book? I thank the authors for this!

This is the rarest of books - one that can be read at several levels and in a host of situations.Grab it before starting a large project to remind yourself what matters in setting up the right design and, even more important, the way to get there. Then come back as you work on the project to read and re-read the chapters on data, security, scalability - each master class covering the topics expertly (in a way that clearly stomped some of the other reviewers. )This is also a book that distills wisdom, clearly gained through experience but still has a surprising amount of “here is how you do it” to provide instant value. The authors also provide a considerable range of references that point to important but now well understood topics, so it won’t explain what DevOps is - it does something much more valuable: it helps connect all the dots into a coherent philosophy (the authors eschew the terms “framework” or “methodology”) anchored into a few key principles.As a Fortune 100 Chief Architect, I had made the authors' previous book (which I recommend to although this is a self-standing work) required reading in my team members - this one will join it on their shelves too.

I just want to say thanks to the authors! What I find most interesting in this book is that whilst a typical architecture function the way we have it defined at most large banks (and perhaps elsewhere too) has value, it has felt over the years increasingly detached from the advancements of how software is developed (and tested and in production). But I could never put my finger on exactly where and what to do about it. This book does exactly that. And especially the views of what to do about it (the 6 principles) suggests a significant shift in how we drive architecture in large organizations.

This book is one of the best technology books!! It’s elegant approach to define how we as architects must refine our practices to adapt to the world of agility and devops is everything!! Everyone in the technology field must have this book on their shelf! Thanks so much to Pierre Pureur, Murat Erder and Eoin Woods!! This is truly an excellent read with so many nuggets for us all!!!

In our ever changing world of increasing system complexity, the responsibilities and skills required to be a software architect must continually evolve. Successfully adapting to constant requirements, technology and business changes requires an architect to be multi-skilled, capable in engineering and technology, business and management. The role of architect has never been more challenging.This is why Continuous Architecture in Practice is an important book for all architects to absorb. The principles-based approach espoused in this book can be used to guide architects in charting a successful path in a broad range of project contexts. The essential activities for software architects present an excellent overview of the core professional skills an agile architect must possess, regardless of the problem domain and technologies in use.Most notably, the book devotes chapters to the key run-time quality attributes that drive modern systems. Security, performance, scalability and resilience are the lifeblood of Internet-facing systems. Each chapter provides a contemporary overview of the characteristics of these quality attributes and explains tactics an architect can adopt to design and evolve systems that are built for long term survival. An additional chapter on data architectures recognizes an important system component that is rarely covered in architecture books. Data lies at the heart of most systems and creating resilient and scalable data architectures exploiting modern data technologies is a skill all architects should have.Written in an approachable, concise and informative style, with concepts illustrated using an on-going case study, this is an excellent book that will help architects address the many challenges of engineering systems in the 2020s and beyond. It is a deep source of knowledge suitable for practicing and aspiring architects, and an advanced college course in software architecture. It will repay the time investment many times over.

This is a survey course of concepts and practices that should be obvious to any experienced software architect working today. It may be interesting if you have never developed multi tenant SaaS solutions. But anyone with hands on experience developing SaaS at scale will struggle to find unique insights.

The core architecture concepts are really well defined and contextualized within the newest software development trends. I definitely recommend it!

An important addition to Architecture series

Trabalho com arquitetura de sistemas desde 2001 (antes desta data pouco se falava em arquitetura de sistemas) e posso afirmar: este livro endereça corretamente os “pain points” da prática. Leitura mandatoria.

I bought this book because I was eager to learn practical advice and tips for a software architect. I liked the book as it thought me some activities of architecture design which I didn't notice much in the past. The book explained how architecture starts, continues, and keeps improvements by the time.