BFF4EAE: Your Backend's New Best Friend Forever
summary
Argues that BFFs should stop shuffling JSON and become action-shaped APIs that ship intent not data, moving orchestration, retries, circuit breakers and adaptive backoff to a self-controlling BFF so clients get one-tailored response and fewer failures; gives concrete patterns (manifest-driven actions, server-driven UI with a suggested nine UI primitives, cache/read-through, protobuf/gRPC notes, Remote Compose alpha) and cites running systems serving over 100 million users and a 0.5s median painted startup.
AI-written summary · about
chapters (21)
- 0:00BFF for AE AE intro
- 1:51What we'll learn
- 3:16Server-driven UI explained
- 5:03REST API problems
- 7:09Action-shaped APIs
- 9:17BFF failure handling
- 12:04Self-controlling BFF design
- 13:51Modern BFF components
- 15:37Airbnb's software-defined UI
- 17:23GraphQL and section UI
- 19:31Software-defined UI with primitives
- 21:39Compose performance
- 23:07Nine UI primitives
- 25:17Remote Compose systems
- 27:04Remote Compose pros/cons
- 28:46Balanced primitive solution
- 31:36Defining actions
- 34:03Chaining actions
- 35:49Versioning and graceful failure in APIs
- 37:34BFF scalability impact
- 38:39Q&A
related talks
39mBFF, our best friend forever for building lots of frontend apps?
54mGiving the Frontend Only What It Needs, or Why You Need a BFF
38mBFF vs GraphQL: A critical perspective
11mFrontend Development With BFF (Backend for Frontend)
21mEnhance and improve user experience with BFF
25mSupercharge your Backend for Frontend with Kotlin
21mEnhance and improve user experience with BFF
09mKeep your friends close and your APIs closer