book

Production-Ready Microservices

by Susan J. Fowler

November 2016

Intermediate to advanced

172 pages

5h 5m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Who This Book Is Written ForWhat This Book Is NotHow To Use This BookHow This Book Is StructuredConventions Used in This BookO’Reilly SafariHow to Contact UsAcknowledgments
From Monoliths to MicroservicesMicroservice ArchitectureThe Microservice EcosystemLayer 1: HardwareLayer 2: CommunicationLayer 3: The Application PlatformLayer 4: MicroservicesOrganizational ChallengesThe Inverse Conway’s LawTechnical SprawlMore Ways to FailCompetition for Resources
The Challenges of Microservice StandardizationAvailability: The Goal of StandardizationProduction-Readiness StandardsStabilityReliabilityScalabilityFault Tolerance and Catastrophe-PreparednessPerformanceMonitoringDocumentationImplementing Production-Readiness
Principles of Building Stable and Reliable MicroservicesThe Development CycleThe Deployment PipelineStagingCanaryProductionEnforcing Stable and Reliable DeploymentDependenciesRouting and DiscoveryDeprecation and DecommissioningEvaluate Your MicroserviceThe Development CycleThe Deployment PipelineDependenciesRouting and DiscoveryDeprecation and Decommissioning
Principles of Microservice Scalability and PerformanceKnowing the Growth ScaleThe Qualitative Growth ScaleThe Quantitative Growth ScaleEfficient Use of ResourcesResource AwarenessResource RequirementsResource BottlenecksCapacity PlanningDependency ScalingTraffic ManagementTask Handling and ProcessingProgramming Language LimitationsHandling Requests and Processing Tasks EfficientlyScalable Data StorageDatabase Choice in Microservice EcosystemsDatabase Challenges in Microservice ArchitectureEvaluate Your MicroserviceKnowing the Growth ScaleEfficient Use of ResourcesResource AwarenessCapacity PlanningDependency ScalingTraffic ManagementTask Handling and ProcessingScalable Data Storage
Principles of Building Fault-Tolerant MicroservicesAvoiding Single Points of FailureCatastrophes and Failure ScenariosCommon Failures Across an EcosystemHardware FailuresCommunication-Level and Application Platform–Level FailuresDependency FailuresInternal (Microservice) FailuresResiliency TestingCode TestingLoad TestingChaos TestingFailure Detection and RemediationIncidents and OutagesAppropriate CategorizationThe Five Stages of Incident ResponseEvaluate Your MicroserviceAvoiding Single Points of FailureCatastrophes and Failure ScenariosResiliency TestingFailure Detection and Remediation
Principles of Microservice MonitoringKey MetricsLoggingDashboardsAlertingSetting up Effective AlertingHandling AlertsOn-Call RotationsEvaluate Your MicroserviceKey MetricsLoggingDashboardsAlertingOn-Call Rotations
Principles of Microservice Documentation and UnderstandingMicroservice DocumentationDescriptionArchitecture DiagramContact and On-Call InformationLinksOnboarding and Development GuideRequest Flows, Endpoints, and DependenciesOn-Call RunbooksFAQMicroservice UnderstandingArchitecture ReviewsProduction-Readiness AuditsProduction-Readiness RoadmapsProduction-Readiness AutomationEvaluate Your MicroserviceMicroservice DocumentationMicroservice Understanding
A Production-Ready Service Is Stable and ReliableA Production-Ready Service Is Scalable and PerformantA Production-Ready Service Is Fault Tolerant and Prepared for Any CatastropheA Production-Ready Service Is Properly MonitoredA Production-Ready Service Is Documented and Understood
Stability and ReliabilityThe Development CycleThe Deployment PipelineDependenciesRouting and DiscoveryDeprecation and DecommissioningScalability and PerformanceKnowing the Growth ScaleEfficient Use of ResourcesResource AwarenessCapacity PlanningDependency ScalingTraffic ManagementTask Handling and ProcessingScalable Data StorageFault Tolerance and Catastrophe-PreparednessAvoiding Single Points of FailureCatastrophes and Failure ScenariosResiliency TestingFailure Detection and RemediationMonitoringKey MetricsLoggingDashboardsAlertingOn-Call RotationsDocumentation and UnderstandingMicroservice DocumentationMicroservice Understanding

Content preview from Production-Ready Microservices

Glossary

actionable alert: An alert that, when triggered, contains a step-by-step process that the on-call rotation can follow to triage, mitigate, and resolve the alert.
alerting: The practice of notifying an on-call developer (or developers) when one of a service’s key metrics has reached a critical or warning alert threshold.
alert threshold: Static or dynamic quantities that are set for each key metric signifying that the key metric in question is at a normal, warning, or critical level; reaching the threshold should trigger an actionable alert.
application platform layer: The third layer of a microservice ecosystem, containing self-service internal tools, the development environment, test, package, build, and release tools, the deployment pipeline, microservice-level logging, and microservice-level monitoring.
application programming interface (API): A well-defined client-side interface in each microservice that allows other services to interact with it programmatically by sending requests to static endpoints.
architecture diagram: A high-level visual representation of the architecture of a microservice.
architecture review: An organizational practice and process for evaluating, understanding, and improving the architecture of a microservice.
bare metal: The term used to refer to servers owned, run, and maintained by the organization itself, as opposed to hardware rented from so-called cloud providers.
canary: The second stage of the deployment pipeline containing ...