liveBook · Manning

Interceptor

An interceptor is a middleware component that observes, modifies, or instruments requests, responses, or operations before, during, or after execution.

How 2 Manning books explain it

.NET in Action, Second Edition

An interceptor is a component that observes or modifies an operation before it is sent to an external system.

How it is used
Audits SQL generated by EF Core during tests and supports review of potential injection vulnerabilities.
How deep it goes
Implements DbCommandInterceptor, ReaderExecutingAsync, test registration, output handling, and ValueTask rationale.
Examples
Logs generated book-lookup SQL and uses an in-memory SQLite test context with xUnit output.
What you can do after
Diagnose and audit EF Core database commands by capturing generated SQL in tests.

Read how .NET in Action, Second Edition explains interceptor →

gRPC Microservices in Go

A gRPC interceptor is middleware that runs around gRPC calls on the client or server to inspect, modify, or instrument them.

How it is used
Centralizes gRPC resilience and observability behavior across microservice call boundaries.
How deep it goes
Explains client and server installation, tracing-provider configuration, batching, metadata, and propagation without detailing interceptor internals.
Examples
Uses Order-to-Payment calls, unary client and server interceptors, Jaeger export, and Jaeger UI trace inspection.
What you can do after
Configure gRPC client and server interceptors to collect, propagate, batch, and export service telemetry.

Read how gRPC Microservices in Go explains interceptor →

Related concepts

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.