The facade pattern provides a simplified client interface over complex or constrained services. It improves the experienced response without requiring changes to underlying systems, making it useful for legacy architectures and third-party APIs. section 5.5.1 section 5.0
A performance-oriented facade can:
- Cache responses so repeated client requests avoid unnecessary calls to slow services. section 5.5.1
- Extract only the fields required by the user interface instead of forwarding oversized responses. section 5.5.1
- Orchestrate and parallelize calls across multiple underlying services while presenting one combined response. section 5.5.1
Shipping-status facade
An e-commerce client needs only a shipment’s current status, but the shipping provider returns full shipment history. A facade can cache provider responses, select the required status fields, and parallelize rate checks across carriers while leaving the provider APIs unchanged. section 5.5.1



