The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Federation Alternatives
Similar projects and alternatives to federation
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
eleventy 🕚⚡️
A simpler site generator. Transforms a directory of templates (of varying types) into HTML.
-
insomnia
The open-source, cross-platform API client for GraphQL, REST, WebSockets, SSE and gRPC. With Cloud, Local and Git storage.
-
apollo-server
🌍 Spec-compliant and production ready JavaScript GraphQL server that lets you develop in a schema-first way. Built for Express, Connect, Hapi, Koa, and more.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
graphql-tools
:wrench: Utility library for GraphQL to build, stitch and mock GraphQL schemas in the SDL-first approach
-
subscriptions-transport-ws
Discontinued :arrows_clockwise: A WebSocket client + server for GraphQL subscriptions
-
supergraph-demo
🍿 Compose subgraphs into a Federation v1 supergraph at build-time with static composition to power a federated graph router at runtime.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
federation reviews and mentions
-
Apollo Federation Custom Scalars
I feel like we ran into this recently at work but not with custom scalars etc. My colleague raised an issue for it. Hope this helps in some way.
-
Apollo Federation Input type union merge
as per the Github issue here. However I have trouble understanding this statement. Why can't the gateway pick and choose which input fields are routed to each subgraph? Isn't it the responsibility of the supergraph SDL and the gateway to do exactly this, this same way it does for entities? What limitations are there that make merging input types using the union strategy not viable?
-
The Stack #3
Federation comes with its own specification and directives as part of it which helps people to define all of the relations between multiple GraphQL entities so that the Apollo Gateway can combine them all together without having to modify the GraphQL gateway and also functions like __resolveReference which helps in resolving an entity with its reference as specified by the directives.
-
A note from our sponsor - WorkOS
workos.com | 23 Apr 2024
Stats
apollographql/federation is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of federation is TypeScript.
Sponsored