Architecting for Scale. How to Maintain High Availability and Manage Risk in the Cloud. 2nd Edition

Spis treści książki

• Forewords
  • Foreword for Second Edition
  • Foreword for First Edition
• Preface
  • Who Should Read This Book
  • Why I Wrote This Book
  • A Word on Scale Today
  • Whats New in the Second Edition
  • Using the Cloud
  • Services Versus Microservices
  • Modern Digital Customer Experiences
  • Navigating This Book
    • Tenet 1. Availability: Maintaining Availability in Modern Applications
    • Tenet 2. Modern Application Architecture: Using Services
    • Tenet 3. Organization: Scaling Your Organization for Modern Applications
    • Tenet 4. Risk: Risk Management for Modern Applications
    • Tenet 5. Cloud: Utilizing the Cloud
  • Online Resources
  • Conventions Used in This Book
  • OReilly Online Learning
  • How to Contact Us
  • Acknowledgments
• I. Tenet 1. Availability: Maintaining Availability in Modern Applications
• 1. Understanding, Measuring, and Improving Your Availability
  • Availability Versus Reliability
  • What Causes Poor Availability?
  • Measuring Availability
    • The Nines
    • Planned Outages Are Still Outages
    • Availability by the Numbers
  • Improving Your Availability When It Slips
    • Measure and Track Your Current Availability
    • Automate Your Manual Processes
      • Automated deploys
      • Configuration management
      • Change experiments and high frequency changes
      • Automated change sanity testing
    • Improve Your Systems
    • Keep on Top of Availability in Your Changing and Growing Application
  • Five Focuses to Improve Application Availability
    • Focus #1: Build with Failure in Mind
      • Design
      • Dependencies
      • Customers
    • Focus #2: Always Think About Scaling
    • Focus #3: Mitigate Risk
    • Focus #4: Monitor Availability
    • Focus #5: Respond to Availability Issues in a Predictable and Defined Way
  • Being Prepared
• 2. Two Mistakes HighHaving Room to Recover from Mistakes
  • Two Mistakes High
    • Scenario #1: Losing a Node
    • Scenario #2: Problems During Upgrades
    • Scenario #3: Data Center Resiliency
      • Then how many servers do you need?
    • Scenario #4: Hidden Shared Failure Types
    • Scenario #5: Failure Loops
  • Managing Your Applications
  • The Space Shuttle
• II. Tenet 2. Modern Application Architecture: Using Services
• 3. Using Services
  • The Monolith Application Versus the Service-Based Application
    • The Ownership Benefit
    • The Scaling Benefit
  • Splitting into Services
    • What Should Be a Service?
  • Dividing into Services
    • Guideline #1: Specific Business Requirements
    • Guideline #2: Distinct and Separable Team Ownership
      • Separate team for security reasons
    • Guideline #3: Naturally Separable Data
    • Guideline #4: Shared Capabilities/Data
    • Mixed Reasons
  • Going Too Far
  • Finding the Right Balance
• 4. Services and Data
  • Stateless ServicesServices Without Data
  • Stateful ServicesServices with Data
  • Data Partitioning
  • Timely Handling of Growing Pains
• 5. Dealing with Service Failures
  • Cascading Service Failures
  • Responding to a Service Failure
    • Predictable Response
    • Understandable Response
    • Reasonable Response
  • Determining Failures
  • Appropriate Action
    • Graceful Degradation
    • Graceful Backoff
    • Fail as Early as Possible
    • Customer-Caused Problems
      • Provide service limits
  • Summary
• III. Tenet 3. Organization: Scaling Your Organization for Modern Applications
• 6. Service OwnershipSTOSA
  • Single Team Owned Service Architecture
  • Advantages of a STOSA Application and Organization
  • What Does It Mean to Own a Service?
  • Using Core Teams and Services
  • Summary
• 7. Service Tiers
  • Application Complexity
  • What Are Service Tiers?
    • Assigning Service Tier Labels to Services
      • Tier 1
      • Tier 2
      • Tier 3
      • Tier 4
  • Example: Online Store
  • Using Service Tiers
    • Expectations
    • Responsiveness
    • Dependencies
      • Critical dependency
      • Noncritical dependency
  • Summary
• 8. Service-Level Agreements
  • What Are SLAs?
  • External Versus Internal SLAs
    • Why Are Internal SLAs Important?
      • SLAs as trust
  • SLAs for Problem Diagnosis
  • Performance Measurements for SLAs
    • Limit SLAs
    • Top Percentile SLAs
    • SLA Conditionals
  • How Many and Which Internal SLAs?
  • Why Internal SLAs Are Important
• IV. Tenet 4. Risk: Risk Management for Modern Applications
• 9. Using Risk Management When Architecting for Scale
  • Identify Risk
    • Remove Worst Offenders
    • Mitigate
    • Review Regularly
    • Managing Risk Summary
  • Likelihood Versus Severity
    • The Top 10 List: Low Likelihood, Low Severity Risk
    • The Order Database: Low Likelihood, High Severity Risk
    • Custom Fonts: High Likelihood, Low Severity Risk
    • T-Shirt Photos: High Likelihood, High Severity Risk
  • The Risk Matrix
    • Scope of the Risk Matrix
    • Creating the Risk Matrix
      • Brainstorming the list
      • Set the likelihood and severity fields
      • Risk item details
      • Mitigation plan
      • Triggered plan
    • Using the Risk Matrix for Planning
    • Maintaining the Risk Matrix
  • Risk Mitigation
  • Recovery Plans
  • Disaster Recovery Plans
  • Improving Our Risk Situation
