Database Reliability Engineering: Designing and Operating Resilient Database Systems

Database Reliability Engineering - highly recommended. I learned a lot and will be referring to this book over the course of the year as I make some changes in my company's engineering practices.I expected this book to cover techniques and patterns for building reliability and resiliency into databases. It delivered on that, but lots more as well. The book starts with a discussion of SLAs, SLOs, risk management, and visibility - after all, you can't really say meaningful things about reliability until you say what you mean BY reliability, in the context of your organizational commitments. Much of the rest of the book grounds back in this discussion in terms of how different techniques are relevant at different SLO and risk tradeoffs, and what things you need to watch to know how you're doing relative to these tradeoffs. It also notes that you can't prevent failures, so rather than trying to engineer with that as the goal (which results in fragile and brittle systems), it's wiser to aim for resiliency and recoverability. We're almost to page 75 before the book gets into meaty database topics like database-specific metrics (IOPS, TPS). We then dive into infrastructure, backup and recovery (and the importance of practicing - backup is boring, but when you need it, functional recovery is awesome like nothing else). The later chapters cover security, crypto, replication, and an overview of datastore architectures (not just relational). The book is a great blend of general guidelines and advice, concrete actions to consider, and architectural patterns that help you reason about data storage in general. Across all of the topics, you'll hear a lot about automation, infrastructure as code, and the need to automate routine operations to ensure consistency, repeatability, and ability to execute in a hurry.This should not be your first book on databases. It assumes a significant level of knowledge about data storage, devops, and automation. However, if you're responsbile for keeping a database system up and running, because that database is keeping your business up and running, this book deserves a place on your bookshelf.

"Database Reliability Engineering: Designing and Operating Resilient Database Systems" presents an actionable, reality-tested framework for helping your business develop a disciplined, sustainable ethos towards some of its' most valuable assets: its data.The authors of this book have the breadth and depth of knowledge and experience that can *only* come from observing unexpected behavior in complex systems built and operated by real humans working for actual companies.The structure and fluidity of the material also set it apart from other books I've read on database administration. After establishing the "guiding principles" of DBRE, I was pleasantly surprised to find a thoughtful framing of the friction between Development and Operations through the lens of Abraham Maslow's " A Theory of Human Motivation ."While the section on Service-Level Objectives is worth the price of the book alone, Laine and Charity apply a similarly deliberate, grounded style to the wealth of technical material as well. You'll learn:* the importance of taking your data infrastructure seriously* what an OpViz framework is and why it matters* that failure is inevitable no matter who runs your hardware* why you should plan beyond "Step 1. Restore from backup."* how testing and development environments aren't just for developers anymore* your data lives on physical computers and computers are terrible* to insert and retrieve data, you use a network (fact: also terrible)* the importance of data security and integrity* tradeoffs of different memory allocation implementations* what CRDTs are and why they matter* and much, much moreThe authors' present reality and a framework for coping with it and advance the discussion of reliability by doing so. Much like " Release It! ", " Continuous Delivery ", " Web Operations ", and " Systems Performance " before it, I believe "Database Reliability Engineering" will become essential reading for people making bits move.

Database administration has always part SRE umbrella, but the way databases are managed has alway been very different. Processes, tools and best practices of SRE world are not typically used with databases. It was kind of ok earlier, but as Cloud technologies, infrastructure as a code and continuous integration has become more main stream, things are changing. Todays' high performing teams expected databases also to be managed in same way as any other part of infrastructure managed by them. This is the first book which has been written to address this gap. A must read for everyone who is responsible for managing databases in today's world.

The authors have very, very deep knowledge - not just database specifics, but how the database interacts with applications and business requirements. They abstract their experience just enough to make it relevant to all data professionals, yet keep the language clear enough that it's still directly mappable to the technologies you use today.It's the kind of book that's easy to read, and hard to implement. Seriously, just implementing the SLOs described in chapter 2 takes most traditional companies months to agree on and monitor.Over time, the brand names and open source tools will change, but the concepts are going to be rock solid for at least a decade. This book is a great waypoint marker set about 5-10 years in the future for most of us, but it'll be one you'll be excited to work towards.

Ainda estou lendo, mas no inicio percebe-se que o livro busca trazer o perfil de DBA "clássico" para cenário de desenvolvimento de software atual e destacar sua importância. Recomendo para DBAs que buscam engajamento. Em relação ao livro, comprei no formato ebook está bem organizado e formatado.

I didn't really know what to expect from this book, but it turns out to be a real winner. I thought it would just be a technical tour of do's and don't for managing an enterprise-scale database for the web. There's plenty of that, but it ends up being a book more about how to best execute database design and operations in a modern tech org which uses cloud, agile, Inf. as Code, etc...This book will teach DBAs how to think like developers, and work more effectively with development teams – and conversely teach developers how to think/work with DBAs. Both sides will learn how to build more robust and well designed data-driven architectures, and keep them running.My only complaint about this book is that it's only 252 pages. There's plenty of value in that, but it's clear the authors could have written at least 200 more pages, and I wish they had. Some areas just get a high-level summary or intro, and there's so much more they could have covered.That said, I think everyone building internet apps, or leading a tech team or org that does so, should read this book. It's terrific.

If someone is looking for a practical guide, then (s)he has to look for another book. This book is more theoretical than real-world example driven.As its title suggests it talks about DBREs. Have you heard about DBRE before? If not, then this can be an excellent starting point.This whole book tries to advocate the DevOps and SRE movement for the database tier. For example, how to collaborate with devs and ops, how to design your system to be more resilient (from infra tier till replication) and many more.None of the topics will be discussed in depth rather the goal is the book is to have a good overview.

I'm still going through it, but so far it has been great.IMO this books is a complement for Google's SRE book in the form of practical advice to whoever has to care about operating a service in production.The way it's structure is clearly explaining how a service has to be operated in an effective way talking about what SLAs are, what observability is, and then talking about what to observe and most importantly why.The book then starts to build on these grounds how to operate, groom and evolve a data store.If you are a developer that has an interest in what Ops mean, this book is an awesome point of contact to get introduced to operations. If you are an Ops who happens to be a DBA, or that simply wants to understand how to build an environment that allows you to operate at large scale, this is the book for you.

Fantastic points, described in an easy to read format.