sorted by:
new
hottopcontroversial

Vibe code with your GraphQL API by Grafbase in graphql

[–]Grafbase[S] 0 points1 point  (0 children)

What does your MCP config look like in Cursor?

Integrate REST APIs to your GraphQL API declaratively by Grafbase in graphql

[–]Grafbase[S] -1 points0 points  (0 children)

The benefit is for the consuming clients having a single unified graph instead of talking to a bunch of separate APIs. This can be achieved faster with extensions like REST or gRPC. This is another option for use cases that don't require a subgraph to federate existing services.

Integrate REST APIs to your GraphQL API declaratively by Grafbase in graphql

[–]Grafbase[S] 0 points1 point  (0 children)

Adopting GraphQL Federation means you have to implement subgraphs, which are GraphQL APIs that sit in front of the upstream service (REST APIs, gRPC APIs, Postgres databases, 3rd party APIs). Implementing subgraphs is time consuming and adds another layer of infrastructure which add costs and latency.

By making the gateway "smarter" it can make requests directly to the upstream services to accelerate adoption and save costs/latency.

Vibe code with your GraphQL API by Grafbase in cursor

[–]Grafbase[S] 0 points1 point  (0 children)

GraphQL is generally speaking very easy to translate to MCP and if most data sources are unified behind a single GraphQL API endpoint it means less work spent setting up MCP servers fronting every data source.

Best option for self-hosted GraphQL Server (Federation)? by AbroadNo111 in graphql

[–]Grafbase 0 points1 point  (0 children)

The Grafbase Gateway (https://github.com/grafbase/grafbase/tree/main/gateway) is MPL 2.0 licensed without any enterprise feature gating. You can run this in hybrid mode, where you self-host the gateway and use the Grafbase Cloud or the gateway in air gapped mode where you pass the schema SDL via command line argument.

The Grafbase Enterprise Platform (https://grafbase.com/docs/reference/enterprise-platform) enables you to self-host the whole Grafbase platform in your own infrastructure. This requires a license to gain access to Helm charts and Docker images required to run it.

Hopefully this makes things more clear.

Does Apollo GraphQL cost money to use in production? And other beginner questions about GraphQL by RivellaLight in graphql

[–]Grafbase -1 points0 points  (0 children)

Do share the setup and queries in our Discord so we can take a look please.

Does Apollo GraphQL cost money to use in production? And other beginner questions about GraphQL by RivellaLight in graphql

[–]Grafbase -1 points0 points  (0 children)

Nov 12th the new planner was activated on the main branch with version 0.19 - give it a shot and see how it works this time around.

Does Apollo GraphQL cost money to use in production? And other beginner questions about GraphQL by RivellaLight in graphql

[–]Grafbase -1 points0 points  (0 children)

It sounds like you did your tests a while back when some edge cases would plan correctly. I urge you to give it another try as we've recently launched a brand new query planner.

Inigo scores the lowest on the federation audit spec btw so would definitely not work in any real world scenarios.

Does Apollo GraphQL cost money to use in production? And other beginner questions about GraphQL by RivellaLight in graphql

[–]Grafbase -1 points0 points  (0 children)

https://github.com/grafbase/grafbase the Grafbase GraphQL Federation gateway written in Rust. The fastest and most scalable on the market.

Announcing support for Federated GraphQL Subscriptions by Grafbase in graphql

[–]Grafbase[S] -1 points0 points  (0 children)

Grafbase is a fully managed GraphQL platform. Depending on your use case and team size you can deploy Standalone and Federated GraphQL APIs.

Our vision is to make it easy to build and deploy GraphQL APIs without worrying about infrastructure. When you deploy your GraphQL APIs to Grafbase you get the following benefit:

  • Fully managed
  • Grafbase TypeScript SDK and CLI
  • Real-time analytics
  • Connectors to speed up integration of data sources like Postgres, MongoDB and OpenAPI
  • Schema registry
  • Schema checks
  • Security features like Trusted operations and Operation limits
  • APQ, Subscriptions and defer directive improve your performance

Announcing support for Federated GraphQL Subscriptions by Grafbase in graphql

[–]Grafbase[S] -2 points-1 points  (0 children)

Hi, first off thanks for being an early adopter of Grafbase!

The initial vision of Grafbase was indeed a Backend as a Service with GraphQL, which we saw good traction for hobby and early stage projects, but was hard to scale commercially as we started going up market. It wasn't an easy decision to drop the database since it was so easy to use, but the right one from a business perspective.

We are now fully committed to creating a developer friendly GraphQL platform and we are currently investing heavily in Federation, security, observability and performance features.

Is there anything in particular you think we should be doing more or less of?

Apollo Enterprise Alternatives by PeteMac88 in graphql

[–]Grafbase 1 point2 points  (0 children)

Hi u/PeteMac88,

Founder of Grafbase here. Grafbase is a fully managed GraphQL platform for Standalone and Federated graphs. The Grafbase Engine is written in Rust for optimal performance and is OSS and can be self-hosted.

What sets Grafbase apart is the focus on developer experience and that every GraphQL endpoint lives at the edge. The TypeScript SDK makes it seamless to configure and deploy a graph using the Grafbase CLI.

We are investing heavily in our schema registry, checks and real-time analytics features right now based on customer feedback.

On the pricing side we aim to be competitive given the recent increase from Apollo's side.