One question, three services

"Who is this person, what is their job, and what badge do they carry?" Three teams own those three answers. Federation asks all three, live, on every request. The event-driven side asks one service that already holds a copy.

Ready

The sliders slow a federation subgraph down. Try Employment at 600ms, then Security at 600ms too: does the total double?

GraphQL Federation

One query to the router. It plans: fetch the Person from HR, then ask Employment and Security for their parts in parallel.

Query

      
Timeline (measured)

Run it to see each hop.

subgraph callfailed
Answer
Console

    

Event-driven projection

One REST call to the query service. It reads three local tables that a consumer filled from events earlier.

Request

      
Timeline (measured)

Run it to see the one hop.

local read
Answer
Console

    
Federation's total is roughly router + HR + the slower of Employment and Security: the two run side by side, but both wait for HR, because they need the Person it returns. The projection's total is one database read, whatever the three teams' services are doing.