liveBook · Manning

Service communication

Also called east-west traffic

Service communication is the exchange of requests, responses, messages, or data between distinct services.

How 3 Manning books explain it

Platform Engineering on Kubernetes

A service-to-service interaction is communication in which one independently deployable service requests or sends data to another service.

How it is used
Coordinates requests and data exchange between independently deployable services while addressing failure handling and platform consistency.
How deep it goes
Explains retries, exponential backoff, sidecars, component configuration, and platform policies, but does not standardize behavior across all technology stacks.
Examples
Uses Spring Retry, go-retryablehttp, Dapr sidecars, and Conference services communicating through invocation APIs.
What you can do after
Apply it via Dapr Service Invocation APIs and configure uniform resiliency policies without changing application code.

Read how Platform Engineering on Kubernetes explains service communication →

gRPC Microservices in Go

Service-to-service communication is the exchange of requests and responses between application services.

How it is used
Connects independently deployable services so they can exchange messages while preserving attention to reliability and data consistency.
How deep it goes
Explains the gRPC and Protocol Buffers approach and identifies resilience concerns without detailing their implementations here.
Examples
Uses a Python Checkout client calling a Java Payment service and contrasts internal gRPC with browser-facing REST.
What you can do after
Evaluate gRPC for internal calls against browser compatibility and maintenance costs, then plan for resilient, observable operation.

Read how gRPC Microservices in Go explains service communication →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

The network interaction through which independently deployed microservices exchange information and coordinate behavior.

How it is used
Coordinates independently responsible microservices so they can collaborate on higher-level application features.
How deep it goes
Explains direct and indirect messaging with HTTP and RabbitMQ, but defers improved service-readiness handling to later treatment.
Examples
Uses video-streaming, video-storage, and history microservices to demonstrate direct requests and streams of messages.
What you can do after
Evaluate whether HTTP or RabbitMQ better fits a coordination or decoupling requirement.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains service communication →

Also covered in

What to know first

Related concepts

Questions about service communication

What is service communication?

Service communication is the exchange of requests, responses, messages, or data between distinct services.

Which Manning books explain service communication?

Platform Engineering on Kubernetes, gRPC Microservices in Go and Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform.

What should I know before learning service communication?

Manning books that teach service communication usually introduce microservice architecture, distributed system, gRPC and HTTP first.

What kinds of service communication are there?

Kinds of service communication include direct messaging.

What is service communication a kind of?

Service communication is a kind of network traffic. Network traffic is the flow or volume of data, including packets and requests, transmitted between systems over a computer network.

What is service communication also called?

Service communication is also called east-west traffic.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.