Add Fusion 16 Release Blog#9718
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a new “Fusion 16” release blog post to the website and updates the MDX compilation pipeline so relative image links in blog posts resolve to the /images/blog/... public asset path (matching the asset sync script behavior).
Changes:
- Added the Fusion 16 release blog post markdown.
- Extended blog post metadata to include the source folder and adjusted blog post rendering to compile MDX with a blog-specific image base URL.
- Updated MDX image path rewriting to support configurable base URLs (docs vs blog).
Reviewed changes
Copilot reviewed 4 out of 13 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
website/src/blog/2026-05-15-fusion-16/2026-05-15-fusion-16.md |
Adds the Fusion 16 release blog post content and embedded media references. |
website/lib/mdx.ts |
Allows MDX image path rewriting to use a caller-provided base URL (enables blog image paths). |
website/lib/blog.ts |
Adds folder to blog post metadata for blog-asset path resolution and bumps the HMR cache key. |
website/app/blog/[...slug]/page.tsx |
Passes a blog-specific image base URL into compileMdxContent for blog post rendering. |
Comments suppressed due to low confidence (1)
website/src/blog/2026-05-15-fusion-16/2026-05-15-fusion-16.md:145
- This benchmark table also uses
||at the start of each row, which introduces an empty column and can break Markdown table rendering. Use the standard single-|table syntax here as well.
| Gateway | Version | Median RPS | Best RPS | Worst RPS | CV% | Notes |
| :-------------------------- | :------------ | ---------: | -------: | --------: | ---: | :------------------------------------------ |
| hive-router | v0.0.49 | 1,590 | 1,618 | 1,585 | 0.7% | |
| hotchocolate | 16.1.0-p.1.10 | 1,441 | 1,463 | 1,434 | 0.6% | |
| cosmo | 0.307.0 | 1,136 | 1,152 | 1,127 | 0.9% | non-compatible response (2 across 2/9 runs) |
| grafbase | 0.53.3 | 1,121 | 1,142 | 1,110 | 0.9% | |
| hive-gateway-router-runtime | 2.5.25 | 511 | 522 | 507 | 1.0% | |
| apollo-router | v2.13.1 | 394 | 404 | 391 | 1.1% | |
| hive-gateway | 2.5.25 | 244 | 248 | 242 | 0.9% | |
| apollo-gateway | 2.13.3 | 236 | 239 | 234 | 0.7% | |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
72
to
76
| content, | ||
| readingTime: readingTime(content).text, | ||
| path: frontmatter.path, | ||
| folder: path.basename(path.dirname(file)), | ||
| }); |
Comment on lines
+123
to
+132
| | Gateway | Version | Median RPS | Best RPS | Worst RPS | CV% | Notes | | ||
| | :-------------------------- | :------------ | ---------: | -------: | --------: | ---: | :------------------------------------------ | | ||
| | hive-router | v0.0.49 | 2,889 | 3,082 | 2,866 | 2.6% | | | ||
| | hotchocolate | 16.1.0-p.1.10 | 2,140 | 2,175 | 2,127 | 0.8% | | | ||
| | grafbase | 0.53.3 | 2,061 | 2,101 | 2,024 | 1.2% | | | ||
| | cosmo | 0.307.0 | 1,255 | 1,273 | 1,246 | 0.7% | non-compatible response (2 across 2/9 runs) | | ||
| | hive-gateway-router-runtime | 2.5.25 | 541 | 553 | 535 | 1.0% | | | ||
| | apollo-router | v2.13.1 | 424 | 433 | 411 | 1.6% | | | ||
| | hive-gateway | 2.5.25 | 252 | 257 | 250 | 0.9% | | | ||
| | apollo-gateway | 2.13.3 | 238 | 240 | 236 | 0.6% | | |
Comment on lines
+151
to
+154
| One major reason why Rust and Go are chosen for gateways is performance, and while you can write really fast software with Rust it does not mean that .NET cannot be fast. I would even say, don't be fooled, .NET is really, really fast, especially when we are talking about work that involves IO like network calls. The whole request processing pipeline of Kestrel is blazing fast. | ||
|
|
||
| So we leaned into .NET and looked at the problems we needed to solve for a gateway, and they are essentially the same problems Kestrel had to overcome. | ||
|
|
| | hive-gateway | 2.5.25 | 244 | 248 | 242 | 0.9% | | | ||
| | apollo-gateway | 2.13.3 | 236 | 239 | 234 | 0.7% | | | ||
|
|
||
| With .NET 11, Microsoft is moving async execution into the runtime, eliminating the need for compiler tricks. This will allow us to reduce allocations even further and possible close the performance gap to the Hive ro. |
|
|
||
| ## ASP.NET Core | ||
|
|
||
| Every GraphQL gateway faces the same challenges and must implement core features like authentication, header propagation, retries, rate limits, observability, and more. While most gateways either reimplement these features and hiding them behind layers of configuration and closed binaries, we chose a different path. |
|
|
||
| ## Composite Schemas Working Group | ||
|
|
||
| A few years ago, together with Apollo and The Guild, we began working on an open specification for federated GraphQL under the GraphQL Foundation: the Composite Schema Specification. This specification is now nearing completion, and Fusion 16 fully implements the current version. Once finalized, it will be published as the official GraphQL Federation specification. Already today there are two gateways implementing the spec and two more that will announce adoption very soon. Its truly amazing to see how the GraphQL ecosystem has worked together to bring this specification to live and create true interoperability. |
This was referenced May 20, 2026
This was referenced May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.