So which one?
Architecture is all about tradeoffs. Neither is better; the right choice depends on what your screen needs from consistency, availability and latency. Measure the read and write paths here, then read the table with your own numbers.
| GraphQL Federation | Event-driven projections | |
| Query latency | Higher: the router waits for several services, in sequence where they depend on each other | Lower: one local database |
| Data freshness | Real-time: every read asks the owner | Eventually consistent: as fresh as the last event applied |
| Service coupling | Tight: every owner must be up for a full answer | Loose: owners and readers meet only through the bus |
| Failure mode | Partial or failed answers when an owner is down | Stale answers when anything upstream is down |
| Read after write | Immediate | After propagation; needs a plan (wait, optimistic UI, or read the owner) |
| Write complexity | Simple: one mutation to the owner | More: outbox, relay, idempotent consumer, replays |
| Moving parts | Router and subgraphs | Plus topics, relays, consumers and projection stores |
Rules of thumb. Federation suits screens that must show the truth this second and can live with an owner's
outage taking part of the page with it (account balances, permissions). Projections suit high-traffic reads that combine many owners
and can be a few hundred milliseconds behind (search, dashboards, feeds). Many systems use both: federate the few fields that must be live,
project the rest.