liveBook · Manning

Cross-cutting concern

As explained in Microservices Patterns, Second Edition

A cross-cutting concern is an architectural concern that affects multiple services or components rather than a single service.

In a microservice architecture, each service needs concerns such as observability, discovery, security, and externalized configuration. Reimplementing them for every service risks duplicated effort and inconsistent, error-prone implementations. section 7.6.2

A microservice chassis handles shared concerns; a service template built on it gives developers a starting point for new services while minimizing duplicated code. section 7.6.2

Examples of concerns and supporting work include:

  • Health checks, centralized log aggregation, distributed tracing, exception tracking, application metrics, and audit logging. section 7.6.2
  • Build logic, such as Maven or Gradle, and a deployment pipeline. section 7.6.2

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the problem and recommends a service template and chassis, while deferring detailed pattern treatment.
Examples
Names health checks, log aggregation, distributed tracing, exception tracking, metrics, audit logging, and Maven or Gradle build logic.
What it assumes
Assumes a microservice architecture in which each service implements shared operational and delivery concerns.
What you can do after
Apply a service template built on a microservice chassis to start services without reimplementing shared concerns.
How it connects
Connects observability, service discovery, security, externalized configuration, service templates, and microservice chassis.

Also explained in

Compare how 6 books explain cross-cutting concern →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.