Accelerating frontend development with stateful BFFs
summary
Demonstrates building a stateful BFF using Netflix Conductor via Orkes to keep session state server side so no browser storage is required and a session ID as pointer resumes interrupted flows. Shows orchestration wiring that retries or triggers compensation, supports multiuser and device-specific routing, and lets UI teams prototype flows in a visual editor or TypeScript. Claims production use across finance, transport and auto, and offers a hands-on workshop on February 15.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:20Stateful BFFs matter
- 1:47User session resilience
- 3:12Adapting UX across devices
- 4:43Conductor for BFF orchestration
- 5:44Workshop and open source
- 6:07Q&A: Why stateful BFFs
- 7:53Q&A: Frontend integration
- 8:58Q&A: Misconceptions
- 11:09Q&A: First steps
- 12:54Q&A: Startup use cases
related talks
11mFrontend Development With BFF (Backend for Frontend)
21mEnhance and improve user experience with BFF
40mBFF4EAE: Your Backend's New Best Friend Forever
25mSupercharge your Backend for Frontend with Kotlin
17mRapidly Build Distributed Applications using Orchestration
30mSPA and BFF for Cloud Foundry
21mEnhance and improve user experience with BFF
34mProcesses, StateCharts and WorkFlows