enforce-thin-proxy

To prevent business logic from leaking into proxy layers, audit endpoints to ensure they strictly perform request extraction, forwarding, logging, and error enrichment. Proxy layers must remain thin and decoupled from domain-specific validation or transformation to keep infrastructure maintainable.

The standard pattern for thin proxy routing is a four-step operational sequence: extract, forward, log, and return. This enforces consistency across boundary layers, ensuring API gateways and edge functions avoid absorbing business logic and remain decoupled.

Audit API gateway code during a code review by scanning proxy functions to flag any that perform validation, data transformation, or business decisions. Generate a migration report to identify bloated proxy code and refactor logic that belongs in the worker layer.

Yes, this proxy audit applies to service-oriented architectures and edge functions. It evaluates boundary layers to verify they remain thin and decoupled, ensuring domain-specific rules are not incorrectly handled within the proxy infrastructure.

A key limitation of keeping proxy layers thin is that they cannot perform domain-specific validation or data transformation. If your edge functions require complex business decisions rather than simple routing, a thin proxy pattern will require refactoring logic into the worker layer.