DevOps: A Software Architect's Perspective

by Len Bass, Ingo Weber, Liming Zhu

The First Complete Guide to DevOps for Software Architects DevOps promises to accelerate the release of new software features and improve monitoring of systems in production, but its crucial implications for software architects and architecture are often ignored. In A Software Architect’s Perspective, three leading architects address these issues head-on. The authors review decisions software architects must make in order to achieve DevOps’ goals and clarify how other DevOps participants are likely to impact the architect’s work. They also provide the organizational, technical, and operational context needed to deploy DevOps more efficiently, and review DevOps’ impact on each development phase. The authors address cross-cutting concerns that link multiple functions, offering practical insights into compliance, performance, reliability, repeatability, and security. This guide demonstrates the authors’ ideas in action with three real-world case datacenter replication for business continuity, management of a continuous deployment pipeline, and migration to a microservice architecture. Comprehensive coverage includes • Why DevOps can require major changes in both system architecture and IT roles • How virtualization and the cloud can enable DevOps practices • Integrating operations and its service lifecycle into DevOps • Designing new systems to work well with DevOps practices • Integrating DevOps with agile methods and TDD • Handling failure detection, upgrade planning, and other key issues • Managing consistency issues arising from DevOps’ independent deployment models • Integrating security controls, roles, and audits into DevOps • Preparing a business plan for DevOps adoption, rollout, and measurement

Genres: Design, Software, Architecture, Computer Science, Programming, Technology, Engineering

352 pages, Hardcover

First published May 5, 2015

Reviews

[Franck Chauvel · Rating 2 out of 5]

This is all the "DevOps" trend: definitions, relationships with agile processes and micro services, and key outcomes and major pitfalls. I regret that it remains at the conceptual level: only the three case studies (Part 3) get more concrete and reflect how mature an organization must be to move to DevOps. I recommend Building Microservices and Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation to readers concerned with the technical aspects of DevOps.

[F M · Rating 2 out of 5]

The very first line comes to mind after finishing the book is 'its a very hard to read'. Authors keep on repeating the same things to the extent that it gets boring and very hard to read. Its all in theory how DevOps should be implemented, approaches and methods. I am very sorry to say that I have not gained much of the practical knowledge by reading it.

[Christoph Kappel · Rating 3 out of 5]

One of the main ideas of the whole DevOps movement is to bring ops and dev closer together, so both can learn from each other - and see the pain they inflict on each other. This works pretty well - but can the overall system design also support this?

Being a book from the SEI series, it is quite heavy to read and sometimes feels like a school book, but it centers around the question from above and is packed with lots of insights, studies and analysis.

[Roberto · Rating 3 out of 5]

abbastanza pieno di fuffa per fare padding e scrivere più pagine.
utile per avere una visione d'insieme, ma non è utile a capire il dettaglio perchè è di alto livello.
needless to say, scritto da accademici.

[David · Rating 4 out of 5]

Great technically detailed book on how the devops works from the architectural perspective. Some parts of the books were beyond my reach, but nevertheless helpful in gaining deeper appreciation of how a DevOps should work.

[Alexey Balchunas · Rating 2 out of 5]

Hard to read, because the author always repeats same things over and over again in every chapter. Plus, I learnt nothing new from it.