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 19 · 19 min read · A BFF that aggregates four upstream services inherits four independent failure modes. Any one of them can be unavailable, slow, or intermittently returning errors at any time. The question is not whet
Join discussion
Apr 16 · 21 min read · A note on the code in this article. The observability setup shown here is derived from a production BFF built for a Norwegian enterprise education platform. Resource names, workspace identifiers, aler
Join discussion
Apr 14 · 19 min read · A note on the code in this article. The pipeline configuration, Dockerfile, and infrastructure definitions shown here are derived from a production deployment built for a Norwegian enterprise educatio
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 12 · 16 min read · A note on the code in this article. The implementation shown here is derived from a production BFF built for a Norwegian enterprise education platform. Service names, domain models, and certain struct
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
