GraphQL Federation: I'm Still Skeptical
A year after my GraphQL post, federation is the new hotness. I still think most teams don't need it.
Graphql
Definition
Graphql coverage in this archive spans 4 posts from Feb 2017 to Oct 2021 and deals with structural tradeoffs: coupling, failure boundaries, and long-term change cost. The strongest adjacent threads are api, federation, and architecture. Recurring title motifs include graphql, federation, skeptical, and probably.
What the archive argues
- Most pieces recommend choosing the simplest architecture that can be operated confidently.
- The consistent theme from 2017 to 2021 is disciplined execution over hype cycles.
- This topic repeatedly intersects with api, federation, and architecture, so design choices here rarely stand alone.
Execution checklist
- Define failure domains and data boundaries before introducing additional services or protocols.
- Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
- When boundary questions appear, cross-read api and federation before committing implementation details.
Common failure modes
- Breaking systems into many parts without clear ownership of cross-service behavior.
- Choosing architecture for trend alignment rather than workload constraints.
- Applying guidance from 2017 to 2021 without revisiting assumptions as context changed.
Suggested reading path
- Start here (current state): GraphQL Federation: I’m Still Skeptical
- Then read (operating middle): GraphQL in Production Is Harder Than They Tell You
- Finish with (foundational context): GraphQL vs REST: Pick the Boring One
Related posts
- GraphQL Federation: I’m Still Skeptical
- GraphQL Federation Is Probably Not For You
- GraphQL in Production Is Harder Than They Tell You
- GraphQL vs REST: Pick the Boring One
References
GraphQL Federation Is Probably Not For You
Most teams adopting GraphQL federation don't need it. A frank take on when it makes sense, when REST is fine, and why conference talks are a terrible basis for architecture decisions.
GraphQL in Production Is Harder Than They Tell You
After a year running GraphQL at the fintech startup, here's what the conference talks leave out.
GraphQL vs REST: Pick the Boring One
Everyone wants to debate GraphQL vs REST like it's a religion. It's not. One reduces round trips, the other is dead simple to cache. Here's how I actually decide.