Services Engineering Reading List

• Highly Available Transactions: Virtues and Limitations
• The Incident Command System
• The Chubby Lock Service for Loosely Coupled Distributed Systems
• Bigtable: a Distributed Storage System for Structured Data
• On Designing and Deploying Internet Scale Services
• Kafka: A Distributed Messaging System for Log Processing
• The Unified Logging Infrastructure for Data Analytics at Twitter
• Automatic Management of Partitioned, Replicated Search Services
• Learning to Embrace Failure
• Scaling Big Data Mining Infrastructure: The Twitter Experience
• Dremel: Interactive Analysis of Web-Scale Datasets
• Out of the Tar Pit
• The Log-Structured Merge-Tree
• In Search of an Understandable Consensus Algorithm
• Failure Trends in a Large Disk Drive Population
• F1 - The Fault-Tolerant Distributed RDBMS Supporting Google’s Ad Business
• Dapper, A Large Scale Distributed Systems Tracing Infrastructure
• Resident Distributed Datasets: a Fault-Tolerant Abstraction for In-Memory Cluster Computing
• The Human Side of Postmortems
• Crew Resource Management: a Positive Change for the Fire Service
• Resilience Engineering: Part I - engineering-part-ii-lenses/) (Allspaw)
• Systems Engineering: a Great Definition
• Chaos Monkey Released Into The Wild
• Some Rules for Engineering and Operations
• Service Level Disagreements Part I - level-disagreements-2.html) (Black)
• Incuriosity Will Kill Your Infrastructure
• My Philosophy on Alerting
• You Can’t Sacrifice Partition Tolerance
• Customer Trust
• Observations on Errors, Corrections, & Trust of Dependent Systems
• Life Beyond Distributed Transactions: An Apostate’s Opinion
• The Network is Reliable
• The Trouble with Clocks
• Call Me Maybe: Final Thoughts
• Getting Real About Distributed Systems Reliability
• On HTTP Load Testing
• Observability at Twitter
• Stevey’s Google Platforms Rant
• Service Design Best Practices
• The Field Guide To Understanding Human Error
• Better: A Surgeon’s Notes on Performance
• The Checklist Manifesto: How to Get Things Right
• Effective Monitoring and Alerting
• Release It!: Design and Deploy Production-Ready Software
• The Challenger Launch Decision
• Managing the Unexpected
• Berkley AMP Lab
• Berkeley Database Group
• Microsoft Systems Research
• Ricon
• Surge
• Velocity
• Resilience Engineering in Practice
• Life Beyond Distributed Transactions: An Apostate’s Opinion
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Observability at Twitter
• Twitter Research
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Observability at Twitter
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Chaos Monkey Released Into The Wild
• Fault Injection in Production
• Highly Available Transactions: Virtues and Limitations
• The Chubby Lock Service for Loosely Coupled Distributed Systems
• Weathering the Unexpected
• The Unified Logging Infrastructure for Data Analytics at Twitter
• Learning to Embrace Failure
• Dremel: Interactive Analysis of Web-Scale Datasets
• The Log-Structured Merge-Tree
• Failure Trends in a Large Disk Drive Population
• Fallacies of Distributed Computing Explained - Gal-Oz)
• F1 - The Fault-Tolerant Distributed RDBMS Supporting Google’s Ad Business
• Chaos Monkey Released Into The Wild
• Some Rules for Engineering and Operations
• Incuriosity Will Kill Your Infrastructure
• You Can’t Sacrifice Partition Tolerance
• The Field Guide To Understanding Human Error
• Agile Retrospectives: Making Good Teams Great
• The Challenger Launch Decision
• Fallacies of Distributed Computing Explained - Gal-Oz)
• Kafka: A Distributed Messaging System for Log Processing
• Design, Lessons, and Advice from Building Distributed Systems at Google
• Better: A Surgeon’s Notes on Performance
• The Checklist Manifesto: How to Get Things Right
• Resilience Engineering in Practice
• Release It!: Design and Deploy Production-Ready Software
• Managing the Unexpected
• Dynamo: Amazon’s Highly Available Key-Value Store
• Effective Monitoring and Alerting
• On HTTP Load Testing
• Bigtable: a Distributed Storage System for Structured Data
• Spanner: Google’s Globally-Distributed Database
• MapReduce: Simplified Data Processing on Large Clusters
• The Google File System
• On Designing and Deploying Internet Scale Services
• Dapper, A Large Scale Distributed Systems Tracing Infrastructure
• Resilience Engineering: Part I - engineering-part-ii-lenses/) (Allspaw)
• Systems Engineering: a Great Definition
• Customer Trust
• Observations on Errors, Corrections, & Trust of Dependent Systems
• Game Day Exercises at Stripe: Learning from `kill -9`
• The Network is Reliable
• The Trouble with Clocks
• Call Me Maybe: Final Thoughts
• Getting Real About Distributed Systems Reliability
• On HTTP Load Testing
• Service Design Best Practices
• High Performance Browser Networking
• Berkeley Database Group
• Microsoft Systems Research
• Monitorama
• Ricon