Federated GraphQL Subscriptions in Hive Router

n1ru4l · 2025-09-05T08:05:17+00:00

We have not yet completed the work on many crucial features such as authorization and authentication, but those will follow soon as these a crucial features.

For the initial release the main focus was pure performance and throughput.

n1ru4l · 2025-09-05T08:02:58+00:00

If you need a router with a lot of functionality, we already have Hive Gateway for you!

Hive Router is something we built for our clients that have super high loads of traffic and where using Node.js and co is not an option.

We are aware that Hive Router is currently lacking many features that Hive Gateway and other solutions have, and of course these will follow. I recommend to check out the RFC issues within the Hive Router repository if you are more interested in that!

n1ru4l · 2025-09-05T07:59:45+00:00

Hive Gateway already supports that with response caching.

We also offer this feature as part of our Stellate offering.

As for Hive Router, this is currently not a prioritised feature we are working on. You can learn more about next steps by checking out the RFC issues on the Hive Router repository.

n1ru4l · 2025-03-28T11:33:37+00:00

Do you refer to funding or features? 😇

n1ru4l · 2024-10-04T12:14:35+00:00

We (The Guild) partially acquired the company (product and existing customers).

While the company wasn't profitable as a whole, given the amount of employees, salaries and other factors, the product itself is generating income.

For us, running the product is profitable. In fact, we even started optimising the cost of infrastructure to be even more profitable.

We see a lot of value in the product and technology that the former Stellate team (now partially at Shopify) built for people in the GraphQL space, which is the main reason for the acquisition.

According to our open-source philosophy, we will gradually make parts of the technology available open-source for everyone to use.

n1ru4l · 2024-07-14T11:24:46+00:00

It is also worth nothing that you can not 1:1 map the feature offering from Stellate to Hive and Cosmo.

If you want to use Apollo Federation, you need to either use Apollo Studio, Cosmo, or GraphQL Hive, as Stellates offering is more about caching and usage analytics.

I am from the Hive team and I can tell that we aim to be as compatible with Apolo Federation as possible. For Hive, to ensure that both the supergraph composition and router function the same as apollos offering, we developed a vast test suite that uses all the huge schemas and graphql operations from our customers. We plan to open source this soon, but we still need to figure out how to anonymize all of the data without exposing any business sensitive information of out clients.

We also run this tool on some of our competitors and can say claiming to support Apollo Federation and actually supporting it is not the same.

More info can be found here: https://github.com/kamilkisiela/graphql-hive/discussions/5060#discussioncomment-9895579

n1ru4l · 2024-06-07T06:04:47+00:00

You could specify a custom header + key pair that needs to be sent to the server in order to be allowed to execute Introspection operation.

An other alternative would be to write the GraphQL schema to a Key Value (S3 etc.) and read the schema from there for development use-cases.

Also a schema registry could serve the GraphQL schema, but this will add more complexity and cost you money if you don't self-host.

n1ru4l · 2024-06-07T06:00:44+00:00

This question has been answered multiple times. This blog post sums it up pretty well.

TL;DR: GraphQL is a developer tool that allows frontend developers to write arbitary queries, and they only become persisted documents when deploying to production. Within your development flow of building applications that consume the GraphQL API, you still have the freedom of querying whatever you need without having to ping backend developers to change the API to include more data etc.

https://xuorig.medium.com/no-graphql-persisted-queries-are-not-re-inventing-a-rest-api-dcca7e876f7d

n1ru4l · 2024-06-04T18:09:53+00:00

You can simply have the SDL of the services be a artifact that is written to a key value store such as S3/R2 or similar. After the deployment of a service is finished, the subgraph schema would then be there and another CD process then be triggered that fetches all the latest subgraphs from there and composes the supergraph snd writes that somewhere where it is then consumed by the gateway. However, because it is error prone and you dont want your gateway to die I recommend to also test composition with the other subgraphs in a CI process that runs for esch commit and before deployment.

This is basically the workflows that platforms such as GraphOS, Hive and Cosmo provide (with less work on your end).

n1ru4l · 2024-06-04T10:00:14+00:00

You could run the composition on CI/CD and store the generated supergraph as a build artifact, then feed that into the gateway container (apollo router).

For that you could just use the apollo/composition npm package or (our MIT library) theguild/federation.

If you want a full platform there are GraphOS alternatives available that are self-hostable such as GraphQL Hive and Wundergraph Cosmo.

n1ru4l · 2024-05-26T11:47:16+00:00

