book

Designing Distributed Systems

by Brendan Burns

February 2018

Intermediate to advanced

162 pages

4h 8m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Who Should Read This BookWhy I Wrote This BookThe World of Distributed Systems TodayNavigating This BookConventions Used in This BookOnline ResourcesUsing Code ExamplesO’Reilly SafariHow to Contact UsAcknowledgments
A Brief History of Systems DevelopmentA Brief History of Patterns in Software DevelopmentFormalization of Algorithmic ProgrammingPatterns for Object-Oriented ProgrammingThe Rise of Open Source SoftwareThe Value of Patterns, Practices, and ComponentsStanding on the Shoulders of GiantsA Shared Language for Discussing Our PracticeShared Components for Easy ReuseSummary
MotivationsSummary
An Example Sidecar: Adding HTTPS to a Legacy ServiceDynamic Configuration with SidecarsModular Application ContainersHands On: Deploying the topz ContainerBuilding a Simple PaaS with SidecarsDesigning Sidecars for Modularity and ReusabilityParameterized ContainersDefine Each Container’s APIDocumenting Your ContainersSummary
Using an Ambassador to Shard a ServiceHands On: Implementing a Sharded RedisUsing an Ambassador for Service BrokeringUsing an Ambassador to Do Experimentation or Request SplittingHands On: Implementing 10% Experiments
MonitoringHands On: Using Prometheus for MonitoringLoggingHands On: Normalizing Different Logging Formats with FluentdAdding a Health MonitorHands On: Adding Rich Health Monitoring for MySQL
Introduction to Microservices
Stateless ServicesReadiness Probes for Load BalancingHands On: Creating a Replicated Service in KubernetesSession Tracked ServicesApplication-Layer Replicated ServicesIntroducing a Caching LayerDeploying Your CacheHands On: Deploying the Caching LayerExpanding the Caching LayerRate Limiting and Denial-of-Service DefenseSSL TerminationHands On: Deploying nginx and SSL TerminationSummary
Sharded CachingWhy You Might Need a Sharded CacheThe Role of the Cache in System PerformanceReplicated, Sharded CachesHands On: Deploying an Ambassador and Memcache for a Sharded CacheAn Examination of Sharding FunctionsSelecting a KeyConsistent Hashing FunctionsHands On: Building a Consistent HTTP Sharding ProxySharded, Replicated ServingHot Sharding Systems
Scatter/Gather with Root DistributionHands On: Distributed Document SearchScatter/Gather with Leaf ShardingHands On: Sharded Document SearchChoosing the Right Number of LeavesScaling Scatter/Gather for Reliability and Scale

Determining When FaaS Makes SenseThe Benefits of FaaSThe Challenges of FaaSThe Need for Background ProcessingThe Need to Hold Data in MemoryThe Costs of Sustained Request-Based ProcessingPatterns for FaaSThe Decorator Pattern: Request or Response TransformationHands On: Adding Request Defaulting Prior to Request ProcessingHandling EventsHands On: Implementing Two-Factor AuthenticationEvent-Based PipelinesHands On: Implementing a Pipeline for New-User Signup
Determining If You Even Need Master ElectionThe Basics of Master ElectionHands On: Deploying etcdImplementing LocksHands On: Implementing Locks in etcdImplementing OwnershipHands On: Implementing Leases in etcdHandling Concurrent Data Manipulation
A Generic Work Queue SystemThe Source Container InterfaceThe Worker Container InterfaceThe Shared Work Queue InfrastructureHands On: Implementing a Video ThumbnailerDynamic Scaling of the WorkersThe Multi-Worker Pattern
Patterns of Event-Driven ProcessingCopierFilterSplitterSharderMergerHands On: Building an Event-Driven Flow for New User Sign-UpPublisher/Subscriber InfrastructureHands On: Deploying Kafka
Join (or Barrier Synchronization)ReduceHands On: CountSumHistogramHands On: An Image Tagging and Processing Pipeline

Content preview from Designing Distributed Systems

Preface

Who Should Read This Book

At this point, nearly every developer is a developer or consumer (or both) of distributed systems. Even relatively simple mobile applications are backed with cloud APIs so that their data can be present on whatever device the customer happens to be using. Whether you are new to developing distributed systems or an expert with scars on your hands to prove it, the patterns and components described in this book can transform your development of distributed systems from art to science. Reusable components and patterns for distributed systems will enable you to focus on the core details of your application. This book will help any developer become better, faster, and more efficient at building distributed systems.

Why I Wrote This Book

Throughout my career as a developer of a variety of software systems from web search to the cloud, I have built a large number of scalable, reliable distributed systems. Each of these systems was, by and large, built from scratch. In general, this is true of all distributed applications. Despite having many of the same concepts and even at times nearly identical logic, the ability to apply patterns or reuse components is often very, very challenging. This forced me to waste time reimplementing systems, and each system ended up less polished than it might have otherwise been.

The recent introduction of containers and container orchestrators fundamentally changed the landscape of distributed system development. Suddenly ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Start your free trial

Designing Distributed Systems, 2nd Edition

Publisher Resources