5 Best Practices for Backends-for-Frontends

Best practices to follow when implementing the BFF pattern: do’s and don’ts.

Published on

Enjoyed this article?

Share it with your network to help others discover it

Continue Learning

Discover more articles on similar topics

WunderGraph Cosmo: Open Source Schema Registry with Schema Checks for Federated GraphQL

With Cosmo, it's easier than ever to manage your federated GraphQL schemas and prevent composition errors and breaking changes before they reach production.

WundergraphWundergraph cosmoOpen source

Getting Started With WunderGraph: An API Gateway That Turns GraphQL Into RPC on the Fly

A comprehensive guide to WunderGraph, with a focus on its new TypeScript Operations feature - async resolvers for data fetching, with shared types between Server & Client.

GraphqlNextjsWundergraph

Fixing the Backends-for-frontends pattern with Build-time GraphQL

The BFF pattern optimizes backends for specific client interfaces. Using GraphQL for it fixes some of its drawbacks, but can we do better? Let’s find out with WunderGraph.

GraphqlBff patternBff

An Introduction to Cosmo Router: Blazingly Fast Open-Source Federation V1/V2 Gateway

Apollo Router's Elastic license preventing adoption? Want to go even faster? This open-source Federation gateway has got you covered.

GraphqlWundergraphWundergraph cosmo

GraphQL: Open Federation is a Game Changer for Federated Architectures

Because a thriving GraphQL ecosystem cannot be built upon closed, proprietary solutions from a single vendor.

Open federationGraphqlWundergraph

GraphQL is Finally Boring.

The reports of GraphQL’s death have been greatly exaggerated. Let’s look beyond trends, instead, at how a mature, reliable GraphQL is making organizations better.

GraphqlApollo federationWundergraph