The Open-Source GraphQL Federation Solution Discord đŁ: https://xitter.cf/t.co/WiK49jUpKZ Github âď¸: https://xitter.cf/t.co/SSorMGNW9q
Space đ
Joined September 2020
- Tweets1.3K
- Following60
- Followers1.2K
- Likes1.2K
Last week we hosted the Federation Dinner Series in San Francisco. Thanks to everyone who came!
We kicked things off with icebreakers, and turns out the federation crowd includes sailors and skydivers, which kind of makes sense. Then people shared what they're wrestling with as AI reshapes their work, and the answers were all over the map. No two people had the same problem, which was probably the most useful part of the night.
The next one's coming. We'll share details soon.
@tokensandai
@AWS @hanghuang_ @DevSeth44 @gregosuri
@Vapi_AI @Redisinc @akashnet @NexlaInc @TigerDatabase @GuildAI @chainguard_dev @insforge
#FederationDinner #GraphQL #PlatformEngineering
skip the pitch deck. just demo it đ¤
last thursday we hosted AI Agents in Prod in SF. workshops, demos, and the kind of room that drives you towards more.
a control plane that maps the blast radius of every ai code change. a music studio controlled by voice. security agents that reproduce exploits in sandboxes.
turns out sf builders don't mess around.
get a glimpse of the winner projectsđ
@GoogleDeepMind ¡ @ElevenLabsDevs ¡ @vercel ¡ @wundergraphcom ¡ @Cometml ¡ @insforge ¡ @usebland
thanks to our speakers: @vincent_koc Maggie Jones @hanghuang_ and @ivanleomk
Tesler's Law of Conservation of Complexity: every application has an inherent amount of irreducible complexity.
The question is who will have to deal with it. Not if. Who?
wundergraph.com/blog/rest-vsâŚ
MCP with one broad OAuth scope breaks least privilege. Scopes should be enforced per tool, derived from the schema, not flattened at the server.
wundergraph.com/blog/mcp-perâŚ
Federation composes subgraphs into a supergraph. Fission flips it.
You design the supergraph first, assign fields to subgraphs, and the system derives the required schemas and dependencies.
Learn more:
wundergraph.com/blog/fissionâŚ
Agents donât integrate APIs like humans.
They canât read docs or SDKs. They have to discover capabilities.
This post touches on why we believe GraphQL is the layer Agents need.
wundergraph.com/blog/graphqlâŚ
Excited to announce that WunderGraph is partnering with Creators Corner for their upcoming Hackathon in San Francisco on April 23rd! đ
Register now! luma.com/shiptoprod
Weâre collecting info on how teams adopt, operate, and scale federation in production. It takes 5â10 minutes to complete, you get early access to the full report, and weâll donate $30 to UNICEF for every valid response.
The goal is to build a clear, vendor-neutral view of whatâs working, whatâs breaking, and how AI is changing the shape of these systems. Take the survey:
8bxwlo3ot55.typeform.com/to/âŚ
Their graph composed fine, but days of implementation work stretched into weeks, because ownership was unclear and coordination required multiple meetings
Read about how Hub changed their approach.
wundergraph.com/blog/graphqlâŚ
Federation's core operation is composition: take many subgraph schemas, merge them into one supergraph.
Many to one
Fission does the inverse: take one supergraph design, decompose it into subgraph responsibilities.
One to many
wundergraph.com/blog/fissionâŚ
Agents need to discover capabilities, navigate structure, and execute within tight context limits.
Our argument: GraphQLâs typed, navigable schema and a federated supergraph match that model.
wundergraph.com/blog/graphqlâŚ
Cosmo Router Cost Control estimates query cost at planning time and can block expensive requests before execution.
Measuring Mode records estimated cost without rejecting.
Enforcing Mode rejects over-limit queries before execution.
wundergraph.com/blog/cost-coâŚ
GraphQL Federation doesnât remove coupling.
It makes it explicit.
@requires wonât fix temporal dependency, the router still needs upstream services.
But instead of hidden HTTP calls, dependencies live in the schema, visible in query plans and validated at build time.
wundergraph.com/blog/microseâŚ
WunderGraph Hub from the CTO's POV (Live Discussion) xitter.cf/i/broadcasts/1qxvvkeyVâŚ
Hub is the missing coordination layer for GraphQL Federation, built for high-velocity teams scaling in the age of AI.
Introducing WunderGraph Hub đ
Hub is a collaborative workspace for GraphQL Federation, and it reimagines the traditional workflow by flipping it on its head:
Instead of starting with subgraphs and stitching them together later (bottom-up),
you start with what the API consumer actually needs (top-down).
API design moves from scattered Jira/Linear tickets, Figma screenshots, and endless alignment meetings onto one powerful canvas.
Governance is built into the platform, allowing you to ship faster than ever before... safely.
Itâs the missing coordination layer for GraphQL Federation, built for high-velocity teams scaling in the age of AI.
đď¸ Try it now for a free 14-day trial (no credit card required).
#GraphQL #GraphQLFederation #Federation #APIs #PlatformEngineering #AIEngineering #APIDesign #APIGovernance
Building Hub with our Customers (Live Discussion) xitter.cf/i/broadcasts/1NGaraovRâŚ
Automation can improve efficiency, but it canât replace empathy.
In our latest post, Viola shares why true customer success starts with human curiosity, not scripts.
Read more: wundergraph.com/blog/customeâŚ
New on the WunderGraph blog: Vincent Vermersch on combining CQRS, GraphQL Federation, and Event-Driven Subscriptions for a smoother developer experience.
Read it here đ wundergraph.com/blog/vincentâŚ
