Back to Catalog
Cloud
azure
Backends for Frontends
Create separate backend services for specific frontend applications
Intent & Description
The Backends for Frontends pattern creates separate backend services for specific frontend applications or interfaces. Instead of having a single backend that serves all clients, each frontend type has a dedicated backend optimized for its needs. This reduces complexity and improves performance for each client type.
Real-world Use Case
Use when different frontend applications have different data requirements or when a single backend becomes too complex to support multiple client types.
Source
Advantages
- Optimized backends for each client type
- Reduced complexity in individual services
- Improved performance and user experience
- Better separation of concerns
Disadvantages
- Code duplication across services
- More services to manage
- Increased infrastructure costs