book

Cloud Native

by Boris Scholl, Trent Swanson, Peter Jausovec

August 2019

Beginner

229 pages

6h 35m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Conventions Used in This BookO’Reilly Online LearningHow to Contact UsAcknowledgments
Distributed SystemsFallacies of Distributed SystemsCAP TheoremThe Twelve-Factor AppAvailability and Service-Level AgreementsSummary
ContainersContainer Isolation LevelsContainer OrchestrationKubernetes OverviewKubernetes and ContainersServerless ComputingFunctionsFrom VMs to Cloud NativeLift-and-ShiftApplication ModernizationApplication OptimizationMicroservicesBenefits of a Microservices ArchitectureChallenges with a Microservices ArchitectureSummary
Fundamentals of Cloud Native ApplicationsOperational ExcellenceSecurityReliability and AvailabilityScalability and CostCloud Native versus Traditional ArchitecturesFunctions versus ServicesFunction ScenariosConsiderations for Using FunctionsComposite of Functions and ServicesAPI Design and VersioningAPI Backward and Forward CompatibilitySemantic VersioningService CommunicationProtocolsMessaging ProtocolsSerialization ConsiderationsIdempotencyRequest/ResponsePublisher/SubscriberChoosing Between Pub/Sub and Request ResponseSynchronous versus AsynchronousGatewaysRoutingAggregationOffloadingImplementing GatewaysEgressService MeshExample ArchitectureSummary
Data Storage SystemsObjects, Files, and DisksDatabasesStreams and QueuesBlockchainSelecting a DatastoreData in Multiple DatastoresChange Data CaptureWrite Changes as an Event to a Change LogTransaction SupervisorCompensating TransactionsExtract, Transform, and LoadMicroservices and Data LakesClient Access to DataRestricted Client Tokens (Valet-Key)Database Services with Fine-Grained Access ControlGraphQL Data ServiceFast Scalable DataSharding DataCaching DataContent Delivery NetworksAnalyzing DataStreamsBatchData Lakes on Object StorageData Lakes and Data WarehousesDistributed Query EnginesDatabases on KubernetesStorage VolumesStatefulSetsDaemonSetsSummary
What Is DevOps?CollaborationAutomationLean Principles and ProcessesMeasurementSharingTestingTest DoublesTest Automation PyramidWhen to Run Which Types of TestsTesting CadenceTesting in ProductionDevelopment Environments and ToolsDevelopment ToolsDevelopment EnvironmentsLocal Development EnvironmentsLocal Development with a Remote ClusterSkaffold Development WorkflowRemote Cluster Routed to Local DevelopmentCloud Development EnvironmentsCI/CDSource Code ControlBuild Stage (CI)Test Stage (CI)Deploy Stage (CD)Release Stage (CD)Post-Release StageMonitoringCollecting MetricsObservable ServicesConfiguration ManagementSingle-Environment VariableMultiple-Environment VariablesAdding ConfigMap Data to a VolumeStoring SecretsDeployment ConfigurationSample CI/CD FlowsSummary
Moving to Cloud NativeBreaking Up the Monolith for the Right ReasonsDecouple Simple Services FirstLearn to Operate on a Small ScaleUse an Anticorruption Layer PatternUse a Strangler PatternCome Up with a Data Migration StrategyRewrite Any Boilerplate CodeReconsider Frameworks, Languages, Data Structures, and DatastoresRetire CodeEnsuring ResiliencyHandle Transient Failures with RetriesUse a Finite Number of RetriesUse Circuit Breakers for Nontransient FailuresGraceful DegradationUse a Bulkhead PatternImplement Health Checks and Readiness ChecksDefine CPU and Memory Limits for Your ContainersImplement Rate Limiting and ThrottlingEnsuring SecurityTreat Security Requirements the Same as Any Other RequirementsIncorporate Security in Your DesignsGrant Least-Privileged AccessUse Separate Accounts/Subscriptions/TenantsSecurely Store All SecretsObfuscate DataEncrypt Data in TransitUse Federated Identity ManagementUse Role-Based Access ControlIsolate Kubernetes PodsWorking with DataUse Managed Databases and Analytics ServicesUse a Datastore That Best Fits Data RequirementsKeep Data in Multiple Regions or ZonesUse Data Partitioning and Replication for ScaleAvoid Overfetching and Chatty I/ODon’t Put Business Logic in the DatabaseTest with Production-like DataHandle Transient FailuresPerformance and ScalabilityDesign Stateless Services That Scale OutUse Platform Autoscaling FeaturesUse CachingUse Partitioning to Scale Beyond Service LimitsFunctionsWrite Single-Purpose FunctionsDon’t Chain FunctionsKeep Functions Light and SimpleMake Functions StatelessSeparate Function Entry Point from the Function LogicAvoid Long-Running FunctionsUse Queues for Cross-Function CommunicationOperationsDeployments and Releases Are Separate ActivitiesKeep Deployments SmallCI/CD Definition Lives with the ComponentConsistent Application DeploymentUse Zero-Downtime ReleasesDon’t Modify Deployed InfrastructureUse Containerized BuildDescribe Infrastructure Using CodeUse Namespaces to Organize Services in KubernetesIsolate the EnvironmentsSeparate Function Source CodeCorrelate Deployments with CommitsLogging, Monitoring, and AlertingUse a Unified Logging SystemUse Correlation IDsInclude Context with Log EntriesCommon and Structured Logging FormatTag Your Metrics AppropriatelyAvoid Alert FatigueDefine and Alert on Key Performance IndicatorsContinuous Testing in ProductionStart with Basic MetricsService CommunicationDesign for Backward and Forward CompatibilityDefine Service Contracts That Do Not Leak Internal DetailsPrefer Asynchronous CommunicationUse Efficient Serialization TechniquesUse Queues or Streams to Handle Heavy Loads and Traffic SpikesBatch Requests for EfficiencySplit Up Large MessagesContainersStore Images in a Trusted RegistryUtilize the Docker Build CacheDon’t Run Containers in Privileged ModeUse Explicit Container Image TagsKeep Container Images SmallRun One Application per ContainerUse Verified Images from Trusted RepositoriesUse Vulnerability Scanning Tools on ImagesDon’t Store Data in ContainersNever Store Secrets or Configuration Inside an ImageSummary
Why Make Applications Portable?The Costs of PortabilityData Gravity and PortabilityWhen and How to Implement PortabilityStandardized InterfacesCommon Services and FeaturesAbstractions and LayersManaged Services from Other VendorsPortability ToolingKubernetes as a Portability LayerSummary