[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-backend-for-frontend::en":3,"gloss-cluster-backend-for-frontend::en":26,"gloss-next-backend-for-frontend::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"backend-for-frontend","integration","Backend for Frontend (BFF)","A Backend for Frontend (BFF) is a dedicated API layer built to serve one specific client — your web app, your mobile app, a partner integration — rather than exposing one general-purpose API to all of them. Each frontend gets its own backend that sits between the client and your downstream services, calling them, aggregating the results, and reshaping the response into exactly what that client needs. The problem it solves is mismatch: a mobile app wants small, battery-friendly payloads and fewer round trips, while a web dashboard wants rich, denormalized data; forcing both through one API means one is always over- or under-served. A BFF lets each evolve independently — the mobile team can change its endpoints without breaking the web team. For SaaS builders integrating many internal or third-party services, a BFF is also a clean place to centralize authentication, rate-limit handling, caching, and combining several upstream APIs into one call. The cost is another service to build and maintain, so it earns its keep once you have genuinely divergent clients.","A backend for frontend gives each client — web, mobile, a partner — its own tailored API layer instead of forcing one general-purpose API to serve them all.",null,[11,14,17,20,23],{"slug":12,"name":13},"api","API",{"slug":15,"name":16},"api-gateway","API Gateway",{"slug":18,"name":19},"graphql","GraphQL",{"slug":21,"name":22},"grpc","gRPC",{"slug":24,"name":25},"ipaas","iPaaS",[27,31,34,37,40,42,45,48,51,54,57,60],{"slug":28,"category":5,"name":29,"updated_at":30},"concurrency-limit","Concurrency Limit","2026-08-24T02:46:38+00:00",{"slug":32,"category":5,"name":33,"updated_at":30},"event-ordering","Event Ordering",{"slug":35,"category":5,"name":36,"updated_at":30},"field-mapping","Field Mapping",{"slug":38,"category":5,"name":39,"updated_at":30},"function-schema","Function Schema",{"slug":21,"category":5,"name":22,"updated_at":41},"2026-08-24T02:46:37+00:00",{"slug":43,"category":5,"name":44,"updated_at":30},"integration-marketplace","Integration Marketplace",{"slug":46,"category":5,"name":47,"updated_at":30},"ip-allowlist","IP Allowlist",{"slug":49,"category":5,"name":50,"updated_at":30},"json-web-token","JSON Web Token (JWT)",{"slug":52,"category":5,"name":53,"updated_at":30},"mcp-server","MCP Server",{"slug":55,"category":5,"name":56,"updated_at":30},"mutual-tls","Mutual TLS (mTLS)",{"slug":58,"category":5,"name":59,"updated_at":30},"oauth-scopes","OAuth Scopes",{"slug":61,"category":5,"name":62,"updated_at":30},"openapi-specification","OpenAPI Specification"]