liveBook · Manning

Proxy

A proxy is an intermediary object or component that represents another object or system and mediates interactions with it.

How 3 Manning books explain it

Effective Platform Engineering

A proxy server is an intermediary that forwards, filters, modifies, or manages network traffic between applications or services.

How it is used
Provides an application-independent integration point for managing communication between services in a service mesh.
How deep it goes
Defines traffic handling and compares Kubernetes deployment placements, but does not detail proxy configuration syntax.
Examples
Illustrates token validation, connection retries, and encryption between proxies.
What you can do after
Evaluate/understand proxy placement against service-specific policy, isolation, and observability needs.

Read how Effective Platform Engineering explains proxy →

The Joy of JavaScript

A Proxy is a JavaScript object that wraps a target object and intercepts fundamental operations on it through handler traps.

How it is used
Applies dynamic weaving to add logging, tracing, caching, masking, instrumentation, and smart-object behavior without changing application implementations.
How deep it goes
Explains targets, handlers, get, set, and has traps with examples, while stopping short of covering every available trap.
Examples
Demonstrates credential tracing and masking, composed handlers, automatic blockchain block hashing, and revocable validation timing.
What you can do after
Build it from scratch using Proxy handlers and Reflect to inject modular behavior around object access and mutation.

Read how The Joy of JavaScript explains proxy →

Java Persistence with Spring Data and Hibernate epub

A proxy is a substitute object that represents another object and defers or controls access to that object's state or behavior.

How it is used
Defers entity and association loading until application code accesses the represented state.
How deep it goes
Explains creation, initialization triggers, generated subclasses, detached-state failures, and entity requirements, while deferring broader fetch-plan treatment.
Examples
Demonstrates Item and User references, seller loading, class inspection, initialization checks, and bid persistence without SELECT statements.
What you can do after
Diagnose lazy-loading behavior, initialize proxies safely, inspect their loaded state, and avoid unnecessary SELECT statements when persisting relationships.

Read how Java Persistence with Spring Data and Hibernate epub explains proxy →

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.