Database Reliability Engineering
Designing and Operating Resilient Database Systems
-
-
4.5 • 2 Ratings
-
-
- $42.99
-
- $42.99
Publisher Description
The infrastructure-as-code revolution in IT is also affecting database administration. With this practical book, developers, system administrators, and junior to mid-level DBAs will learn how the modern practice of site reliability engineering applies to the craft of database architecture and operations. Authors Laine Campbell and Charity Majors provide a framework for professionals looking to join the ranks of today’s database reliability engineers (DBRE).
You’ll begin by exploring core operational concepts that DBREs need to master. Then you’ll examine a wide range of database persistence options, including how to implement key technologies to provide resilient, scalable, and performant data storage and retrieval. With a firm foundation in database reliability engineering, you’ll be ready to dive into the architecture and operations of any modern database.
This book covers:
Service-level requirements and risk management
Building and evolving an architecture for operational visibility
Infrastructure engineering and infrastructure management
How to facilitate the release management process
Data storage, indexing, and replication
Identifying datastore characteristics and best use cases
Datastore architectural components and data-driven architectures
Customer Reviews
Worth the Investment
I purchased this book having a long history of delivering highly critical, fault tolerant database solutions for very large global financial institutions. The one philosophy I have is, never stop learning how to improve resiliency and be open to new approaches, hence my interest in reading the wisdom of other experiences.
Laine and Charity do a good job covering years of experience across a wide and evolving footprint of database technology. The fundamental goal of the book appears to engage the reader in thinking wide about issues that cause databases to fail and the software, operations and social engineering required to prevent it.
The book is framed and connects with its reader through Maslow’s hierarchy of needs. As an engineer and senior manager I would have preferred an approach built on disaster risk models such as Prevention, Protection, Mitigation, Response and Recovery. But I suspect the Maslow model is more approachable and engaging for a disparate audience of practitioners.
Every practitioner will approach this material from different areas of experience, budget, resources and skill. The fundamental lesson from this book is that resilience happens through an Engineered approach and continuous partnership of multiple disciplines. The book attempts to widen the experience thinking of practitioners, communicate importance of metrics, and give a framework for balancing resiliency risk against competing business goals.
Worth the investment in time and money. But augment with product specific best practices and regulatory frameworks.