Portfolio ↗

Quiz

2948 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas2948 Architecture Fundamentals91 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking96 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

5 questions in BFF for Experience.

  1. BFF for Experience advanced

    A team adds a backend-for-frontend per client - web, iOS, Android, partner. Latency and payload sizes improve immediately. What has been given up, and when does that bill arrive?

    3 min answer bffcouplingownershipduplication
  2. BFF for Experience advanced

    A travel platform serves web, iOS, Android and partner integrations from the same services. When is a backend-for-frontend justified?

    1 min answer bffapi-designaggregationcoupling
  3. BFF for Experience advanced

    Review this. An API gateway terminates TLS and validates tokens. Behind it a GraphQL gateway stitches 23 services. Behind that, four backend-for-frontend services - web, iOS, Android and partner - each call the GraphQL gateway, and the web client also runs a normalised client cache. Two clients carry 96% of traffic. Adding one field to one screen takes three pull requests across three repositories. What would you remove, what is the one change that matters, and what would you leave alone?

    3 min answer bffgraphqlaggregationarchitecture-review
  4. BFF for Experience intermediate Multiple choice

    Six product teams ship a web app and an iOS app against 23 domain services. A typical screen needs data from four to nine of them. Mobile releases take roughly three weeks to reach 90% of installs. Round-trip time on mobile networks is 60-150 ms. The platform team must pick one aggregation approach for the next two years. Which fits?

    2 min answer bffownershipapi-shapesversion-tail
  5. BFF for Experience intermediate

    Your mobile BFF now contains pricing logic, entitlement checks and order validation. What has gone wrong?

    2 min answer bffboundariesdrift