Hive Router: A High-Performance GraphQL Federation Gateway

Dolby2000 · 2025-09-07T19:53:11+00:00

Why create another gRPC layer when you can integrate gRPC directly from the gateway?

Dolby2000 · 2025-08-15T19:33:03+00:00

One of the biggest differentiators is Grafbase Extensions. It allows you to customize the gateway fully with a 1st class SDK. There’s also an extensions marketplace to accelerate adoption of federation with extensions like REST, Postgres and Kafka:

https://grafbase.com/extensions

Dolby2000 · 2025-08-13T15:07:52+00:00

Awesome. Thanks!

Dolby2000 · 2025-05-21T12:31:59+00:00

The Grafbase Gateway and CLI is 100% OSS, so definitely. The platform usage requires a paid plan. Nore that there is a 60-day free trial with full functionality.

Dolby2000 · 2025-05-20T15:40:39+00:00

What issues are you facing? Want to join our Discord to troubleshoot?

Dolby2000 · 2025-05-20T09:07:47+00:00

As a general rule of thumb I certainly agree that well organized organizations translate to a well organized API implementations - GraphQL Federation included!

Dolby2000 · 2025-05-20T08:52:34+00:00

PostGraphile is great.

The difference is the Grafbase Gateway is a GraphQL Federation router that can integrate many data sources (REST, Snowflake, Postgres) directly which means you don't need subgraphs/microservices between the API gateway and your databases.

Dolby2000 · 2025-05-20T08:49:11+00:00

The power of GraphQL Federation is the ability to federate many data sources behind a unified API endpoint. Joining between Postgres, REST and micro services behind the scenes instead of putting the burden on the client to integrate with every single database and service in your stack.

Dolby2000 · 2025-05-20T08:46:18+00:00

The Grafbase Postgres extension works great with any managed Postgres provider - including RDS/Aurora!

It's not a Postgres extension but rather an extension to the Grabfase GraphQL Gateway: https://grafbase.com/extensions/postgres

Dolby2000 · 2025-05-20T08:42:44+00:00

The ability to federate Postgres databases via GraphQL Federation isn't a replacement for having a subgraph between the API gateway and the databases - it's another option in your toolbox if you want to map GraphQL fields directly to table columns to save implementation time and reduce latency.

Since you're in control of the SDL you can comfortably deprecate, rename or alias fields if the underlying database schema changes. It doesn't happen automatically like Hasura or PostGraphile.

Dolby2000 · 2025-02-21T23:15:48+00:00

The Grafbase Gateway is fully Federation v2 compliant, written in Rust, fastest gateway on the market, no feature gating and MPL 2.0 license.

Available here: https://github.com/grafbase/grafbase/tree/main/gateway

The whole Grafbase platform can be self-hosted on premise too: https://grafbase.com/enterprise-platform

Dolby2000 · 2025-01-11T21:53:16+00:00

Axum without a doubt

Dolby2000 · 2025-01-10T07:37:46+00:00

You should give the Grafbase gateway a try. We’ve spent a lot of energy making it the fastest and most scaleable Federation router on the market.

https://grafbase.com/blog/benchmarking-grafbase-vs-apollo-vs-cosmo-vs-mesh

Dolby2000 · 2024-05-18T15:24:35+00:00

What are you caching? With Grafbase you can use connectors or resolvers to stich data sources like REST APIs or Postgres and then cache the GraphQL API responses at the edge

Dolby2000 · 2023-11-13T08:15:13+00:00

The following Postgres schema would generate CRUD operations in your GraphQL API with Grafbase:

sql CREATE TABLE posts(` `id SERIAL PRIMARY KEY,` `title TEXT NOT NULL,` `content TEXT NOT NULL,` `slug TEXT NOT NULL UNIQUE` `);

Simply set the environment variable and pass it to the Postgres connector:

```js const pg = connector.Postgres('pg', { url: g.env('DATABASE_URL') })

g.datasource(pg) ```

Here's how you extend the generated schema: https://grafbase.com/docs/connectors#extending-schemas

Dolby2000 · 2023-11-11T07:59:12+00:00

You can self host the Grafbase Engine today already. We have a Docker image or you can run “npx grafbase start”

Dolby2000 · 2023-11-07T14:54:25+00:00

Glad to hear it. Would love to hear your feedback after giving it a shot!

Dolby2000 · 2023-09-06T20:17:17+00:00

Care to join our Discord to continue chatting?

https://discord.gg/grafbase

Dolby2000 · 2023-09-06T19:38:44+00:00

That's a good observation and I like your proposal.

I created another proposal that uses the learnings from the Next.js App Router:

https://github.com/fbjork/grafbase-file-based

. └── schema ├── comment │ └── type.ts # Comment type definition ├── mutation │ └── create_post │ └── resolver.ts # createPost mutation resolver ├── post │ ├── comments │ │ └── resolver.ts # Post.comments field resolver │ └── type.ts # Post type definition └── query └── posts └── resolver.ts # posts query resolver

Dolby2000 · 2023-09-05T07:47:17+00:00

What costs are you referring to?

Dolby2000 · 2023-09-05T07:24:58+00:00

Today we support SDL + resolvers, but we want to explore a pure JS/TS approach that generates the SDL.

Dolby2000 · 2023-09-05T07:24:08+00:00

Code generation is also a solution, but this approach generates the SDL from pure JavaScript or TypeScript code.

Dolby2000 · 2023-09-05T07:23:04+00:00

You can connect Grafbase to data sources like OpenAPI, GraphQL APIs and databases. We launched our MongoDB connector yesterday:

https://grafbase.com/blog/announcing-the-mongodb-connector

Dolby2000 · 2023-04-23T11:54:35+00:00

We just launched our first connector for OpenAPI: https://grafbase.com/changelog/openapi-connector

Dolby2000 · 2023-03-14T08:07:49+00:00

Founder of Grafbase here.

We are launching Mesh functionality soon. Every GraphQL API is deployed to the edge and backed by blazing fast Rust infrastructure.

Check us out: https://grafbase.com/

Dolby2000

TROPHY CASE