Skip to main content

Vert.x Web GraphQL extends Vert.x Web with the GraphQL-Java library so that you can build a GraphQL server.

This is the reference documentation for Vert.x Web GraphQL. It is highly recommended to get familiar with the GraphQL-Java API first. You may start by reading the GraphQL-Java documentation.
This module has Tech Preview status, this means the API can change between versions.

Getting started

To use this module, add the following to the dependencies section of your Maven POM file:


Or, if you use Gradle:

compile 'io.vertx:vertx-lang-ruby:3.7.0'

Handler setup

Create a Vert.x Web Route and a GraphQLHandler for it:

require 'vertx-web-graphql/graph_ql_handler'
graphQL = setup_graph_ql_java()


The handler serves both GET and POST requests. However you can restrict the service to one type of HTTP method:

require 'vertx-web-graphql/graph_ql_handler'
graphQL = setup_graph_ql_java()"/graphql").handler(&VertxWebGraphql::GraphQLHandler.create(graphQL).method(:handle))
The GraphQLHandler does not require a BodyHandler to read POST requests content.

Enable query batching

Query batching consists in posting an array instead of a single object to the GraphQL endpoint.

Vert.x Web GraphQL can handle such requests but by default the feature is disabled. To enable it, create the GraphQLHandler with options:

require 'vertx-web-graphql/graph_ql_handler'
options = {
  'requestBatchingEnabled' => true

handler = VertxWebGraphql::GraphQLHandler.create(graphQL, options)

Building a GraphQL server

The GraphQL-Java API is very well suited for the asynchronous world: the asynchronous execution strategy is the default for queries (serial asynchronous for mutations).

To avoid blocking the event loop, all you have to do is implement data fetchers that return a CompletionStage instead of the result directly.

Code not translatable

Fetching data with callback-based APIs

Implementing a data fetcher that returns a CompletionStage is not a complex task. But when you work with Vert.x callback-based APIs, it requires a bit of boilerplate.

This is where the VertxDataFetcher can help:

Code not translatable

Providing data fetchers with some context

Very often, the GraphQLHandler will be declared after other route handlers. For example, you could protect your application with authentication.

In this case, it is likely that your data fetchers will need to know which user is logged-in to narrow down the results. Let’s say your authentication layer stores a User object in the RoutingContext.

You may retrieve this object by inspecting the DataFetchingEnvironment:

dataFetcher = { |environment,future|

  routingContext = environment.get_context()

  user = routingContext.get("user")

  retrieve_links_posted_by(user, &future)

The routing context is available with any kind of data fetchers, not just VertxDataFetcher.

If you prefer not to expose the routing context to your data fetchers, configure the GraphQL handler to customize the context object:

require 'vertx-web-graphql/graph_ql_handler'
dataFetcher = { |environment,future|

  # User as custom context object
  user = environment.get_context()

  retrieve_links_posted_by(user, &future)


graphQL = setup_graph_ql_java(dataFetcher)

# Customize the query context object when setting up the handler
handler = VertxWebGraphql::GraphQLHandler.create(graphQL).query_context(lambda { |routingContext|

  return routingContext.get("user")



JSON data results

The default GraphQL data fetcher is PropertyDataFetcher. As a consequence, it will be able to read the fields of your domain objects without further configuration.

Nevertheless, some Vert.x data clients return JsonArray and JsonObject results.

If you don’t need (or don’t wish to) use a domain object layer, you can configure GraphQL-Java to use VertxPropertyDataFetcher instead:

Code not translatable
VertxPropertyDataFetcher wraps a PropertyDataFetcher so you can still use it with domain objects.

Using dataloaders

Dataloaders help you to load data efficiently by batching fetch requests and caching results.

First, you must configure the GraphQL object to use the DataLoaderDispatcherInstrumentation:

dispatcherInstrumentation =

graphQL = Java::Graphql::GraphQL.new_graph_ql(graphQLSchema).instrumentation(dispatcherInstrumentation).build()

Then create a batch loader:

linksBatchLoader = lambda { |keys,environment|

  return retrieve_links_from_backend(keys, environment)

If you work with Vert.x callback-based APIs, you may use a VertxBatchLoader to simplify your code.

Eventually, configure the GraphQLHandler to create a DataLoaderRegistry for each request:

Code not translatable