Apr 19 · 20 min read · Every article in this series has described building a BFF on a greenfield system — a clean slate where the architecture is decided upfront and the frontend and BFF are developed in parallel. That is n
Join discussion
Apr 17 · 9 min read · Most frontend applications don’t fail because of bad UI. They fail because they were never designed to scale. At small scale, components and hooks feel enough. At large scale, they become the problem.
Join discussion
Apr 12 · 18 min read · A note on the code in this article. The implementation shown here is derived from a production Vue 3 application built for a Norwegian enterprise education platform. Service names, domain models, and
Join discussion
Apr 11 · 14 min read · Before writing a single line of BFF code, one question deserves a direct answer: is BFF actually the right abstraction for your situation, or would an API Gateway or GraphQL solve the same problems wi
AArchit commented
Apr 10 · 15 min read · In Part 1, I broke down when Micro Frontends make sense and when they're architectural overkill. We covered the decision framework, performance trade-offs, and red flags to watch for. Now comes the ha
Join discussion
Apr 8 · 15 min read · In the previous article, we established when a BFF earns its overhead. This article assumes you have made that decision and are now facing the harder question: how do you actually design the thing wel
LALaura and 3 more commented
Mar 21 · 5 min read · At some point, most frontend teams hit the same wall. The backend exposes what it knows — resources, entities, service boundaries — and the frontend is left stitching four API calls into a single scre
Join discussion
