Seeking SRE. Conversations About Running Production Systems at Scale
- Ocena:
- Bądź pierwszym, który oceni tę książkę
- Stron:
- 590
- Dostępne formaty:
-
ePubMobi
Opis ebooka: Seeking SRE. Conversations About Running Production Systems at Scale
Organizations big and small have started to realize just how crucial system and application reliability is to their business. They’ve also learned just how difficult it is to maintain that reliability while iterating at the speed demanded by the marketplace. Site Reliability Engineering (SRE) is a proven approach to this challenge.
SRE is a large and rich topic to discuss. Google led the way with Site Reliability Engineering, the wildly successful O’Reilly book that described Google’s creation of the discipline and the implementation that’s allowed them to operate at a planetary scale. Inspired by that earlier work, this book explores a very different part of the SRE space. The more than two dozen chapters in Seeking SRE bring you into some of the important conversations going on in the SRE world right now.
Listen as engineers and other leaders in the field discuss:
- Different ways of implementing SRE and SRE principles in a wide variety of settings
- How SRE relates to other approaches such as DevOps
- Specialties on the cutting edge that will soon be commonplace in SRE
- Best practices and technologies that make practicing SRE easier
- The important but rarely explored human side of SRE
David N. Blank-Edelman is the book’s curator and editor.
Wybrane bestsellery
-
Do you wish the existing books on site reliability engineering started at the beginning? Do you wish someone would walk you through how to become an SRE, how to think like an SRE, or how to build and grow a successful SRE function in your organization? Becoming SRE addresses all of these needs a...
Becoming SRE. First Steps Toward Reliability for You and Your Organization Becoming SRE. First Steps Toward Reliability for You and Your Organization
(143.65 zł najniższa cena z 30 dni)143.65 zł
169.00 zł(-15%) -
If you do systems administration work of any kind, you have to deal with the growing complexity of your environment and increasing demands on your time. Automating System Administration with Perl, Second Edition, not only offers you the right tools for your job, but also suggests the best way to ...
Automating System Administration with Perl. Tools to Make You More Efficient. 2nd Edition Automating System Administration with Perl. Tools to Make You More Efficient. 2nd Edition
(118.15 zł najniższa cena z 30 dni)118.15 zł
139.00 zł(-15%) -
Poznaj świat programowania w R, języku stworzonym z myślą o statystyce, analizie danych i wizualizacji. Ta kompleksowa książka poprowadzi Cię krok po kroku od zupełnych podstaw aż po zaawansowane techniki, wszystko to w ciągu jednego dnia. Oto, czego się nauczysz: Podstawy języka R: Zrozumi...
Język R w jeden dzień. R od podstaw, po zaawansowane techniki Język R w jeden dzień. R od podstaw, po zaawansowane techniki
-
Język Python został ostatnio sklasyfikowany w indeksie TIOBE jako najpopularniejszy obecnie język programowania, co zawdzięcza szerokim możliwościom stosowania go w projektowaniu, prototypowaniu, testach, wdrażaniu i konserwacji oprogramowania. To zaktualizowane i rozszerzone czwarte wydanie poka...
Python w pigułce. Podręczny przewodnik po wersjach 3.10 i 3.11 Python w pigułce. Podręczny przewodnik po wersjach 3.10 i 3.11
Alex Martelli, Anna Martelli Ravenscroft, Steve Holden, Paul McGuire
(152.10 zł najniższa cena z 30 dni)152.10 zł
169.00 zł(-10%) -
Dzięki tej książce dowiesz się, w jaki sposób uczynić architekturę oprogramowania wystarczająco plastyczną, aby mogła odzwierciedlać zachodzące zmiany biznesowe i technologiczne. W nowym wydaniu rozbudowano pojęcia zmiany kierowanej i przyrostowej, a także przedstawiono najnowsze techniki dotyczą...
Architektura ewolucyjna. Projektowanie oprogramowania i wsparcie zmian. Wydanie II Architektura ewolucyjna. Projektowanie oprogramowania i wsparcie zmian. Wydanie II
(43.55 zł najniższa cena z 30 dni)46.90 zł
67.00 zł(-30%) -
Język modelowania UML i będące jego częścią diagramy UML odgrywają ważną rolę w inżynierii oprogramowania. Stanowią komunikacyjny pomost podczas pracy zespołowej i w kontaktach zarówno z menedżerami, jak i klientami biznesowymi, niekoniecznie zorientowanymi w procesach projektowych i deweloperski...
UML. Kurs video. Projektowanie diagramów i modelowanie systemów w teorii i praktyce UML. Kurs video. Projektowanie diagramów i modelowanie systemów w teorii i praktyce
(58.04 zł najniższa cena z 30 dni)83.85 zł
129.00 zł(-35%) -
Głębokie sieci neuronowe mają niesamowity potencjał. Osiągnięcia ostatnich lat nadały procesom uczenia głębokiego zupełnie nową jakość. Obecnie nawet programiści niezaznajomieni z tą technologią mogą korzystać z prostych i niezwykle skutecznych narzędzi, pozwalających na sprawne implementowanie p...
Uczenie maszynowe z użyciem Scikit-Learn, Keras i TensorFlow. Wydanie III Uczenie maszynowe z użyciem Scikit-Learn, Keras i TensorFlow. Wydanie III
(116.35 zł najniższa cena z 30 dni)125.30 zł
179.00 zł(-30%) -
Tę książkę docenią programiści, menedżerowie, inżynierowie i liderzy techniczni. Znajdziesz w niej cenne informacje o filozofii inżynierii oprogramowania, jak również o postępach w sposobie myślenia na jej temat. Na tej bazie oparto zestaw zasad ułatwiających skuteczne radzenie sobie z dwoma pods...
Nowoczesna inżynieria oprogramowania. Stosowanie skutecznych technik szybszego rozwoju oprogramowania wyższej jakości Nowoczesna inżynieria oprogramowania. Stosowanie skutecznych technik szybszego rozwoju oprogramowania wyższej jakości
(44.85 zł najniższa cena z 30 dni)48.30 zł
69.00 zł(-30%) -
To nie jest podręcznik dla programistów. Celem autorów jest zaprezentowanie jedynej w swoim rodzaju perspektywy firmy Google, od lat rozwijającej trwały ekosystem oprogramowania, co pozwoliło zebrać pożyteczne wnioski dotyczące skali działalności i czasu jej trwania. W książce zwrócono uwagę na t...
Inżynieria oprogramowania według Google. Czego warto się nauczyć o tworzeniu oprogramowania Inżynieria oprogramowania według Google. Czego warto się nauczyć o tworzeniu oprogramowania
(83.85 zł najniższa cena z 30 dni)90.30 zł
129.00 zł(-30%) -
Ta książka zawiera opis podstawowych wzorców, zasad i praktyk przydatnych podczas analizy dziedzin biznesowych, ułatwiających zrozumienie ich strategii i dostosowanie architektury do potrzeb biznesu, aby umożliwić zbudowanie solidnej implementacji logiki biznesowej. Omówiono tu narzędzia i techni...
Koncepcja Domain-Driven Design. Dostosowywanie architektury aplikacji do strategii biznesowej Koncepcja Domain-Driven Design. Dostosowywanie architektury aplikacji do strategii biznesowej
(51.35 zł najniższa cena z 30 dni)55.30 zł
79.00 zł(-30%)
Ebooka "Seeking SRE. Conversations About Running Production Systems at Scale" przeczytasz na:
-
czytnikach Inkbook, Kindle, Pocketbook, Onyx Boox i innych
-
systemach Windows, MacOS i innych
-
systemach Windows, Android, iOS, HarmonyOS
-
na dowolnych urządzeniach i aplikacjach obsługujących formaty: PDF, EPub, Mobi
Masz pytania? Zajrzyj do zakładki Pomoc »
Audiobooka "Seeking SRE. Conversations About Running Production Systems at Scale" posłuchasz:
-
w aplikacji Ebookpoint na Android, iOS, HarmonyOs
-
na systemach Windows, MacOS i innych
-
na dowolnych urządzeniach i aplikacjach obsługujących format MP3 (pliki spakowane w ZIP)
Masz pytania? Zajrzyj do zakładki Pomoc »
Kurs Video "Seeking SRE. Conversations About Running Production Systems at Scale" zobaczysz:
-
w aplikacjach Ebookpoint i Videopoint na Android, iOS, HarmonyOs
-
na systemach Windows, MacOS i innych z dostępem do najnowszej wersji Twojej przeglądarki internetowej
Szczegóły ebooka
- ISBN Ebooka:
- 978-14-919-7881-8, 9781491978818
- Data wydania ebooka:
- 2018-08-21 Data wydania ebooka często jest dniem wprowadzenia tytułu do sprzedaży i może nie być równoznaczna z datą wydania książki papierowej. Dodatkowe informacje możesz znaleźć w darmowym fragmencie. Jeśli masz wątpliwości skontaktuj się z nami sklep@ebookpoint.pl.
- Język publikacji:
- angielski
- Rozmiar pliku ePub:
- 11.9MB
- Rozmiar pliku Mobi:
- 25.7MB
Spis treści ebooka
- Introduction
- And So It Begins...
- Origin Story
- Voices
- Forward in All Directions!1
- Acknowledgments
- I. SRE Implementation
- 1. Context Versus Control in SRE
- 2. Interviewing Site Reliability Engineers
- Interviewing 101
- Who Is Involved
- Industry Versus University
- Biases
- The Funnel
- Interviewing 101
- SRE Funnels
- Phone Screens
- Conducting a phone screen
- Phone Screens
- The Onsite Interview
- Coding and system questions
- Deep dives and architecture questions
- Cultural interviews
- Take-Home Questions
- Advice for Hiring Managers
- Selling candidates
- Walking away
- Final Thoughts on Interviewing SREs
- Further Reading
- 3. So, You Want to Build an SRE Team?
- Choose SRE for the Right Reasons
- Orienting to a Data-Driven Approach
- Commitment to SRE
- Making a Decision About SRE
- 4. Using Incident Metrics to Improve SRE at Scale
- The Virtuous Cycle to the Rescue: If You Dont Measure It
- Metrics Review: If a Metric Falls in the Forest
- Surrogate Metrics
- Repair Debt
- Virtual Repair Debt: Exorcising the Ghost in the Machine
- Real-Time Dashboards: The Bread and Butter of SRE
- Learnings: TL;DR
- Further Reading
- 5. Working with Third Parties Shouldnt Suck
- Build, Buy, or Adopt?
- Establish Importance
- Identify Stakeholders
- Make a Decision
- Acknowledge Reality
- Is this a core competency?
- Integration timeline?
- Project Operating Expense and Abandonment Expense
- Build, Buy, or Adopt?
- Third Parties as First-Class Citizens
- When Theyre Down, Youre Down
- Direct impact
- Indirect impact
- When Theyre Down, Youre Down
- Running the Black Box Like a Service
- Service-Level Indicators, Service-Level Objectives, and SLAs
- SLIs on black boxes
- Polling API informs SLIs
- Real-time data informs SLIs
- Synthetic monitoring informs SLIs
- RUM informs SLIs
- SLIs on black boxes
- SLOs
- Negotiating SLAs with vendors
- Playbook: From Staging to Production
- Testing and staging
- Monitoring
- Uses for synthetic monitoring
- Uses for RUM
- Tooling
- Automation
- Logging
- Disaster planning
- Communication
- Decommissioning
- Closing Thoughts
- 6. How to Apply SRE Principles Without Dedicated SRE Teams
- SREs to the Rescue! (and How They Failed)
- A Matter of Scale in Terms of Headcount
- The Embedded SRE
- SREs to the Rescue! (and How They Failed)
- You Build It, You Run It
- The Deployment Platform
- Closing the Loop: Take Your Own Pager
- Introducing Production Engineering
- Some Implementation Details
- Developers Productivity and Health Versus the Pager
- Resolving Cross-Team Reliability Issues by Using Postmortems
- Uniform Infrastructure and Tooling Versus Autonomy and Innovation
- Getting Buy-In
- Conclusion
- Further Reading
- 7. SRE Without SRE: The Spotify Case Study
- Tabula Rasa: 20062007
- Prelude
- Key Learnings
- Tabula Rasa: 20062007
- Beta and Release: 20082009
- Prelude
- Bringing Scalability and Reliability to the Forefront
- Key Learnings
- The Curse of Success: 2010
- Prelude
- A New Ownership Model
- The dev owner role
- The ops owner role
- Formalizing Core Services
- Blessed Deployment Time Slots
- On-Call and Alerting
- Not completely pain-free
- Spawning Off Internal Office Support
- Addressing the Remaining Top Concerns
- Long lead times
- Unintentional specialization and misalignment
- Interruptions
- Introducing the goalie role
- Creating Detectives
- Key Learnings
- Pets and Cattle, and Agile: 2011
- Prelude
- Forming Bad Habits
- Breaking Those Bad Habits
- Key Learnings
- A System That Didnt Scale: 2012
- Prelude
- Manual Work Hits a Cliff
- Key Learnings
- Introducing Ops-in-Squads: 20132015
- Prelude
- Lightening the manual load
- Prelude
- Building on Trust
- Driving the Paradigm Shift
- Key Learnings
- Autonomy Versus Consistency: 20152017
- Prelude
- Benefits
- Trade-Offs
- Key Learnings
- The Future: Speed at Scale, Safely
- 8. Introducing SRE in Large Enterprises
- Background
- Introducing SRE
- Defining Current State
- Start by defining the roles and responsibilities of traditional functions in the organization to understand the landscape
- Prepare the business case: personalize and evaluate the cost of having engineering resources responsible for reliability
- Prepare the business case: calculate cost of similar resources doing duplicate work
- To establish a roadmap for what products SRE will be responsible for, survey the current infrastructure landscape
- Defining Current State
- Identifying and Educating Stakeholders
- Start having conversations with leaders and champions in the organization
- Defining SRE
- Presenting the Business Case
- Implementing the SRE Team
- Setting goals and defining metrics of success
- Growing the team: insource or outsource?
- Insourcing experienced talent: rotating engineering team members
- SRE throughout the development cycle
- Defining the role of supporting divisions
- Lessons Learned
- Sample Implementation Roadmap
- Closing Thoughts
- Further Reading
- 9. From SysAdmin to SRE in 8,963 Words
- Clarifying Terminology
- Service-Level Indicator
- SLA
- Service-Level Objective
- Clarifying Terminology
- Establishing SLAs for Internal Components
- Understanding External Dependencies
- Nontechnical Solutions
- Tracking Availability Level
- Dealing with Corner Cases
- Conclusion
- 10. Clearing the Way for SRE in the Enterprise
- Toil, the Enemy of SRE
- Toil in the Enterprise
- Silos, Queues, and Tickets
- Silos Get in the Way
- Ticket-Driven Request Queues Are Expensive
- Take Action Now
- Start by Leaning on Lean
- Get Rid of as Many Handoffs as Possible
- Replace Remaining Handoffs with Self-Service
- Self-Service Is More Than a Button
- Self-Service Helps SREs in Multiple Ways
- Operations as a Service
- Error Budgets, Toil Limits, and Other Tools for Empowering Humans
- Error Budgets
- Toil Limits
- Leverage Existing Enthusiasm for DevOps
- Unify Backlogs and Protect Capacity
- Psychological Safety and Human Factors
- Join the Movement
- 11. SRE Patterns Loved by DevOps People Everywhere
- Pattern 1: Birth of Automated Testing at Google
- Pattern 2: Launch and Handoff Readiness Review at Google
- Pattern 3: Create a Shared Source Code Repository
- Conclusion
- Further Reading and Source Material
- 12. DevOps and SRE: Voices from the Community
- Background
- Method
- Results
- Replies
- 13. Production Engineering at Facebook
- II. Near Edge SRE
- 14. In the Beginning, There Was Chaos
- The Problem with Systems
- Economic Pillars of Complexity
- Beginning Chaos
- Navigating Complexity for Safety
- Chaos Goes Big
- Formalization
- Advanced Principles
- Frequently Asked Questions
- Conclusion
- 15. The Intersection of Reliability and Privacy
- The Intersection of Reliability and Privacy
- The General Landscape of Privacy Engineering
- Privacy and SRE: Common Approaches
- Reducing Toil
- Automation
- Default behavior for shared architectures
- Frameworks
- Reducing Toil
- Efficient and Deliberate Problem Solving
- Solve challenges once
- Find and address root causes
- Relationship Management
- Early Intervention and Education Through Evangelism
- Nuances, Differences, and Trade-Offs
- Conclusion
- Further Reading
- 16. Database Reliability Engineering
- Guiding Principles of the Database Reliability Engineer
- Protect the Data
- Self-Service for Scale
- Databases Are Not Special
- Guiding Principles of the Database Reliability Engineer
- A Culture of Database Reliability Engineering
- Recoverability
- Considerations for Recovery
- Anatomy of a Recovery Strategy
- Building Block 1: Detection
- User error
- Application errors
- Infrastructure services
- Operating system and hardware errors
- Building Block 2: Diverse Storage
- Online, high-performance storage
- Online, low-performance storage
- Offline storage
- Object storage
- Building Block 3: A Varied Toolbox
- Full physical backups
- Incremental physical backups
- Full and incremental logical backups
- Object stores
- Building Block 4: Testing
- Championing Recovery Reliability
- Continuous Delivery: From Development to Production
- Education and Collaboration
- Architecture
- Data model
- Best practices and standards
- Tools
- Education and Collaboration
- Collaboration
- Deployment
- Migrations and Versioning
- Impact Analysis
- Migration Patterns
- Migration testing
- Rollback testing
- Championing CD
- Making the Case for DBRE
- Further Reading
- 17. Engineering for Data Durability
- Replication Is Table Stakes
- Backups
- Restoration
- Freshness
- Backups
- Replication
- Estimating durability
- Replication Is Table Stakes
- Real-World Durability
- Isolation
- Physical isolation
- Logical isolation
- Operational isolation
- Isolation
- Protection
- Testing
- Safeguards
- Recovery
- Verification
- The Power of Zero
- Verification Coverage
- Disk Scrubber
- Index Scanner
- Storage Watcher
- Watching the Watchers
- Automation
- Window of Vulnerability
- Operator Fatigue
- Reliability
- Conclusion
- 18. Introduction to Machine Learning for SRE
- Why Use Machine Learning for SRE?
- Why and How Should My Company Be Engaging in This?
- Some SRE Problems Machine Learning Can Help Solve
- The Awakening of Applied AI
- What Is Machine Learning?
- What Do We Mean by Learning?
- From Chess to Go: How Deep Can We Dive?
- Why Now? What Changed for Us?
- What Are Neural Networks?
- Neurons and Neural Networks
- How and When Should We Apply Neural Networks?
- What Kinds of Data Can We Use?
- Practical Machine Learning
- Popular Libraries for Neural Networks
- Practical Machine Learning Examples
- Installing Python, IPython, and Jupyter Notebook
- Decision trees
- A neural network from scratch
- Using TensorFlow and TensorBoard
- Time series: server requests waiting
- Success Stories
- Further Reading
- My GitHub Repository
- Recommended Books
- III. SRE Best Practices and Technologies
- 19. Do Docs Better: Integrating Documentation into the Engineering Workflow
- Defining Quality: What Do Good Docs Look Like?
- Functional Requirements for SRE Documentation
- Service overviews
- Playbooks
- Postmortems
- Policies
- SLAs
- Defining success metrics
- Functional Requirements for SRE Documentation
- Defining Quality: What Do Good Docs Look Like?
- Integrating Docs into the Engineering Workflow
- The Google Experience: g3doc and EngPlay
- What We Learned
- Where possible, documentation should live in source control, alongside its associated code
- Pick the simplest markup language that supports your needs
- Integrations are key to adoption
- Doing Docs Better: Best Practices
- Create Templates for Each Documentation Type
- Better > Best: Set Realistic Standards for Quality
- Require Docs as Part of Code Review
- Ruthlessly Prune Your Docs
- Recognize and Reward Documentation
- Communicating the Value of Documentation
- Further Reading
- 20. Active Teaching and Learning
- Active Learning
- Active Learning Example: Wheel of Misfortune
- Active Learning Example: Incident Manager (a Card Game)
- Active Learning Example: SRE Classroom
- Active Learning
- The Costs of Failing to Learn
- Learning Habits of Effective SRE Teams
- Production Meetings
- Postmortems
- A Call to Action: Ditch the Boring Slides
- 21. The Art and Science of the Service-Level Objective
- Why Set Goals?
- Availability
- Time Quanta
- Transactions
- Transactions over Time Quanta
- On Evaluating SLOs
- Histograms
- Where Percentiles Fall Down (and Histograms Step Up)
- Parting Thought: Looking at SLOs Upside Down
- Further Reading
- 22. SRE as a Success Culture
- Where Did SRE Come From?
- Key Values for SRE
- Keeping the Site Up
- Isolated failure domains
- Redundant systems
- Graduated degradation
- Keeping the Site Up
- Empowering Teams to Do the Right Thing
- Approaching Operations as an Engineering Problem
- Achieving Business Success Through Promises (Service Levels)
- Progression in Service-Level Execution
- Critical Enabling Functions of SRE
- Monitoring, Metrics, and KPIs
- Incident Management and Emergency Response
- Capacity Planning and Demand Forecasting
- Performance Analysis and Optimization
- Provisioning, Change Management, and Velocity
- Phases of SRE Execution
- Phase 1: Firefighting/Reactive
- Phase 2: Gatekeepers
- Phase 3: Advocates/Partners
- Phase 4: Catalytic
- Complications of Differing Phases
- Focus on the Details of Success
- Further Reading
- 23. SRE Antipatterns
- Antipattern 1: Site Reliability Operations
- Antipattern 2: Humans Staring at Screens
- Antipattern 3: Mob Incident Response
- Antipattern 4: Root Cause = Human Error
- Antipattern 5: Passing the Pager
- Antipattern 6: Magic Smoke Jumping!
- Antipattern 7: Alert Reliability Engineering
- Antipattern 8: Hiring a Dog-Walker to Tend Your Pets
- Antipattern 9: Speed-Bump Engineering
- Antipattern 10: Design Chokepoints
- Antipattern 11: Too Much Stick, Not Enough Carrot
- Antipattern 12: Postponing Production
- Antipattern 13: Optimizing Failure Avoidance Rather Than Recovery Time (MTTF > MTTR)
- Antipattern 14: Dependency Hell
- Antipattern 15: Ungainly Governance
- Antipattern 16: Ill-Considered SLOh-Ohs
- Antipattern 17: Tossing Your API Over the Firewall
- Antipattern 18: Fixing the Ops Team
- So, Thats It, Then?
- 24. Immutable Infrastructure and SRE
- Scalability, Reliability, and Performance
- Failure Recovery
- Simpler Operations
- Faster Startup Times
- Known State
- Continuous Integration/Continuous Deployment with Confidence
- Security
- Multiregion Operations
- Release Engineering
- Building the Base Image
- Deploying Applications
- Disadvantages
- Conclusion
- 25. Scriptable Load Balancers
- Scriptable Load Balancers: The New Kid on the Block
- Why Scriptable Load Balancers?
- Scriptable Load Balancers: The New Kid on the Block
- Making the Difficult Easy
- Shard-Aware Routing
- Routing requests with DNS
- Routing queries in the application
- Routing requests in the application
- Routing requests with a scriptable load balancer
- Shard-Aware Routing
- Harnessing Potential
- Case Study: Intermission
- Service-Level Middleware
- Middleware to the Rescue
- APIs of Service-Level Middleware
- Case Study: WAF/Bot Mitigation
- Avoiding Disaster
- Getting Clever with State
- Case Study: Checkout Queue
- Looking to the Future and Further Reading
- 26. The Service Mesh: Wrangler of Your Microservices?
- Ready to Get Rid of the Monolith?
- Current State of Microservice Networking
- Service Mesh to the Rescue
- The Benefits of a Sidecar Proxy
- Eventually Consistent Service Discovery
- Observability and Alarming
- Sidecar Performance Implications
- Thin Libraries and Context Propagation
- Configuration Management (Control Plane Versus Data Plane)
- The Service Mesh in Practice
- The Origin and Development of Envoy at Lyft
- Operating Envoy at Lyft
- Operational learnings
- Development learnings
- Technical learnings
- The Future of the Service Mesh
- Further Reading
- IV. The Human Side of SRE
- 27. Psychological Safety in SRE
- The Primary Indicator of a Successful Team
- How to Build Psychological Safety into Your Own Team
- Make respect part of your teams culture
- Make space for people to take chances
- Make it obvious when your team is doing well
- Make your communication clear and your expectations explicit
- Make your team feel safe
- Why are operations teams more likely to feel unsafe than other engineering teams?
- We love interrupts and the torrents of information
- On-call and operations
- Cognitive overload
- Imaginary expectations
- Operations teams are bad at estimating their level of psychological safety
- How to Build Psychological Safety into Your Own Team
- The Primary Indicator of a Successful Team
- Further Reading
- 28. SRE Cognitive Work
- Introduction
- What Do SRE People Do?
- Why Should We Care About Practitioner Cognition?
- Critical Decisions Made Under Uncertainty and Time Pressure Cannot Be Scripted
- Human Performance in Modern Complex Systems: The Main Themes
- Observations on SRE Cognitive Work Around Incidents
- Every Incident Could Have Been Worse
- Sacrifice Decisions Take Place Under Uncertainty
- Repairs to Functional Systems
- Special Knowledge About Complex Systems
- Managing the Costs of Coordination
- Classification schemes
- Formal role assignments
- SREs Are Cognitive Agents Working in a Joint Cognitive System
- The Calibration Problem
- Mental Models
- Incidents Trigger Individual Recalibration
- Incidents Are Opportunities for Collective Recalibration
- What Are the Implications of All This?
- Incidents Will Continue
- Incidents Will Impose Costs
- Incident Patterns Will Change
- Incidents Point to Specific Calibration Problems and Locations
- What Should Happen Next?
- Build a Corpus of Cases
- Focus on Making Automation a Team Player in SRE Work
- Address the Calibration Problem
- What Can You Do?
- Conclusion
- References
- 29. Beyond Burnout
- Defining Mental Disorders
- Mental Disorders Are Missing from the Diversity Conversation
- Sanity Isnt a Business Requirement
- Thoughts and Prayers Arent Scalable
- Full-Stack Inclusivity
- Application
- Interviewing
- Compensation
- Benefits
- Onboarding
- Working Conditions
- Job Duties
- Training
- Promotion
- Leaving
- Inclusivity for Anyone Helps Everyone
- Mental Disorder Resources
- 30. Against On-Call: A Polemic
- The Rationale for On-Call
- First, Do No Harm
- Parallels with SRE
- Differences with SRE
- Underlying Assumptions Driving On-Call for Engineers
- On-Call Is Emergency Medicine Instead of Ward Medicine
- Counterarguments
- The Rationale for On-Call
- The Cost to Humans of Doing On-Call
- We dont need another hero
- Actual Solutions
- Training
- Prioritization
- Accommodations
- Compensation
- Flexible schedules
- Recovery
- Exclusion backlash
- Improving On-the-Job Performance
- Cognitive hacks
- We Need a Fundamental Change in Approach
- Strong-Anti-On-Call
- Weak-Anti-On-Call
- A Union of the Two
- Conclusion
- 31. Elegy for Complex Systems
- The Computer and Human Systems Cannot Be Separated
- Decoherence and Cascading Failure
- Always in a State of Partial Failure
- Novelty Priority Inversion
- Nobody Anticipates the Overhead of Coordination
- Your healthcare.gov Is Out There
- To Get Involved
- Further Reading
- 32. Intersections Between Operations and Social Activism
- Before, During, After
- Creating the Perfect Plan
- Principles of Organizing
- Principles 1 and 2 (interfaces and incident command)
- Principles 3 and 4 (blameless retrospectives and psychological safety)
- Managing Crisis: Responding When Things Break Down
- Handling chaos: contrast in responses during the July 8 KKK rally
- Preparing for the worst: handling terror at Unite the Right
- The corollary to trust is forgiveness
- Before, During, After
- Writing Our Own History: Making Sense of What Went Down
- Charlottesville in review: assigning and avoiding blame
- Beyond culpability: building capacity instead of assigning blame
- The Long Tail: Turning Action into Change
- Activism and Change Within a Company
- Conclusion
- 33. Conclusion
- Index
O'Reilly Media - inne książki
-
Software as a service (SaaS) is on the path to becoming the de facto model for building, delivering, and operating software solutions. Adopting a multi-tenant SaaS model requires builders to take on a broad range of new architecture, implementation, and operational challenges. How data is partiti...(237.15 zł najniższa cena z 30 dni)
245.65 zł
289.00 zł(-15%) -
Great engineers don't necessarily make great leaders—at least, not without a lot of work. Finding your path to becoming a strong leader is often fraught with challenges. It's not easy to figure out how to be strategic, successful, and considerate while also being firm. Whether you're on the...(126.65 zł najniższa cena z 30 dni)
126.65 zł
149.00 zł(-15%) -
Data science happens in code. The ability to write reproducible, robust, scaleable code is key to a data science project's success—and is absolutely essential for those working with production code. This practical book bridges the gap between data science and software engineering,and clearl...(211.65 zł najniższa cena z 30 dni)
211.65 zł
249.00 zł(-15%) -
With the massive adoption of microservices, operators and developers face far more complexity in their applications today. Service meshes can help you manage this problem by providing a unified control plane to secure, manage, and monitor your entire network. This practical guide shows you how th...(203.15 zł najniższa cena z 30 dni)
203.15 zł
239.00 zł(-15%) -
Get practical advice on how to leverage AI development tools for all stages of code creation, including requirements, planning, design, coding, debugging, testing, and documentation. With this book, beginners and experienced developers alike will learn how to use a wide range of tools, from gener...(164.25 zł najniższa cena z 30 dni)
186.15 zł
219.00 zł(-15%) -
Rust's popularity is growing, due in part to features like memory safety, type safety, and thread safety. But these same elements can also make learning Rust a challenge, even for experienced programmers. This practical guide helps you make the transition to writing idiomatic Rust—while als...(164.25 zł najniższa cena z 30 dni)
186.15 zł
219.00 zł(-15%) -
Advance your Power BI skills by adding AI to your repertoire at a practice level. With this practical book, business-oriented software engineers and developers will learn the terminologies, practices, and strategy necessary to successfully incorporate AI into your business intelligence estate. Je...(211.65 zł najniższa cena z 30 dni)
211.65 zł
249.00 zł(-15%) -
Microservices can be a very effective approach for delivering value to your organization and to your customers. If you get them right, microservices help you to move fast by making changes to small parts of your system hundreds of times a day. But if you get them wrong, microservices will just ma...(203.15 zł najniższa cena z 30 dni)
203.15 zł
239.00 zł(-15%) -
JavaScript gives web developers great power to create rich interactive browser experiences, and much of that power is provided by the browser itself. Modern web APIs enable web-based applications to come to life like never before, supporting actions that once required browser plug-ins. Some are s...(186.15 zł najniższa cena z 30 dni)
186.15 zł
219.00 zł(-15%) -
How will software development and operations have to change to meet the sustainability and green needs of the planet? And what does that imply for development organizations? In this eye-opening book, sustainable software advocates Anne Currie, Sarah Hsu, and Sara Bergman provide a unique overview...(169.14 zł najniższa cena z 30 dni)
169.14 zł
199.00 zł(-15%)
Dzieki opcji "Druk na żądanie" do sprzedaży wracają tytuły Grupy Helion, które cieszyły sie dużym zainteresowaniem, a których nakład został wyprzedany.
Dla naszych Czytelników wydrukowaliśmy dodatkową pulę egzemplarzy w technice druku cyfrowego.
Co powinieneś wiedzieć o usłudze "Druk na żądanie":
- usługa obejmuje tylko widoczną poniżej listę tytułów, którą na bieżąco aktualizujemy;
- cena książki może być wyższa od początkowej ceny detalicznej, co jest spowodowane kosztami druku cyfrowego (wyższymi niż koszty tradycyjnego druku offsetowego). Obowiązująca cena jest zawsze podawana na stronie WWW książki;
- zawartość książki wraz z dodatkami (płyta CD, DVD) odpowiada jej pierwotnemu wydaniu i jest w pełni komplementarna;
- usługa nie obejmuje książek w kolorze.
Masz pytanie o konkretny tytuł? Napisz do nas: sklep[at]helion.pl.
Książka, którą chcesz zamówić pochodzi z końcówki nakładu. Oznacza to, że mogą się pojawić drobne defekty (otarcia, rysy, zagięcia).
Co powinieneś wiedzieć o usłudze "Końcówka nakładu":
- usługa obejmuje tylko książki oznaczone tagiem "Końcówka nakładu";
- wady o których mowa powyżej nie podlegają reklamacji;
Masz pytanie o konkretny tytuł? Napisz do nas: sklep[at]helion.pl.
Książka drukowana
Oceny i opinie klientów: Seeking SRE. Conversations About Running Production Systems at Scale David N. Blank-Edelman (0) Weryfikacja opinii następuję na podstawie historii zamówień na koncie Użytkownika umieszczającego opinię. Użytkownik mógł otrzymać punkty za opublikowanie opinii uprawniające do uzyskania rabatu w ramach Programu Punktowego.