docs: cdn mirror and circuit breaker (#7356)

Co-authored-by: Denis Badurina <badurinadenis@gmail.com>
Co-authored-by: Adam Benhassen <adambenhassen@hotmail.com>

Author: 3 people

packages/libraries/apollo/CHANGELOG.md

@@ -140,8 +140,8 @@
 
   const supergraphManager = createSupergraphManager({
     endpoint: [
-      'https://cdn.graphql-hive.com/artifacts/v1/9fb37bc4-e520-4019-843a-0c8698c25688/supergraph',
-      'https://cdn-mirror.graphql-hive.com/artifacts/v1/9fb37bc4-e520-4019-843a-0c8698c25688/supergraph'
+      'https://cdn.graphql-hive.com/artifacts/v1/9fb37bc4-e520-4019-843a-0c8698c25688',
+      'https://cdn-mirror.graphql-hive.com/artifacts/v1/9fb37bc4-e520-4019-843a-0c8698c25688'
     ],
     key: ''
   })
@@ -155,8 +155,8 @@
 
   const supergraphManager = createSupergraphManager({
     endpoint: [
-      'https://cdn.graphql-hive.com/artifacts/v1/9fb37bc4-e520-4019-843a-0c8698c25688/supergraph',
-      'https://cdn-mirror.graphql-hive.com/artifacts/v1/9fb37bc4-e520-4019-843a-0c8698c25688/supergraph'
+      'https://cdn.graphql-hive.com/artifacts/v1/9fb37bc4-e520-4019-843a-0c8698c25688',
+      'https://cdn-mirror.graphql-hive.com/artifacts/v1/9fb37bc4-e520-4019-843a-0c8698c25688'
     ],
     key: '',
     circuitBreaker: {

packages/web/docs/next-env.d.ts

@@ -1,5 +1,6 @@
 /// <reference types="next" />
 /// <reference types="next/image-types/global" />
+/// <reference types="next/navigation-types/compat/navigation" />
 /// <reference path="./.next/types/routes.d.ts" />
 
 // NOTE: This file should not be edited

packages/web/docs/src/app/blog/(posts)/how-we-shipped-cdn-access-tokens-with-cloudflare-workers-and-r2/page.mdx

@@ -33,7 +33,7 @@ sequenceDiagram;
   participant CDN Storage (R2)
 
   critical Validate Access Token
-    Client->>+CDN (CF Worker): Request GET /v1/artifact/c7ce447c-f5e6-4f13-87b8-d3051ba3fc45/sdl
+    Client->>+CDN (CF Worker): Request GET /artifacts/v1/c7ce447c-f5e6-4f13-87b8-d3051ba3fc45/sdl
     CDN (CF Worker)-->>-Client: Responds with 302 presigned URL
   end
   Client->>CDN Storage (R2): GET: presigned URL
@@ -76,7 +76,7 @@ sequenceDiagram;
   participant CDN Storage (R2)
 
   critical Validate Access Token
-    Client->>+CDN (CF Worker): Request GET /v1/artifact/c7ce447c-f5e6-4f13-87b8-d3051ba3fc45/sdl
+    Client->>+CDN (CF Worker): Request GET /artifacts/v1/c7ce447c-f5e6-4f13-87b8-d3051ba3fc45/sdl
     CDN (CF Worker)-->>-Client: Responds with 302 presigned URL
   end
   Client->>CDN Storage (R2): GET: presigned URL
@@ -202,7 +202,7 @@ the token validation method.
 Instead of verifying the CDN access token using an encryption secret environment variable, we would
 now instead load the R2 key based on the artifact target id being accessed.
 
-E.g. for the URL `/v1/artifact/c7ce447c-f5e6-4f13-87b8-d3051ba3fc45/sdl`, we would load the R2 key
+E.g. for the URL `/artifacts/v1/c7ce447c-f5e6-4f13-87b8-d3051ba3fc45/sdl`, we would load the R2 key
 `<bucket-name>/cdn-legacy-keys/c7ce447c-f5e6-4f13-87b8-d3051ba3fc45/` and then check the hash stored
 in that key, against the provided access key (the `X-Hive-CDN-Key` header value).
 
@@ -346,7 +346,7 @@ The `privateAccessKeyId` is never stored anywhere on our side, only the hash.
 The `"hv2"` prefix is a convenience for us for quickly identifying whether an access key sent to us
 is a legacy or new access token.
 
-E.g. for the URL `/v1/artifact/c7ce447c-f5e6-4f13-87b8-d3051ba3fc45/sdl`, we would load the R2 key
+E.g. for the URL `/artifacts/v1/c7ce447c-f5e6-4f13-87b8-d3051ba3fc45/sdl`, we would load the R2 key
 `<bucket-name>/cdn-keys/c7ce447c-f5e6-4f13-87b8-d3051ba3fc45/<access-key-id>`.
 
 We can read the `accessKeyId` from the `X-Hive-CDN-Key` header value.

packages/web/docs/src/app/product-updates/(posts)/2025-12-04-cdn-mirror-and-circuit-breaker/page.md

@@ -0,0 +1,57 @@
+---
+title: 'Enhanced CDN and Gateway Reliability'
+description:
+  Major improvements to our CDN infrastructure to ensure higher availability and resilience against
+  outages.
+date: 2025-12-05
+authors: [laurin]
+---
+
+We understand that the reliability of our High-Availability CDN is critical for your production
+GraphQL Gateway. Even a brief outage can have a significant impact.
+
+To further enhance the resilience of our systems, we've introduced two major improvements to
+mitigate potential outages of critical components for the Gateway.
+
+### CDN Mirror for High Availability
+
+We now operate a second CDN mirror, `cdn-mirror.graphql-hive.com`, built on AWS CloudFront. This
+mirror serves as a complete replica of our primary Cloudflare-based CDN. In the event of an outage
+with our main CDN, you can seamlessly switch to the mirror, ensuring your schemas and artifacts
+remain available.
+
+Our official SDKs have been updated to automatically handle this fallback when configured with both
+endpoints.
+
+### Circuit Breaker for Usage Reporting and CDN requests
+
+Failures are inevitable. To gracefully handle transient issues with our usage reporting service,
+we've implemented a Circuit Breaker pattern in our Hive SDKs and the Hive Gateway.
+
+If the client detects a series of failed requests to any origin, it will temporarily stop sending
+new request to that origin. This prevents your gateway or service from being overwhelmed with
+failing requests and allows it to run stable even if an outage on the CDN or usage reporting occurs.
+
+### Conclusion
+
+These improvements are now available for the Hive JS SDK and JavaScript Hive Gateway. We will soon
+also ship these improvements for the Hive Rust SDK, Hive Router and the Apollo Router Hive Plugin.
+
+Please upgrade to the following versions, and adjust your configuration to use the dual CDN.
+
+- Hive Gateway
+  [`v2.1.22`](https://github.com/graphql-hive/gateway/releases/tag/release-1764767579837)
+- [`@graphql-hive/yoga@0.46.0`](https://github.com/graphql-hive/console/releases/tag/%40graphql-hive%2Fyoga%400.46.0)
+- [`@graphql-hive/core@0.18.0`](https://github.com/graphql-hive/console/releases/tag/%40graphql-hive%2Fcore%400.18.0)
+- [`@graphql-hive/apollo@0.45.0`](https://github.com/graphql-hive/console/releases/tag/%40graphql-hive%2Fapollo%400.45.0)
+
+These updates are part of our ongoing commitment to providing a highly available and reliable schema
+registry for your GraphQL APIs.
+
+---
+
+**Further reading:**
+
+- [Running with Hive Console in Production: A High-Availability Guide](/docs/schema-registry/high-availability-resilence)
+- [CDN Documentation](/docs/schema-registry/high-availability-cdn)
+- [Hive Client Configuration (including Circuit Breaker)](/docs/api-reference/client#circuitbreaker)

packages/web/docs/src/content/api-reference/_meta.ts

@@ -1,7 +1,10 @@
 export default {
   'graphql-api': 'Public GraphQL API',
   cli: 'Hive CLI',
-  client: 'Hive Client Configuration',
+  client: 'Hive JavaScript Client',
+  'ruby-client': 'Hive Ruby Client',
+  'php-client': 'Hive PHP Client',
+  'rust-client': 'Hive Rust Client',
   'gateway-cli': 'Hive Gateway CLI',
   'gateway-config': 'Hive Gateway Configuration',
   'link-specifications': 'Hive GraphQL Link Spec',