liveBook · Manning

Sidecar pattern

As explained in Grokking Software Architecture

The sidecar pattern deploys a helper process alongside a primary application process to provide supporting infrastructure capabilities.

A sidecar is a helper process deployed alongside a primary application service. In a service mesh, lightweight sidecar proxies intercept network traffic and handle concerns such as mutual TLS (mTLS), identity-based authorization, routing, and retries, keeping that networking logic out of the application. section 11.3.3

For a legacy system, introduce the pattern gradually:

  • Test a small set of services in staging; validate traffic routing and mTLS before expanding. section 11.3.3
  • Run the mesh in audit mode to map existing traffic, then issue identities and gradually enable deny-by-default policies. section 11.3.3

How Grokking Software Architecture covers it

How deep it goes
Defines the pattern and outlines staging and legacy-migration procedures, without detailing proxy implementation.
Examples
Uses service-mesh proxies for polyglot microservices and an audit-first rollout for legacy traffic.
What it assumes
Assumes a primary application service or legacy system whose network traffic can be handled by an adjacent helper process.
What you can do after
Operate/configure a gradual service-mesh rollout, validating routing and mTLS in staging before enforcing policies on legacy services.
How it connects
Connects sidecars to service meshes, Zero Trust, mutual TLS, identity-based authorization, and microservices.

Also explained in

Compare how 12 books explain sidecar pattern →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.