Comparison
Proxy patternvsSidecar proxy
Proxy pattern
the object looks and behaves exactly like the real one, and its whole job is deciding whether the call gets through.
A wrapper with the same interface as its subject whose purpose is to control access to it — checking permission, deferring creation, or standing in for something remote. It shares its shape with the decorator and differs in intent: a decorator adds behaviour the caller wants, a proxy manages access the caller should not have to think about. Proxies typically control the subject's lifetime as well, where decorators are handed one already made.
Full entry →Sidecar proxy
every connection your service makes actually goes through a proxy in the same pod, which is where the retries and the TLS happen.
The per-workload proxy that intercepts inbound and outbound traffic, giving a mesh its identity, encryption, routing and telemetry without application changes. It is the data plane of a service mesh, and it is why mesh features apply uniformly to services written in five languages. Its costs are a hop of latency, memory and CPU on every pod, and a genuinely difficult startup and shutdown ordering problem with the application beside it.
Full entry →