Backends for Frontend
Last updated
What is Backends for Frontend?
Create separate backend services to be consumed by specific frontend applications or interfaces. This pattern is useful when you want to avoid customizing a single backend for multiple interfaces. This pattern was first described by Sam Newman.
Free resources to learn Backends for Frontend
More in stage 23: Reliability Patterns
- Reliability Patterns
- Strangler Fig
- Sidecar
- Static Content Hosting
- Leader Election
- CQRS
- Pipes & Filters
- Ambassador
- Gateway Routing
- Gateway Offloading
- Gateway Aggregation
- External Config Store
- Compute Resource Consolidation
- Anti-Corruption Layer
- Valet Key
- Sequential Convoy
- Static Content Hosting
- Scheduling Agent Supervisor
- Sharding
- Queue-Based Load Leveling
- Materialized View
- Publisher/Subscriber
- Index Table
- Priority Queue
- Event Sourcing
- Pipes and Filters
- CQRS
- Competing Consumers
- Cache-Aside
- Choreography
- Claim Check
- Async Request Reply
Backends for Frontend: common questions
Can I learn Backends for Frontend in Hindi?
This lesson is written in English. Once you sign in, open it in the interactive course and ask the AI tutor to explain Backends for Frontend in Hindi or Hinglish. The tutor answers from this lesson’s own text, so it stays on the syllabus, and it runs on your own Google, OpenAI or Anthropic key.
Is this Backends for Frontend tutorial for beginners?
It is lesson 103 of 147 in the free System Design roadmap, in stage 23, Reliability Patterns. If you are new to System Design, start from stage 1 and come back here in order; if you already know the earlier stages, this lesson stands on its own.