# Adopting GraphQL Federation at State Farm  - Our First Baby Steps

**URL:** <https://community.apollographql.com/t/adopting-graphql-federation-at-state-farm-our-first-baby-steps/8610>\
**Category:** API Design, Strategy & Governance\
**Tags:** federation, connectors, schema-design\
**Created:** [February 21, 2025, 5:30pm UTC](https://community.apollographql.com/t/adopting-graphql-federation-at-state-farm-our-first-baby-steps/8610 "2025-02-21T17:30:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![austinmehmetee2g](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/austinmehmetee2g/32/5764_2.png) [@austinmehmetee2g](https://community.apollographql.com/u/austinmehmetee2g)\
**Post date:** [February 21, 2025, 5:30pm UTC](https://community.apollographql.com/t/adopting-graphql-federation-at-state-farm-our-first-baby-steps/8610/1 "2025-02-21T17:30:40Z")

</div>

Howdy everyone, just wanted to shoot the community a link to a blog post State Farm released about our first steps into Federated GraphQL. Would love for everyone to check it out and provide feedback or ask questions if they have any

> **[Adopting GraphQL Federation at State Farm — Our First Baby Steps](https://engineering.statefarm.com/adopting-graphql-federation-at-state-farm-our-first-baby-steps-ec735c8f5195)**
>
> By Austin Mehmet and Brian Vanderbusch

---

<div class="post-metadata">

**Author:** ![Dan\_Boerner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/dan_boerner/32/5748_2.png) [@Dan\_Boerner](https://community.apollographql.com/u/Dan_Boerner)\
**Post date:** [February 21, 2025, 6:26pm UTC](https://community.apollographql.com/t/adopting-graphql-federation-at-state-farm-our-first-baby-steps/8610/2 "2025-02-21T18:26:53Z")

</div>

Great writeup and a classic story of initial “Proof of Value”.

> Our concept focused on modeling a policy retrieval system. This system allowed us to fetch policy details, agent details, claims details, and customer details all through a single supergraph. We ended up building 10 subgraphs that exposed 15 queries, 1 mutation, 63 types and 378 fields. Pages that would require multiple network requests to gather up the data they needed to paint a screen could now all be done with one call against our supergraph.

Note the difference between this and a very limited technical POC. They went after an important system, proved out the concept, but more importantly the value to the business and customer.

🙌 Well done @austinmehmetee2g and @undefined!  
It’s been so rewarding to work with your team ,and watch this project grow to deliver impact and real value to State Farm’s platform and customers.
