Design - Build - Run is structured in such a way that each chapter introduces key concepts or considerations that flow through to the next. That is not to say that this book can't be used as a reference, but I suggest that initially you follow the book chapter-by-chapter to get the most out of it:
In Part I, you look at what production readiness means and all the quality characteristics your software needs to meet. You will examine the tools and technologies you're going to use by weighing the pros and cons of each and understanding the financial and quality impact of what you're going to do or not going to do. You set out your responsibilities as a developer and development team and ensure that you have everything in place to ensure success.
In Part II, you then look at the entire production spectrum. You will look at the environments and the data centers. You will look at service delivery and operations, and you'll look at monitoring, alerting, reporting, and batch. You will examine incident investigation and application maintenance.
In Part III, you will look at the conceptual design for the case study used throughout the remainder of this book. The chapters look at the conceptual design, planning the architecture, and modeling the application components. The case study is used to draw out a number of techniques and considerations and to lead into the patterns and practices discussions.
In Part IV, you will then examine some key patterns and practices that ensure you design and build your systems so that they are production-ready and support all that you have seen so far. You will examine designing for batch and reporting. You will move on to designing for performance, designing for resilience, designing for monitoring, designing for incident investigation, designing for application maintenance, and designing for testing. This part closes off with designing for deployment.
In Part V, you take a quick look at the some of the implications of applying the patterns and practices to your projects and the steps you can take to address them. This part uses the code associated with this book to demonstrate profiling the code and assessing the output as well as running the tests and assessing code coverage.