• 10. Game Days
  • Staging Versus Production Environments
    • Staging/Test Environments
    • Production Environments
  • Concerns with Running Game Days in Production
  • Summary
• 11. Building Systems with Reduced Risk
  • Technique #1: Introduce Redundancy
    • Idempotent Interfaces
    • Redundancy Improvements That Increase Complexity
  • Technique #2: Understand Independence
  • Technique #3: Manage Security
  • Technique #4: Encourage Simplicity
  • Technique #5: Build in Self-Repair
  • Technique #6: Standardize on Operational Processes
  • Summary
• V. Tenet 5. Cloud: Utilizing the Cloud
• 12. Getting Started Architecting for Scale with the Cloud
  • Six Levels of Cloud Maturity
    • Level 1: Experimenting with the Cloud
    • Level 2: Securing the Cloud
    • Level 3: Using Servers and Applications in the Cloud
    • Level 4: Enabling Value-Added Managed Services
    • Level 5: Enabling Cloud-Unique Services
    • Level 6: Cloud All In
    • Organization Versus Application Maturity Level
  • Cloud Adoption Mistakes
    • Trap #1: Not Trusting Cloud Security
    • Trap #2: Performing Cloud Migration via Lift-and-Shift
    • Trap #3: The Lure of ServerlessDepending Too Much on the Hype
  • When and How to Use Multiple Clouds
    • Defining What We Mean by Multiple Clouds
      • Joint cloud applications
      • Selective cloud applications
      • Single cloud applications
    • Which Model? Which Cloud?
  • The Cloud in Summary
• 13. Five Industry Trends Changed by the Cloud
  • What Has Changed in the Cloud?
    • Change #1: Acceptance of Microservice-Based Architectures
    • Change #2: Smaller, More Specialized Cloud Services
    • Change #3: Greater Focus on the Application
    • Change #4: The Micro Startup
    • Change #5: Security and Compliance Has Matured
  • Change Continues
• 14. Types of SaaS and Tenancy
  • Comparing Managed Hosting and Different Types of SaaS
    • Managed Hosting
    • Multi-Tenant SaaS
    • Single-Tenant SaaS
  • Mixing Different Types of SaaS
  • Common SaaS Characteristics
  • SaaS Versus Managed Hosting
  • Summary
• 15. Distributing Your Application in the AWS Cloud
  • AWS Architecture
    • AWS Region
    • AWS Availability Zone
    • Data Center
  • Architecture Overview
  • Availability Zones Are Not Data Centers
  • Maintaining Location Diversity for Availability Reasons
    • AWSMapping Availability Zones in Multiple Accounts
  • Distributing Your Application
• 16. Managed Infrastructure
  • Structure of Cloud-Based Services
    • Raw Resource
      • Where you can see the impact of using raw resources
    • Server-Based Managed Resource
      • Where you can see the impact of using server-based managed resources
    • Serverless Managed Resource
      • Why serverless?
  • Implications of Using Managed Versus Non-Managed Resources
  • Summary
• 17. Cloud Resource Allocation
  • Usage-Based Resources Allocation
  • Allocated-Capacity Resource Allocation
    • Changing Allocations
    • Automated Allocation of Resource Capacity
    • Issues with Automatic Allocation
    • Dynamic Allocation, Dynamic Cost
      • Reserved capacity
  • Pros and Cons of Usage-Based Versus Allocated-Capacity
• 18. Serverless and Functions as a Service
  • Example Application #1: Event Processing
  • Example Application #2: Mobile Backend
  • Example Application #3: Internet of Things Data Intake
  • Advantages and Disadvantages of FaaS
  • Serverless Hype and the Future of FaaS
• 19. Edge Computing
  • Edge Computing Today
  • Why We Care
  • What Should Be in the Edge Versus the Cloud?
    • How Do We Decide? The Driverless Car
  • Edge Scaling Isnt the Same as Cloud Scaling
    • Criteria for Using Edge Versus Cloud
  • Eight Keys to Success in the Edge
    • #1: Be Smart About What Goes on the Edge
    • #2: Dont Ignore DevOps Principles in the Edge
    • #3: Nail a Highly Distributed Deployment Strategy
    • #4: Reduce Versioning as Much as Possible
    • #5: Reduce Per Node Provisioning and Configuration Options
    • #6: Scaling Is an Edge Issue, Not Just a Cloud Issue
    • #7: Nail Monitoring and Analytics
    • #8: The Edge Is Not Magic
  • Edge Computing Overall
• 20. Geographic Impact on Using the Cloud
  • Cloud Matters Everywhere, But at Different Levels
  • Replacement Mentality Impacts How You Adopt Cloud
  • Which Cloud Is Most Important?
  • Important Technologies Differ
  • Data Sovereignty Is Universal
  • My Take
• VI. Conclusion
• 21. Putting It All Together
  • Tenet #1Availability
  • Tenet #2Architecture
  • Tenet #3Organization
  • Tenet #4Risk
  • Tenet #5Cloud
  • Architecting for Scale
• Index

pokaż cały spis treści

ukryj recenzje