# How to implement federation using spring boot? Doucmentation talks about only "key", what about others?

**URL:** https://community.apollographql.com/t/how-to-implement-federation-using-spring-boot-doucmentation-talks-about-only-key-what-about-others/7467
**Category:** Schema Design
**Tags:** federation
**Created:** [May 2, 2024, 1:31pm UTC](https://community.apollographql.com/t/how-to-implement-federation-using-spring-boot-doucmentation-talks-about-only-key-what-about-others/7467 "2024-05-02T13:31:32Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![dkuc](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/dkuc/32/2892_2.png) [@dkuc](https://community.apollographql.com/u/dkuc)
#### Post date: [May 6, 2024, 2:51pm UTC](https://community.apollographql.com/t/how-to-implement-federation-using-spring-boot-doucmentation-talks-about-only-key-what-about-others/7467/4 "2024-05-06T14:51:53Z")

</div>

Hello 👋  
Since this information is the same for all subgraph implementations, we have documented it on our website → [Federation-specific GraphQL directives](https://www.apollographql.com/docs/federation/federated-types/federated-directives)

`@key` is the core concept behind federation as it is used to define entities and since we need to be able to somehow “enter” the subgraph to get additional info for entities we also need this extra entity resolver. All other directives are used for instrumenting the composition/query planner on how the requests should be processed - you just need to apply them to your schema but there is no code specific logic required in your subgraph. See linked docs for the details.

---

_[View the full topic](https://community.apollographql.com/t/how-to-implement-federation-using-spring-boot-doucmentation-talks-about-only-key-what-about-others/7467)._