Skip to main content

路 One min read
Donna Zhou

We are pleased to announce the release of graphql-java v24.0.

This release is an unexpected breaking change release. It was made to help propagate a fix in the DataLoader library.

We consider v23.x poisoned and we don't recommend you use it because of the latent bug explained in the release notes on GitHub.

Going forward we will not be supporting v23.x, instead please skip this series and use v24.x going forward.

路 One min read
Donna Zhou

Update: please use the v24 series of releases instead of v23 releases. We have made a clearer breaking change in Java DataLoader, thus we will discontinue v23.

We are pleased to announce the release of graphql-java v23.0! Thanks to everyone in the community who contributed to the release, whether that was code, helping to report issues, or participating in discussions.

This is a breaking change release. Included are performance improvements and features.

For the full details, please see the release notes on GitHub.

路 2 min read
Andreas Marek

GraphQL Java has become a mature and widely adopted library over the past 9.5 years. And while we continue to maintain, improve and add features, we don't expect revolutionary changes to the core of the library.

As side effect of this maturity it became clear over the least years, that performance is a key aspect that users are interested in. Especially in larger scale applications performance can have a huge impact on operational costs and user experience.

In GraphQL Java we leverage JMH aka Java Microbenchmark Harness to measure and compare different performance aspects.

Historically, performance testing was done manually by running JMH benchmarks on a local machine.

This comes with the obvious flaw that it's not reproducible over time and across different machines. A benchmark run on one developer's machine is not comparable to a run on another developer's machine (or often even the same machine months later).

We are very happy to share that we have now an automated performance testing setup in place to overcome these limitations by running the benchmarks in an isolated cloud environment.

Currently, it runs on every commit to the master branch and the results are stored in the
performance results folder. You can visualize and compare results with the JMH Visualizer tool, a free tool which runs in the browser. Our goal is to provide clear and reproducible performance improvements over time while preventing any regressions.

This work is sponsored and made possible by Atlassian and we are very grateful for their support.

路 One min read
Donna Zhou

We are thrilled to announce the release of graphql-java v22.0! Thanks to everyone in the community who contributed to the release, whether that was code, helping to report issues, or participating in discussions.

This is a breaking change release, which includes major performance improvements. This release also introduces the @defer directive, which enables data to be received incrementally, rather than waiting until all data is resolved. This can reduce an application's time-to-interactive. See more on the @defer draft specification on the GraphQL Working Group's GitHub repo.

For the full details, please see the release notes on GitHub.