Backend For Frontend: Building APIs w. end user in mind
summary
N26 replaces client-side aggregation with per-domain presentation services that run live on several screens, moving aggregation, translations, dynamic assets to the backend and emitting JSON with S3 asset URLs and deep-link strings. Implementation uses Kotlin/Spring and a Cocoon-based DSL for component config. Results show lower CPU on devices, server-side caching and fallbacks, faster feature pushes and easier A/B testing; risks are API version drift and the BFF as a stateless single point of failure that must be heavily over-provisioned.
AI-written summary · about
chapters (4)
related talks
21mEnhance and improve user experience with BFF
25mSupercharge your Backend for Frontend with Kotlin
41mDiscussing Backend For Front-end
21mEnhance and improve user experience with BFF
11mFrontend Development With BFF (Backend for Frontend)
44mBackend less Development revisited
37mDiscussing Backend-For-Frontend
09mKeep your friends close and your APIs closer