book

Microservices in Action

Name: Microservices in Action
ISBN: 9781617294457

by Paulo A Pereira, Morgan Bruce

October 2018

Intermediate to advanced

392 pages

10h 55m

English

Manning Publications

Read now

Unlock full access

Titlepage
Copyright
preface
acknowledgments
about this book
How this book is organized: a roadmapAbout the codeBook forum
about the authors
about the cover illustration
Part 1: The lay of the land
Chapter 1: Designing and running microservices
1.1 What is a microservice application?1.1.1 Scaling through decomposition1.1.2 Key principles1.1.3 Who uses microservices?1.1.4 Why are microservices a good choice?1.2 What makes microservices challenging?1.2.1 Design challenges1.2.2 Operational challenges1.3 Microservice development lifecycle1.3.1 Designing microservices1.3.2 Deploying microservices1.3.3 Observing microservices1.4 Responsible and operationally aware engineering cultureSummary
Chapter 2: Microservices at SimpleBank
2.1 What does SimpleBank do?2.2 Are microservices the right choice?2.2.1 Risk and inertia in financial software2.2.2 Reducing friction and delivering sustainable value2.3 Building a new feature2.3.1 Identifying microservices by modeling the domain2.3.2 Service collaboration2.3.3 Service choreography2.4 Exposing services to the world2.5 Taking your feature to production2.5.1 Quality-controlled and automated deployment2.5.2 Resilience2.5.3 Transparency2.6 Scaling up microservice development2.6.1 Technical divergence2.6.2 Isolation2.7 What’s next?Summary

