book

Microservices: Up and Running

by Ronnie Mitra, Irakli Nadareishvili

November 2020

Intermediate to advanced

316 pages

8h 32m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Who Should Read This BookWhat You’ll NeedConventions Used in This BookUsing Code ExamplesO’Reilly Online LearningHow to Contact UsAcknowledgments
What Are Microservices?Reducing Coordination CostsThe Coordination Cost ProblemThe Hard PartsLearning by DoingThe “Up and Running” Microservices ModelDecisions, Decisions…Writing a Lightweight Architectural Decision RecordSummary
Why Teams and People MatterTeam SizeTeam SkillsInterteam CoordinationIntroducing Team TopologiesTeam TypesInteraction ModesDesigning a Microservices Team TopologyEstablish a System Design TeamBuilding a Microservices Team TemplatePlatform TeamsEnabling and Complicated-Subsystem TeamsConsumer TeamsSummary
Introducing the Seven Essential Evolutions of Design for Services: The SEED(S) MethodIdentifying ActorsExample Actors in Our Sample ProjectIdentifying Jobs That Actors Have to DoUsing Job Story Format to Capture JTBDsExample JTBDs in Our Sample ProjectDiscovering Interaction Patterns with Sequence DiagramsDeriving Actions and Queries from JTBDsExample Queries and Actions for Our Sample ProjectDescribing Each Query and Action as a Specification with an Open StandardExample OAS for an Action in Our Sample ProjectGetting Feedback on the API SpecificationImplementing MicroservicesMicroservices Versus APIsSummary
Why Boundaries Matter, When They Matter, and How to Find ThemDomain-Driven Design and Microservice BoundariesContext MappingSynchronous Versus Asynchronous IntegrationsA DDD AggregateIntroduction to Event StormingThe Event-Storming ProcessIntroducing the Universal Sizing FormulaThe Universal Sizing FormulaSummary
Independent Deployability and Data SharingMicroservices Embed Their DataEmbedding Data Should Not Lead to an Explosion in the Number of Database ClustersData Embedding and the Data Delegate PatternUsing Data Duplication to Solve for IndependenceDistributed Transactions and Surviving FailuresEvent Sourcing and CQRSEvent SourcingImproving Performance with Rolling SnapshotsEvent StoreCommand Query Responsibility SegregationEvent Sourcing and CQRS Beyond MicroservicesSummary
DevOps Principles and PracticesImmutable InfrastructureInfrastructure as CodeContinuous Integration and Continuous DeliverySetting Up the IaC EnvironmentSet Up GitHubInstall TerraformConfiguring Amazon Web ServicesSetting Up an AWS Operations AccountConfigure the AWS CLISetting Up AWS PermissionsCreating an S3 Backend for TerraformBuilding an IaC PipelineCreating the Sandbox RepositoryUnderstanding TerraformWriting the Code for the Sandbox EnvironmentBuilding the PipelineTesting the PipelineSummary
Infrastructure ComponentsThe NetworkThe Kubernetes ServiceThe GitOps Deployment ServerImplementing the InfrastructureInstalling kubectlSetting Up the Module RepositoriesThe Network ModuleThe Kubernetes ModuleSetting Up Argo CDTesting the EnvironmentCleaning Up the InfrastructureSummary
Coding Standards and the Developer’s Setup10 Workspace Guidelines for a Superior Developer ExperienceSetting Up a Containerized Environment LocallyInstalling MultipassEntering the Container and Mapping FoldersInstalling DockerTesting DockerAdvanced Local Docker Usage: Installing CassandraInstalling KubernetesSummary
Designing Microservice EndpointsFlights MicroserviceReservations MicroserviceDesigning an OpenAPI SpecificationImplementing the Data for a MicroserviceRedis for the Reservations Data ModelMySQL Data Model for the Flights MicroserviceImplementing Code for a MicroserviceThe Code Behind the Flights MicroserviceHealth ChecksIntroducing a Second Microservice to the ProjectHooking Services Up with an Umbrella ProjectSummary

Setting Up the Staging EnvironmentThe Ingress ModuleThe Database ModuleForking the Staging Infrastructure ProjectConfiguring the Staging WorkflowEditing the Staging Infrastructure CodeShipping the Flight Information ContainerIntroducing Docker HubConfiguring Docker HubConfiguring the PipelineDeploying the Flights Service ContainerUnderstanding Kubernetes DeploymentsCreating a Helm ChartCreating the Microservices Deployment RepositoryArgo CD for GitOps DeploymentClean UpSummary
Changes in a Microservices SystemBe Data-OrientedThe Impact of ChangesThree Deployment PatternsConsiderations for Our ArchitectureInfrastructure ChangesMicroservices ChangesData ChangesSummary
On Complexity and Simplification Using MicroservicesMicroservices QuadrantMeasuring the Progress of a Microservices TransformationSummary

Content preview from Microservices: Up and Running

Chapter 12. A Journey’s End (and a New Beginning)

Congratulations, you’ve made it to the final chapter! While you may be reaching the end of your journey with us, we hope it is only the beginning of a long and fruitful journey in successfully implementing microservices on real projects. We make no excuses for the fact that we are admirers of the microservices architecture and of the benefits it can bring when deployed in the right context, with the right intentions and skill. It is by no means the only choice and should never be implemented without understanding all the implications, but it can certainly be a very powerful choice in your arsenal of architectural tools.

We have witnessed many successful microservices projects. There is also no shortage of failed attempts to adopting microservices. Our main motivation in writing this book was to increase a reader’s chances of success, if they so choose to implement their system in the microservices style. We tried to do it by providing step-by-step, pragmatic guidelines on when, why, and how to deploy microservices, explaining core concepts and demonstrating the implementation of those concepts, using simple examples. We hope we were successful in achieving the goal of turning abstract concepts into a more approachable step-by-step explanation, but most importantly, we hope you enjoyed reading this book, even if it provided only a handful of key ideas you think you can use when implementing your own systems.

Before we part ways, ...