# Service Proxy

> For AI agents: the complete glossary index is at [llms.txt](https://glossary.cncf.io/llms.txt).
> Markdown versions of every glossary page are available by appending `index.md` to the page URL.

A service proxy intercepts traffic to or from a given [service](https://glossary.cncf.io/service/), 
applies some logic to it, then forwards that traffic to another service. 
It essentially acts as a “go-between” that collects information about network traffic and/or applies rules to it.

## Problem it addresses

To keep track of service to service communication (aka network traffic) and 
potentially transform or redirect it, we need to collect data. 
Traditionally, the code enabling data collection and network traffic management was embedded within each application.

## How it helps

A service proxy allows us to “externalize” this functionality. 
No longer does it need to live within the apps. 
Instead, it’s now embedded into the platform layer (where your apps run).

Acting as gatekeepers between services, proxies provide insight into what type of communication is happening. 
Based on their insight, they determine where to send a particular request or even deny it entirely.

Proxies gather critical data, manage routing (spreading traffic evenly among services or rerouting if some services break down), 
encrypt connections, and cache content (reducing resource consumption).

---

- Canonical URL: https://glossary.cncf.io/service-proxy/
- Status: Completed
- Last modified November 30, 2023: ` chore: remove duplicated lines ` ([e57ed31](https://github.com/cncf/glossary/commit/e57ed3109d8084268bac253d77a19e799d83bcf9))
- Source: https://github.com/cncf/glossary/blob/main/content/en/service-proxy.md
- License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)