Part 2: Design
Chapter 3: Architecture of a microservice application
3.1 Architecture as a whole3.1.1 From monolith to microservices3.1.2 The role of an architect3.1.3 Architectural principles3.1.4 The four tiers of a microservice application3.2 A microservice platform3.2.1 Mapping your runtime platform3.3 Services3.3.1 Capabilities3.3.2 Aggregation and higher order services3.3.3 Critical and noncritical paths3.4 Communication3.4.1 When to use synchronous messages3.4.2 When to use asynchronous messages3.4.3 Asynchronous communication patterns3.4.4 Locating other services3.5 The application boundary3.5.1 API gateways3.5.2 Backends for frontends3.5.3 Consumer-driven gateways3.6 Clients3.6.1 Frontend monoliths3.6.2 Micro-frontendsSummary
Chapter 4: Designing new features
4.1 A new feature for SimpleBank4.2 Scoping by business capabilities4.2.1 Capabilities and domain modeling4.2.2 Creating investment strategies 4.2.3 Nested contexts and services4.2.4 Challenges and limitations4.3 Scoping by use case4.3.1 Placing investment strategy orders 4.3.2 Actions and stores4.3.3 Orchestration and choreography4.4 Scoping by volatility4.5 Technical capabilities4.5.1 Sending notifications4.5.2 When to use technical capabilities4.6 Dealing with ambiguity4.6.1 Start with coarse-grained services4.6.2 Prepare for further decomposition4.6.3 Retirement and migration4.7 Service ownership in organizationsSummary
Chapter 5: Transactions and queries in microservices
5.1 Consistent transactions in distributed applications5.1.1 Why can’t you use distributed transactions?5.2 Event-based communication5.2.1 Events and choreography5.3 Sagas5.3.1 Choreographed sagas5.3.2 Orchestrated sagas5.3.3 Interwoven sagas5.3.4 Consistency patterns5.3.5 Event sourcing5.4 Queries in a distributed world5.4.1 Storing copies of data5.4.2 Separating queries and commands5.4.3 CQRS challenges5.4.4 Analytics and reporting5.5 Further readingSummary
Chapter 6: Designing reliable services
6.1 Defining reliability6.2 What could go wrong?6.2.1 Sources of failure6.2.2 Cascading failures6.3 Designing reliable communication6.3.1 Retries6.3.2 Fallbacks6.3.3 Timeouts6.3.4 Circuit breakers6.3.5 Asynchronous communication6.4 Maximizing service reliability6.4.1 Load balancing and service health6.4.2 Rate limits6.4.3 Validating reliability and fault tolerance6.5 Safety by default6.5.1 Frameworks6.5.2 Service meshSummary
Chapter 7 : Building a reusable microservice framework
7.1 A microservice chassis7.2 What’s the purpose of a microservice chassis?7.2.1 Reduced risk7.2.2 Faster bootstrapping7.3 Designing a chassis7.3.1 Service discovery7.3.2 Observability7.3.3 Balancing and limiting7.4 Exploring the feature implemented using the chassis7.5 Wasn’t heterogeneity one of the promises of microservices?Summary
Part 3: Deployment
Chapter 8: Deploying microservices
8.1 Why is deployment important?8.1.1 Stability and availability8.2 A microservice production environment8.2.1 Features of a microservice production environment8.2.2 Automation and speed8.3 Deploying a service, the quick way8.3.1 Service startup8.3.2 Provisioning a virtual machine8.3.3 Run multiple instances of your service8.3.4 Adding a load balancer8.3.5 What have you learned?8.4 Building service artifacts8.4.1 What’s in an artifact?8.4.2 Immutability8.4.3 Types of service artifacts8.4.4 Configuration8.5 Service to host models8.5.1 Single service to host8.5.2 Multiple static services per host8.5.3 Multiple scheduled services per host8.6 Deploying services without downtime8.6.1 Canaries and rolling deploys on GCESummary
Chapter 9: Deployment with containers and schedulers
9.1 Containerizing a service9.1.1 Working with images9.1.2 Building your image9.1.3 Running containers9.1.4 Storing an image9.2 Deploying to a cluster9.2.1 Designing and running pods9.2.2 Load balancing9.2.3 A quick look under the hood9.2.4 Health checks9.2.5 Deploying a new version9.2.6 Rolling back9.2.7 Connecting multiple servicesSummary
Chapter 10: Building a delivery pipeline for microservices
10.1 Making deploys boring10.1.1 A deployment pipeline10.2 Building a pipeline with Jenkins10.2.1 Configuring a build pipeline10.2.2 Building your image10.2.3 Running tests10.2.4 Publishing artifacts10.2.5 Deploying to staging10.2.6 Staging environments10.2.7 Deploying to production10.3 Building reusable pipeline steps10.3.1 Procedural versus declarative build pipelines10.4 Techniques for low-impact deployment and feature release10.4.1 Dark launches10.4.2 Feature flagsSummary
Part 4: Observability and ownership
Chapter 11: Building a monitoring system
11.1 A robust monitoring stack11.1.1 Good monitoring is layered11.1.2 Golden signals11.1.3 Types of metrics11.1.4 Recommended practices11.2 Monitoring SimpleBank with Prometheus and Grafana11.2.1 Setting up your metric collection infrastructure11.2.2 Collecting infrastructure metrics — RabbitMQ11.2.3 Instrumenting SimpleBank’s place order11.2.4 Setting up alerts11.3 Raising sensible and actionable alerts11.3.1 Who needs to know when something is wrong?11.3.2 Symptoms, not causes 11.4 Observing the whole applicationSummary
Chapter 12 : Using logs and traces to understand behavior
12.1 Understanding behavior across services12.2 Generating consistent, structured, human-readable logs12.2.1 Useful information to include in log entries12.2.2 Structure and readability12.3 Setting up a logging infrastructure for SimpleBank12.3.1 ELK- and Fluentd-based solution12.3.2 Setting up your logging solution12.3.3 Configure what logs to collect12.3.4 Finding a needle in the haystack12.3.5 Logging the right information12.4 Tracing interactions between services12.4.1 Correlating requests: traces and spans12.4.2 Setting up tracing in your services12.5 Visualizing tracesSummary
Chapter 13: Building microservice teams
13.1 Building effective teams13.1.1 Conway’s Law13.1.2 Principles for effective teams13.2 Team models13.2.1 Grouping by function13.2.2 Grouping across functions13.2.3 Setting team boundaries13.2.4 Infrastructure, platform, and product13.2.5 Who’s on-call?13.2.6 Sharing knowledge13.3 Recommended practices for microservice teams13.3.1 Drivers of change in microservices13.3.2 The role of architecture13.3.3 Homogeneity versus technical flexibility13.3.4 Open source model13.3.5 Design review13.3.6 Living documentation13.3.7 Answering questions about your application13.4 Further readingSummary
Appendix: Installing Jenkins on Minikube
Running Jenkins on KubernetesSetting up HelmCreate a namespace and a volumeInstalling JenkinsConfiguring RBACTesting it all works
Index

Content preview from Microservices in Action

7 Building a reusable microservice framework

This chapter covers

Building a microservice chassis
Advantages of enforcing uniform practices across teams
Abstracting common concerns in a reusable framework

Once an organization fully embraces microservices and teams grow in number, it’s quite likely that each of those teams will start specializing in a given set of programming languages and tools. Sometimes, even when using the same programming language, different teams will choose a different combination of tools to achieve the same purpose. Although nothing is wrong with this, it may lead to an increased challenge for engineers moving between different teams. The ritual to set up new services, as well as the code structure, may be quite ...

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.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9781617294457Publisher Support Publisher Website

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Microservices in Action

by Paulo A Pereira, Morgan Bruce

7 Building a reusable microservice framework

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.