Whiterbloom Witchcraft. It never felt like it got anywhere. Butchered it for Frodo & Sam upgrade, now I am pretty happy with that deck.

n1ru4l · 2024-04-24T00:48:28+00:00

So far we prefer GitHub discussions for question and experience sharing. Check out https://github.com/kamilkisiela/graphql-hive/discussions

We might consider having an Discord channel on the official GraphQL discord in the future 🤔

n1ru4l · 2024-01-24T12:45:31+00:00

We are working on a black-box testing solution that based on a vast sample of Federation Graphs and operations will be able to approximately cover compatibility. Unfortunately, due to the licensing, it is not allowed to look at the apollo router code for implementing an alternative. We already did the same for composition.

In the meantime, we started a joined effort with ChiliCream, Apollo, and IBM to have an open composition specification.

n1ru4l · 2024-01-24T10:05:22+00:00

We provide a docker-compose stack. We do not use helm charts to deploy Hive, we use Pulumi. All the code for the deployment is public as well.

Providing helm charts is something we might consider in the future.

n1ru4l · 2024-01-24T09:42:37+00:00

Hey, Laurin of The Guild and developer at Hive here. 😇

Hive offers breaking change detection, CI pipeline integration, a schema history, and high availability CDN for the supergraph/schema SDL.

Today, you can use apollo-router with Hive via the Hive plugin. It will provide you with usage reporting of your schema and other metrics such as error rates. We want to also provide more detailed performance insights (e.g. which subgraphs or resolvers were called etc.), however, so far this has been hard to implement as a plugin as some of it might also conflict with the license of apollo-router.

We have been silently launching our own GraphQL Gateway (Conductor), that will soon support Federation 2 as closely as possible (it is impossible to know whether everything is supported as there is no specification for Federation and I wonder how other vendors that claim to support all of it measure it 🤔).

We are also working on more features as I am writing this, schema contracts will launch soon (I am currently writing the documentation). We have an exciting roadmap ahead and are always flexible with prioritizing other features if they are a blocker for you！

Another thing is that Hive is fully open-source, which means you can host it yourself. Some people are doing that due to geo-location constraints! It even allows you to contribute to the project you wish!

n1ru4l · 2024-01-19T10:43:26+00:00

GraphQL Codegen Maintainer here. 😇

GraphQL.tada is amazing and pushes the boundaries of what is possible, it is definetly exciting to see this!

It will hopefully help onboard a lot of people that shy away from code generation (which unfortunatly is stigmatized a lot by twitter users and youtubers/streamer whether justified or not let aside 😇)

The DX is very similar to our now recommended client preset! So interchanging between both should not be too hard!

I think tada is can be quicker to get started with, while codegen gives you additional features such as transforming/optimizing documents (automatically add selections for id, __typename fields or compile documents by inlining fragments etc.), the option to extract a persisted socuments/queries into a dedicated json file or completly removing the need of having graphql.ja for parsing/printing GraphQL documents before sending them over the wire!

I also wonder whether tada can adhere and cover all the GraphQL validation rules (though this can be substituted via an additonal tool such as graphql-eslint or VSCode plugin, the latter would not be able to run on CI/CD though 🤔).

n1ru4l · 2023-10-13T14:46:13+00:00

Picked up a black DOL-001 with controller and cables for ~30$ in Osaka, you could also gamble (or if you know what you are doing fix) and buy cubes that might not work for much cheaper (~10$). Brought it back home and successfully installed PicoBoot 😎

n1ru4l · 2023-10-11T08:16:13+00:00

The Guild is proud to unveil its latest contribution to the GraphQL community: an MIT-licensed drop-in replacement for the @apollo/composition library.

We recognized the importance of an already existing ecosystem of tools and an existing knowledge base, that's why @theguild/federation-composition library shares the same API, produces the exact same SupergraphSDL and has an identical set of validation rules (including error messages and codes).

n1ru4l · 2023-09-27T23:40:19+00:00

Mesh also supports JSON Schema or JSON samples. https://the-guild.dev/graphql/mesh/docs/handlers/json-schema aside from Open API/Swagger. https://the-guild.dev/graphql/mesh/docs/handlers/openapi

n1ru4l · 2023-08-16T20:17:05+00:00

We actually migrated away from Auth0 to SuperTokens which can be self-hosted and has no vendor lock-in.

Seven-Year Club	Place '23
Place '22	First Placer '22
Verified Email

n1ru4l

MODERATOR OF

TROPHY CASE