# Subscription in federation 2

**URL:** <https://community.apollographql.com/t/subscription-in-federation-2/5838>\
**Category:** General\
**Tags:** federation\
**Created:** [March 1, 2023, 6:14am UTC](https://community.apollographql.com/t/subscription-in-federation-2/5838 "2023-03-01T06:14:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![killjoy2013](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/killjoy2013/32/2861_2.png) [@killjoy2013](https://community.apollographql.com/u/killjoy2013)\
**Post date:** [March 1, 2023, 6:14am UTC](https://community.apollographql.com/t/subscription-in-federation-2/5838/1 "2023-03-01T06:14:08Z")

</div>

Hi,  
will there be subscription support in apollo federation?  
I checked [federation-subscription-tools](https://github.com/apollosolutions/federation-subscription-tools) but it’s over complicating the scenario. We need a rather structured solution. To implement async communication between microservices (subgraphs), subscription is inevitable in apollo graphql federation I believe.

---

<div class="post-metadata">

**Author:** ![Bally](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/bally/32/4332_2.png) [@Bally](https://community.apollographql.com/u/Bally)\
**Post date:** [June 1, 2023, 7:57pm UTC](https://community.apollographql.com/t/subscription-in-federation-2/5838/2 "2023-06-01T19:57:24Z")

</div>

Hi, I’m in the same boat here, having a separate instance of apollo server that will only serve subscriptions seems to be overkill imo.

---

<div class="post-metadata">

**Author:** ![Justin\_Gonzalez](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/justin_gonzalez/32/5359_2.png) [@Justin\_Gonzalez](https://community.apollographql.com/u/Justin_Gonzalez)\
**Post date:** [February 6, 2025, 8:48pm UTC](https://community.apollographql.com/t/subscription-in-federation-2/5838/3 "2025-02-06T20:48:43Z")

</div>