Enhance customer experiences with Apollo GraphOS


<p>Did you know mobile application performance was the use case that drove the initial development of GraphQL? GraphQL has grown by leaps and bounds and is now used to power entire API platforms, but it remains an essential part of the mobile application developer’s toolkit.  To that end, we are excited to launch new, free courses for <a href="https://www.apollographql.com/tutorials/apollo-ios-swift-part1">iOS</a> and <a href="https://www.apollographql.com/tutorials/apollo-kotlin-android-part1">Android</a> developers in the Apollo Odyssey learning platform!</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="666" src="https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-1024x666.png" alt="The image is a screenshot of a webpage from the Apollo GraphQL Odyssey tutorial series titled “Apollo iOS and Swift: Pagination, Mutations, and Subscriptions”. The tutorial section displayed is “Complete the details view”. The page includes a heading titled “Test the DetailView”, followed by instructions guiding users to build and run their application, verifying that clicking on a launch item navigates to a corresponding DetailView.

There are two prominent visuals on the page:
	1.	A screenshot of an Xcode editor showing SwiftUI code for handling the DetailView.
	2.	An iPhone simulator displaying a detailed launch view with a mission patch, launch details, and a “Book Now!” button.

The left sidebar contains a navigation menu with sections:
	•	Introduction
	•	Complete the details view (highlighted)
	•	Write your first mutation
	•	Authenticate your operations
	•	Define additional mutations
	•	Paginate results
	•	Write your first subscription

Below the main content, there is a paragraph mentioning that the “Book Now!” button has been added but isn’t functional yet, leading into the next section about making changes with GraphQL mutations, including authentication." class="wp-image-24074" srcset="https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-1024x666.png 1024w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-300x195.png 300w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-768x499.png 768w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-1536x999.png 1536w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-2048x1332.png 2048w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-1200x780.png 1200w, https://wp.apollographql.com/wp-content/uploads/2025/02/Screenshot-2024-09-03-at-1.23.36 PM-1980x1287.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#apollo-ios-and-apollo-kotlin" aria-hidden="true" class="aal_anchor" id="apollo-ios-and-apollo-kotlin"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Apollo iOS and Apollo Kotlin</h2>



<p>Apollo is proud to maintain the most widely-used free and open source GraphQL clients for web and mobile platforms.  <a href="https://www.apollographql.com/docs/ios">Apollo iOS</a> and <a href="https://www.apollographql.com/docs/kotlin">Apollo Kotlin</a> are trusted by thousands of iOS and Android teams to power their production applications written in Swift and Kotlin.  In order to fully leverage these industry-standard tools, a grasp of the fundamentals is essential.</p>



<p>App development teams getting started with GraphQL now have access to new two-part courses:</p>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/tutorials/apollo-ios-swift-part1">Apollo iOS and Swift</a></li>



<li><a href="https://www.apollographql.com/tutorials/apollo-kotlin-android-part1">Android Development with Apollo Kotlin</a></li>
</ul>



<p>All of these courses are part of our expansive and free Apollo Odyssey platform.  There’s plenty more where that came from, too: check out our extensive library of courses for UI developers, backend developers, and platform engineers.</p>



<p>If you have any ideas for new courses, please post your feedback in this <a href="https://community.apollographql.com/t/new-odyssey-courses-for-apollo-kotlin-and-apollo-ios-post-your-feedback-here/8678" data-type="link" data-id="https://community.apollographql.com/t/new-odyssey-courses-for-apollo-kotlin-and-apollo-ios-post-your-feedback-here/8678">Apollo Community thread</a>!  We’re always eager to hear what people want to learn about next.</p>


New GraphQL courses for iOS and Android development

What’s New in GraphOS: Apollo Winter ’25 Release – Apollo Connectors, Native Query Planner, Improved Tools, and More!


<p>Today we are releasing <a href="https://www.apollographql.com/graphos/apollo-connectors">Apollo Connectors</a>, a major update that brings our declarative, graph-based orchestration technology to teams using REST APIs.</p>



<p>Modern applications integrate dozens or even hundreds of different APIs. The task is significant. These APIs must be called in a precise manner and sequence. API calls need to be chained together, feeding the output of one into the next. In some cases, it’s desirable to parallelize them for better performance. Synchronous services can be made async, and vice versa. Almost universally, it is necessary to filter, transform, and reformat the responses, as they are rarely an exact match for the needs of an application. Teams must properly handle errors and timeouts, not to mention authentication and authorization.</p>



<p>We can give a name to these tasks: API orchestration.</p>



<p>API orchestration accounts for a significant fraction of the total cost of implementing software. It shows up everywhere: application teams shipping roadmap items, companies migrating off of legacy software systems or onto modern microservice architectures, anyone acquiring products and integrating them together, and in every agentic AI project – the last of these especially top of mind now for many. And because orchestration requirements tend to be unique to each individual application or use case, teams end up accumulating a mountain of code dedicated to orchestration.</p>



<p>In the vast majority of cases, API orchestration is implemented procedurally, as code. This is the world of backends-for-frontends, integration APIs, and SDKs autogenerated from service catalogs. Sometimes the code is implemented as a separate tier, as in the BFF pattern. Other times, it lurks inside applications or services. No matter where it lives, this code is expensive to write and annoying to maintain. It holds API-rich companies back from shipping great products and getting the most value from their API investments.</p>



<h3 class="wp-block-heading"><a href="#graphql-is-graph-based-api-orchestration" aria-hidden="true" class="aal_anchor" id="graphql-is-graph-based-api-orchestration"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL is graph-based API orchestration</h3>



<p>What we’ve known all along is that GraphQL is really a technology for API orchestration. GraphQL federation, which we developed in collaboration with many of the teams using GraphQL at large scales, allows developers to write GraphQL queries that get executed as an automatically planned sequence of individual API calls. The heart of what makes this possible is an advanced runtime, the <a href="https://www.apollographql.com/graphos-router">Apollo Router</a>, that provides connection management, rate limits, error handling, API call chaining and more, all made available through GraphQL schemas and operations.</p>



<p>Most of the API orchestration tasks I listed above? They’re built right into the Apollo Router with our implementation of <a href="https://www.apollographql.com/federation">GraphQL federation</a>. Apollo developers don’t write procedural code to cache API responses, enforce authentication policies, filter results, or join across APIs. To give one example of how much power comes with this, you can mark part of a query as “deferrable” which instructs the query planner to break the query into a synchronous portion and an async portion to be delivered later – typically data coming from slow APIs that you can’t allow to delay app interactivity or a screen render. Six characters and a couple of braces replace what would have been a significant amount of procedural code to write, test, and maintain.</p>



<p>GraphQL federation has been a huge success. It now powers many of the largest online retailers, media properties, traditional banks, and fintech startups. It’s probably inside your television and will almost certainly be in your next car. Companies that adopt this architecture are able to ship new products in a fraction of the time it used to take and with far less development risk.</p>



<h3 class="wp-block-heading"><a href="#bringing-graphql-to-everyone" aria-hidden="true" class="aal_anchor" id="bringing-graphql-to-everyone"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Bringing GraphQL to everyone</h3>



<p>There’s one hitch, though. To use graph-based API orchestration, you needed GraphQL APIs – either by adding GraphQL to existing services or by creating new GraphQL-specific services (what GraphQL federation developers call “subgraph servers”). This requirement was a significant up-front price of admission to the benefits of graph-based orchestration. And hearing customer after customer tell us about the REST APIs they wanted to bring to the graph led us to a key insight, which is that the responses from these APIs are awfully close to the entity objects that make up a federated GraphQL schema. All that’s really necessary is a language for describing the relationship between them.</p>



<p>And that leads us to today’s news: we’re making <a href="https://www.apollographql.com/graphos/apollo-connectors">Apollo Connectors</a> for REST APIs generally available, which lets you define a GraphQL schema in terms of the REST APIs you have and orchestrate calls to those APIs with just a few lines of configuration. </p>



<p>Connectors are meant to work with real-world APIs: they include functions you can use to restructure and transform API responses as needed and support the usual patterns for headers, auth credentials, and so on. And it’s just federated GraphQL under the hood, so you can use all the usual federation features and mix and match any combination of REST and GraphQL together. You can read much more technical detail about how Apollo Connectors work in our <a href="https://www.apollographql.com/blog/our-journey-to-apollo-connectors">engineering blog</a>, the <a href="https://www.apollographql.com/docs/graphos/schema-design/connectors">documentation</a>, or just give it a try with your own APIs. Everything you need is included in our free tier of GraphOS and you can be orchestrating APIs in well under an hour.<br>Since we <a href="https://www.apollographql.com/events/exploring-apollo-s-new-products-a-deep-dive">previewed Apollo Connectors</a> at GraphQL Summit in October we’ve worked with many of you to improve every aspect of their tooling and functionality. Early results are promising: you can read about how the team at <a href="https://www.apollographql.com/customers/cox-automotive">Cox Automotive </a>used Apollo Connectors to add a particularly important API to their graph in just days, saving nearly a year of otherwise planned development work. We’re looking forward to hearing about your experience.</p>



<h3 class="wp-block-heading"><a href="#the-future-is-declarative" aria-hidden="true" class="aal_anchor" id="the-future-is-declarative"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>The future is declarative</h3>



<p>Declarative architectures define the modern, cloud-native stack. Containerization for packaging software. React for packaging UI components. It should be no different for APIs.  Apollo Connectors allows developers to describe the data model they want, and let Apollo&#8217;s graph-based API orchestration infrastructure figure out how to do it.</p>



<p>We believe declarative, graph-based orchestration is going to replace procedural orchestration code. We’re excited to see GraphQL become the standard that all developers can reach for and we’re committed to working with everyone interested to make that happen. And we can’t wait to see what you build with it.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>Ready to get started? Try Connectors today with <a href="https://studio.apollographql.com/signup?referrer=blog">our new free tier</a>, explore our <a href="https://www.apollographql.com/docs/">documentation</a> and<a href="https://www.apollographql.com/tutorials/"> Odyssey training courses</a>, or join us at upcoming <a href="https://www.apollographql.com/events">Connectors Live events</a> to learn more. The future of APIs is here – powered by GraphQL-based API orchestration that makes it easier than ever to build applications.</td></tr></tbody></table></figure>


REST API Orchestration With GraphQL

Our Journey to Apollo Connectors


<p>We&#8217;re announcing an important update: starting with the 1.60 release of <a href="https://www.apollographql.com/graphos-router">Apollo GraphOS Router</a> and Apollo Router Core coming in the next few weeks, <a href="https://www.apollographql.com/federation">Apollo Federation</a> 1.0 supergraphs will no longer be supported. This update accompanies the introduction of a <a href="https://www.apollographql.com/docs/graphos/routing/query-planning/native-query-planner">new native query planner</a> in these Apollo Router versions, marking a significant advancement in our technology. <a href="https://www.apollographql.com/docs/graphos/reference/migration/to-federation-version-2">Upgrading to Apollo Federation 2.0</a> is essential to leverage these improvements fully, and as Federation and Apollo Router are mission-critical infrastructure for your API workloads, we are here to guide you through every step of this transition to confidently operating your GraphQL platform.</p>



<p><strong>Understanding the importance of upgrading</strong></p>



<p>The next Apollo Router versions, 1.60 and beyond, include a new native query planner with significant performance enhancements. Our extensive testing of over 620 million operations showed a median 10x improvement in query planning time, a 2.9x reduction in CPU utilization, and a 2.2x reduction in memory consumption. Designed specifically for Federation 2.0 supergraphs, this new query planner simplifies maintenance and enhances security by eliminating dependencies, including the need for a JavaScript execution engine within the Apollo Router process.</p>



<p><strong>Timeline and planning</strong></p>



<p>Federation 1.0 supergraphs have been marked as deprecated in our <a href="https://www.apollographql.com/graphos/studio">GraphOS Studio</a> UI and users have not been able to create them since Q3 2023. With the upcoming new Apollo Router versions, support for Federation 1.0 supergraphs will end across all Apollo products, including Apollo Gateway. We strongly recommend you upgrade to Apollo Router and Federation 2.0 to ensure continued compatibility with our latest innovations.</p>



<p>If you are still operating your GraphQL deployment without having yet migrated to Federation 2.0, upgrading to the new query planner in Apollo Router 1.60 and beyond will introduce a breaking change.&nbsp;</p>



<p>Migration to Federation 2.0 is simple and focuses on the composition layer, without requiring changes to existing subgraphs in most cases. You only need to compose a supergraph with Federation 2.0 and typically your subgraphs can continue using Federation 1.0 until they need 2.0 features. Our<a href="https://www.apollographql.com/docs/graphos/reference/migration/to-federation-version-2"> migration guide</a> details how you can update just your Federation composition step to compile a compatible supergraph.</p>



<p><strong>Available resources and ongoing support</strong></p>



<p>We recognize that transitioning from Federation 1.0 to Federation 2.0 is a significant step for some of our users. This decision reflects our commitment to eliminating the complexities of outdated technology and ensuring our offerings meet the evolving needs of modern API infrastructures. We are dedicated to transparent communication and improving our deprecation processes to help maintain the robustness, efficiency, and security of your systems.&nbsp;</p>



<p>Apollo values your partnership and trust as we continue to innovate. We are here to support you through this transition to keep your API infrastructure powerful and future-proof. For additional support, please visit our <a href="https://community.apollographql.com/t/migrate-apollo-federation-1-0-supergraphs-to-apollo-federation-2-0/8125">Apollo Community</a> or, for GraphOS users, contact our Technical Support team at <a href="mailto:support@apollographql.com">support@apollographql.com</a>. </p>



<p></p>


Migrate Apollo Federation 1.0 Supergraphs to Apollo Federation 2.0


<p>Writing resolvers for REST APIs has been a rite of passage for developers working with GraphQL, but what if there were an easier way? Meet Apollo Connectors.&nbsp;&nbsp;</p>



<p>As shown in Figure 1, Apollo Connectors mitigate the need to write code that connects to and returns data from REST APIs, reducing code surface area and time so you can focus on the business problem you&#8217;re trying to solve.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdJZU6oZN7MiGs9r1tQQXZkwJJpcuPFikCrKor3lk6x3MroNldHwChst6pbHyV0h2d8fx0bdhmW7xxntWRZCNWhxOe3ZrMe-lt0P1_MZQ16jxNuOmPkQdayuZT_XW9cF_69YpmiEA?key=Tfq51hg4_0CBkUiIKxkXplEo" alt=""/></figure>



<p><em>Figure 1: Data flow showing Apollo Connector for REST APIs</em></p>



<p>In this article, we will walk through a React client web application that leverages the Apollo GraphQL client to call a public <a href="https://currencyapi.com/">CurrencyAPI</a> web service using the REST API Apollo Connector for REST APIs.&nbsp; A screenshot of the UI is seen in the following figure:&nbsp;&nbsp;</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdmYwlhbO07vkGGfTIugVC2usLpczle-KJMiJoGsGgE53FYx4zzzo3TFsFiMJ5InCSTzJ7HA7cSxtF9HRXJLQ7j6zhZ1jatfDn1WGDFQ2sY-ixRi7Fmpz-HNH2TQPQiOOmat7an?key=Tfq51hg4_0CBkUiIKxkXplEo" alt=""/></figure>



<p><em>Figure 2: Screenshot of the Currency Converter</em></p>



<p>Under the covers, the React app uses the GraphQL Client as usual and issues the query statement.&nbsp; There are no changes there.&nbsp; On the backend, you simply define the GraphQL schema file and that’s it. There is no need to create resolvers to fetch the data from the REST API.&nbsp; In the following sections, you will learn how to set up and configure the Apollo Connector for REST APIs.</p>



<h1 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting Started</h1>



<p>In this article we will use a third party service called CurrencyAPI to fetch real-time currency exchange rates.&nbsp; At the time of this writing (Nov 2024), CurrencyAPI offers a free API key.&nbsp; If you wish to follow along, create an API key from <a href="https://currencyapi.com/">https://currencyapi.com/</a> and copy it down, as you will need it later.</p>



<p>You will also need an Apollo account and the latest version of Apollo Rover CLI.&nbsp; See sections 1 and 2 of the following Apollo Connector tutorial for installation instructions:</p>



<p><a href="https://www.apollographql.com/tutorials/connectors-intro-rest/02-setup">https://www.apollographql.com/tutorials/connectors-intro-rest/02-setup</a></p>



<p>Next, clone the repository.</p>



<p><code>git clone https://github.com/RWaltersMA/CurrencyConverter.git</code></p>



<h2 class="wp-block-heading"><a href="#obtain-api-keys-and-configure-demo" aria-hidden="true" class="aal_anchor" id="obtain-api-keys-and-configure-demo"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Obtain API keys and configure demo</h2>



<p>At the time of this writing, Apollo Connectors is in preview with an anticipated general availability in early 2025.&nbsp; This blog will be updated as this feature evolves.</p>



<p>Now, we are ready to configure Apollo Studio and obtain our API Key.&nbsp; Navigate to <a href="http://studio.apollographql.com/?_gl=1*tm0r8z*_gcl_aw*R0NMLjE3MzE3MDM4ODQuQ2owS0NRaUFfOXU1QmhDVUFSSXNBQmJNU1BzRm5OM1NIXzRWQWN2VHJGRFBrQkctcVltVk9ncU1iLUJjczh4YkpBOVlUZzFGQ3MyWngwZ2FBaHBfRUFMd193Y0I.*_gcl_au*MTM2NzI4NDM4Ny4xNzMwMjIwNjQ0">Apollo Studio</a> and click “Create a new Graph.”&nbsp; In the “Publish your schema using Federation” dialog, you will see toward the bottom the API Key to be used with Rover.</p>



<p>Below is a sample:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session">APOLLO_KEY=service:Currency-02wxjh:xxxxxxxxxxxxxxx \
  rover subgraph publish Currency-02wxjh@current \
  --schema ./products-schema.graphql \
  --name your-subgraph-name \
  --routing-url http://products.prod.svc.cluster.local:4001/graphql</code></pre>



<p>Copy the value for <code>APOLLO_KEY</code>.&nbsp; Open the <code>rover-dev.md file</code> and update the section with your personalized <code>APOLLO_KEY</code>.&nbsp; Copy the service name to <code>APOLLO_GRAPH_REF</code> and save the file.</p>



<p>Next, update the <code>router-config.yaml</code> file and replace the placeholders “&lt;&lt;REPLACE&gt;&gt;” with the API Key you obtained from currencyAPI and save this file.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml">preview_connectors:
  subgraphs:
    currency:
      $config:
        # Replace this value with your currencyAPI key
        apikey: &lt;&lt;REPLACE&gt;&gt;</code></pre>



<p>Now, we are ready to start a local Apollo instance.&nbsp; Copy and paste into a terminal the <code>rover dev</code> statement that is within your <code>rover-dev.md </code>file.&nbsp; For example, the command for <code>sh</code> looks like the following:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-shell-session">APOLLO_KEY=&quot;service:Currency-02wxjh:xxxxxxxxxx&quot; \
APOLLO_GRAPH_REF=&quot;Currency-02wxjh@current&quot; \
APOLLO_ROVER_DEV_ROUTER_VERSION=2.0.0-preview.1 \
rover dev --supergraph-config supergraph.yaml --router-config router-config.yaml</code></pre>



<p>If successful, the console will display the following:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-">supergraph config loaded successfully
warning: Do not run this command in production! It is intended for local development only.
==&gt; Watching /Users/robwalters/Code/CurrencyConverter/currency.graphql for changes
WARN: Connector debugging is enabled, this may expose sensitive information.
==&gt; your supergraph is running! head to http://localhost:4000 to query your supergraph
successfully composed with version =2.10.0-preview.0
successfully composed with version =2.10.0-preview.0 after updating the &#039;currency&#039; subgraph</code></pre>



<div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained">
<p>A note about <code>router-config.yaml</code>:&nbsp; In this example, we are launching a react client on the same machine as Rover.&nbsp; Since these are operating on different ports, the client on localhost:4000 and Rover on localhost:3000, the server needs to address CORS (Cross origin resource sharing).&nbsp; To do this, we added the following configuration to the <code>router-config.yaml </code>file:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml">cors:
  allow_any_origin: true</code></pre>
</div></div>



<p>Note that setting CORS to allow any origin option is not recommended for production use unless necessary.&nbsp; For more information on configuration parameters in the router, check out the <a href="https://www.apollographql.com/docs/graphos/reference/router/configuration#yaml-config-file">online documentation</a>.</p>



<h1 class="wp-block-heading"><a href="#starting-the-client" aria-hidden="true" class="aal_anchor" id="starting-the-client"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Starting the client</h1>



<p>Navigate to the <strong>client</strong> folder and issue:</p>



<p><code>npm install</code></p>



<p>Then</p>



<p><code>npm start</code></p>



<p>Once launched, a web browser will open to localhost:3000 and display the UI shown in Figure 2.</p>



<p>Enter any value into the amount and select your favorite base and desired currency.&nbsp; Press Convert to see the most current amount in your desired currency.</p>



<p>Let’s take a look at what is happening under the covers.&nbsp; First let’s look at the client code, specifically the <code>convert.js</code> file within the <strong>src/components </strong>folder.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-typescript">// GraphQL query to fetch currencyList and listExchangeRate
const GET_currencyList = gql`
  query Query {
    currencyList {
      symbol
      name
    }
    listExchangeRate {
      symbol
      rate
    }
  }
`;</code></pre>



<p>Our simple example has two queries <code>currencyList</code><strong>,</strong> which returns the complete list of symbols and names for the currency, and <code>listExchangeRate</code><strong>,</strong> which returns the current rate for each symbol.&nbsp; These data are used to populate the drop-downs in the UI.&nbsp; When using Apollo Connectors, the client does not need to make any changes.&nbsp; It is business as usual for your front-end folks.&nbsp; The real magic is in the back end.</p>



<h1 class="wp-block-heading"><a href="#taking-a-closer-look-at-the-apollo-connector" aria-hidden="true" class="aal_anchor" id="taking-a-closer-look-at-the-apollo-connector"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Taking a closer look at the Apollo Connector</h1>



<p>Open the <code>currency.graphql</code> file.&nbsp; This file contains the configuration for the REST Apollo Connector.&nbsp;&nbsp;</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">extend schema
  @link(
    url: &quot;https://specs.apollo.dev/federation/v2.10&quot;
    import: [&quot;@key&quot;]
  )
  @link(
    url: &quot;https://specs.apollo.dev/connect/v0.1&quot;
    import: [&quot;@source&quot;, &quot;@connect&quot;]
  )
  @source(
    name: &quot;v1&quot;
    http: {
      baseURL: &quot;https://api.currencyapi.com/v3/&quot;
      headers: [{ name: &quot;apikey&quot;, value: &quot;{$config.apikey}&quot; }]
    }
  )

type Query {
  &quot;A list of currencies&quot;
  currencyList: [Currency]
    @connect(
      source: &quot;v1&quot;
      http: { GET: &quot;/currencies&quot; }
      selection: &quot;&quot;&quot;
        data-&gt;entries {
          symbol: key
          name: value.name
        }
      &quot;&quot;&quot;
    )

  &quot;List exchange rates&quot;
  listExchangeRate: [ExchangeRate]
    @connect(
      source: &quot;v1&quot;
      http: { GET: &quot;/latest&quot; }
      selection: &quot;&quot;&quot;
        data-&gt;entries {
          symbol: key
          rate: value.value
        }
      &quot;&quot;&quot;
    )
}

type Currency {
   symbol: String
   name: String
}

type ExchangeRate {
   symbol: String
   rate: Float
}</code></pre>



<p>This is all that is needed for your Apollo Server to connect to a REST API, no extra resolver code!&nbsp; Looking at the GraphQL query, you’ll see an <code>@link</code> statement referencing Apollo Connector.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">@link(
  url: &quot;https://specs.apollo.dev/connect/v0.1&quot;
  import: [&quot;@source&quot;, &quot;@connect&quot;]
)</code></pre>



<p>Here, we are importing the <code>@source</code> and <code>@connect</code> directives.&nbsp; The <code>@connect</code> requires additional configuration parameters such as the details about the HTTP request, any headers, and a parameter called “selection” which filters the data from the REST API results.&nbsp; Here is the <code>currencyList</code> field in our example:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">  &quot;A list of currencies&quot;
  currencyList: [Currency]
    @connect(
      source: &quot;v1&quot;
      http: { GET: &quot;/currencies&quot; }
      selection: &quot;&quot;&quot;
        data-&gt;entries {
          symbol: key
          name: value.name
        }
      &quot;&quot;&quot;
    )</code></pre>



<p>In this query, the Apollo Connector will use the base url defined in the <code>@link</code> and append the string defined as part of the HTTP request type in this case is GET.&nbsp; Since our currencyAPI endpoint requires an authentication header, we add the <strong>headers</strong> field and add a key-value pair referencing the API Key and value we defined earlier in the <code>router-config.yaml </code>file.&nbsp; Next, we need to tell the connector what data to extract from the API results.&nbsp; We define this in the <strong>selection</strong> parameter.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-perl">data-&gt;entries {
  symbol: key
  name: value.name
}</code></pre>



<p>For reference, the data that returns from the CurrencyAPI is similar to the following:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-json">{
  &quot;data&quot;: {
    &quot;AED&quot;: {
      &quot;symbol&quot;: &quot;AED&quot;,
      &quot;name&quot;: &quot;United Arab Emirates Dirham&quot;,
      &quot;symbol_native&quot;: &quot;د.إ&quot;,
      &quot;decimal_digits&quot;: 2,
      &quot;rounding&quot;: 0,
      &quot;code&quot;: &quot;AED&quot;,
      &quot;name_plural&quot;: &quot;UAE dirhams&quot;,
      &quot;type&quot;: &quot;fiat&quot;,
      &quot;countries&quot;: [
        &quot;AE&quot;
      ]
    },
    ...
  }
}</code></pre>



<p>For our client we want to return just the symbol and name of each of the currencies.&nbsp; Since our return result has all our data under the “data” field, we start with data and iterate through each subdocument using the <strong>entities</strong> keyword.&nbsp; For each of these <strong>entities,</strong> we return the key, which in this example result is “AED” and add that value to a “symbol” field.&nbsp; We give the field “name” the value of the name field in the result. For a complete discussion and more examples of selection parameters, see the <a href="https://www.apollographql.com/docs/graphos/schema-design/connectors/selection">online documentation</a>.</p>



<h1 class="wp-block-heading"><a href="#summary" aria-hidden="true" class="aal_anchor" id="summary"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Summary</h1>



<p>Building resolvers for REST APIs can be a complex yet essential task for developers working with GraphQL. However, Apollo Connectors now provide a simpler, more efficient way to integrate REST APIs into your GraphQL schema, eliminating the need for custom resolver code. In this article, you learned how to setup and configure an Apollo Connector for REST APIs that query data from the CurencyAPI public API endpoint.&nbsp; Apollo Connectors is currently in preview, for more information, check out the <a href="https://www.apollographql.com/graphos/apollo-connectors">Apollo Connectors</a> website.</p>



<h1 class="wp-block-heading"><a href="#call-to-action" aria-hidden="true" class="aal_anchor" id="call-to-action"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Call to action</h1>



<p>Curious how Apollo Connectors can streamline your GraphQL workflows? Sign up for a <a href="https://www.apollographql.com/connectors-demo">demo</a> or join our upcoming webinar on December 12th, 2024: <a href="https://www.apollographql.com/events/api-orchestration-in-30-minutes-a-stripe-checkout-workflow-with-apollo-connectors">API Orchestration in 30 Minutes: A Stripe Checkout Workflow with Apollo Connectors</a>.&nbsp; After attending this webinar, you will have a solid understanding of orchestrating API calls with Apollo Connectors in the context of real-world use cases.&nbsp; If you are reading this after the event date, the webinar will be available on-demand.</p>


Effortless Data Fetching: Introducing Apollo Connectors for REST APIs


<p>Apollo Connectors make it easier than ever to create a GraphQL API leveraging non-GraphQL services. Developers can use a declarative syntax, right in their schema files, to connect GraphQL fields to HTTP APIs. GraphOS Router uses that information to talk <em>directly</em> to the API, no subgraph needed.</p>



<h2 class="wp-block-heading"><a href="#reducing-complexity" aria-hidden="true" class="aal_anchor" id="reducing-complexity"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Reducing complexity</h2>



<p>Before today, when developers wanted to add a REST service to their federated GraphQL API, they had to take several steps:</p>



<ol class="wp-block-list">
<li>Identify a programming language and a Federation-compatible GraphQL framework</li>



<li>Deploy a new subgraph service, including monitoring, auto-scaling, and load-balancing, which will sit in between the router and the REST API</li>



<li>For each change to the REST API:
<ol class="wp-block-list">
<li>Design the subgraph schema for the underlying REST data</li>



<li>Write bindings to the REST API in the chosen programming language</li>



<li>Write resolvers that leverage those bindings</li>



<li>Deploy the subgraph service</li>



<li>Compose and publish the schema to update the router</li>
</ol>
</li>
</ol>



<p>Apollo Connectors eliminate the need for the intermediate service, saving developer time and infrastructure cost. With connectors, each iteration is reduced to:</p>



<ol class="wp-block-list">
<li>Design the subgraph schema for the underlying REST data</li>



<li>Compose and publish the schema to update the router</li>
</ol>



<p>The router then speaks directly to the REST APIs:</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd9Ttaekoj3X97LvhKoxcsHefPNT2jOCAh5GViBlTzPwsiGwXwmCMFahiAhQ81UNfPP6h4y_f4rnW4V8Fyh-wRlyjvRMXvT6FcTY4m8CGpQk_V3L1hgX5YZQhLl8AhEa7EjYdZJ0hROdshuIyUgDSXVsio?key=X-2ujg-cWaXZiwKXT52_aQ" alt=""/></figure>



<h2 class="wp-block-heading"><a href="#delighting-developers" aria-hidden="true" class="aal_anchor" id="delighting-developers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Delighting developers</h2>



<p>Apollo Connectors are designed with a singular goal in mind: make it as easy as possible for developers to build high-quality GraphQL APIs. Every aspect was built from the ground up to achieve this goal, starting with the declarative syntax:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">type Query {
 post(id: ID!): Post
   @connect(
     source: &quot;rest_api_v1&quot;
     http: { GET: &quot;/posts/{$args.id}&quot; }
     selection: &quot;&quot;&quot;
       id
title
body
author: { id: userId }
     &quot;&quot;&quot;
   )
}</code></pre>



<p>Data sources are connected right in your schema, so there&#8217;s no need to hop back and forth between multiple files. The selection format, for transforming the data, is designed to feel like the GraphQL query language to reduce context switching. It&#8217;s also designed to provide as much feedback as possible early in the development lifecycle, especially when combined with our <a href="http://go.apollo.dev/connectors/guides#visual-studio-code">Visual Studio Code extension</a>. No more catching typos after deploy:</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfTnKYrGuW1QQgne9IzJQFlLYxcC_tYJD8KOGK4MV2o1jlSiV-tmWWYyR-Mr42H0bQoz0TyKM1nTW8Rd3xymb7s2JRS3JB881hhNPmuSLhho9IfACWABG7xI917Pk6cskl45msWuHK9AdjwR8_lanBEat0?key=X-2ujg-cWaXZiwKXT52_aQ" alt=""/><figcaption class="wp-element-caption">Apollo&#8217;s Visual Studio Code extension underlines errors in your Connectors definition</figcaption></figure>



<p>Our focus on developers extends through the testing phase, with powerful new debugging tools built into <a href="https://www.apollographql.com/docs/graphos/explorer/sandbox/">Apollo Sandbox</a>:</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcuYoRXVO2LnwxaISPX-Cn_aGE_-Hz5J9W_rmxODLNyECou0Q3MLijxEYKRiMxnvCiQnqLSRqTvTaMPByLdVx-A2xLCoZpHlW8YirW0gZA8m0fRnUmmziCfeJoSbwLuCOjfM93XRz6yhXKpl4U69ydOs1O1?key=X-2ujg-cWaXZiwKXT52_aQ" alt=""/></figure>



<p>And, of course, you get the production-ready features you&#8217;ve come to expect from GraphOS Router, like in-depth observability, built on the OpenTelemetry standard:</p>



<figure class="wp-block-image is-resized"><img decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfZi8mBk3kSsuD3CUdbPZpxzdtXdVfpdaZawe42ny1vaohq8hUwWffKVwOF-7bmBsZeaTfx0SMHa830H9A4xFZNiYzKNyut-_g5Op_0LdyyfVZ6k31axT-fWlrnjKU28F_M3p4EBvbQGe24KrFxpDJOItpu?key=X-2ujg-cWaXZiwKXT52_aQ" alt="" style="width:610px;height:auto"/><figcaption class="wp-element-caption">Apollo Studio&#8217;s insights page</figcaption></figure>



<h2 class="wp-block-heading"><a href="#get-connected" aria-hidden="true" class="aal_anchor" id="get-connected"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get connected</h2>



<p>Apollo is on a journey to make developing, operating, and consuming APIs as delightful as possible. GraphQL is a developer-friendly abstraction over all the moving pieces of modern applications. Apollo Connectors make the process of tying those pieces together into a cohesive, well-crafted schema, better than ever. You can <a href="https://go.apollo.dev/connectors">try out connectors today</a> with your existing Enterprise plan or by getting <a href="https://studio.apollographql.com/signup?referrer=blog">started with GraphOS</a> for free. Send us your feedback and ask questions in our <a href="https://community.apollographql.com/tag/connectors">forums</a> or <a href="https://discord.gg/graphos">Discord server</a>. We can&#8217;t wait to see what you create!</p>


Apollo Connectors: Blazing-Fast Integration with REST APIs

What’s new in Apollo GraphOS 


<p>Apollo Kotlin 4 is the new major version of Apollo Kotlin. It builds on top of Apollo Kotlin 3 and brings a number of tooling and API improvements:</p>



<ul class="wp-block-list">
<li>A brand new IDE plugin for all your refactoring needs.</li>



<li>Improvement to the error handling APIs, making it easier to handle errors in a single place.</li>



<li>WasmJs support.</li>



<li>A multiplatform GraphQL parser.</li>



<li>A preview of semantic nullability.</li>



<li>Network monitoring API, new WebSocket APIs and more …</li>
</ul>



<p>For a comprehensive list of all changes, please review the <a href="https://github.com/apollographql/apollo-kotlin/releases/tag/v4.0.0">full changelog</a>.</p>



<p>If you&#8217;re currently using Apollo Kotlin 3, refer to the <a href="https://www.apollographql.com/docs/kotlin/v4/migration/4.0/#moved-artifacts">migration guide</a> for step-by-step migration instructions.</p>



<p>Or read on for a brief summary of the key updates and a preview of what&#8217;s on the horizon.</p>



<h2 class="wp-block-heading"><a href="#android-studio-intellij-plugin" aria-hidden="true" class="aal_anchor" id="android-studio-intellij-plugin"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Android Studio/IntelliJ plugin</h2>



<p>If you’re using Android Studio or IntelliJ, <a href="https://www.apollographql.com/docs/kotlin/v4/testing/android-studio-plugin/">you can now download the Apollo IntelliJ plugin in the IntelliJ marketplace</a> and get even more help from your IDE.</p>



<p>Apollo IDE plugin core features include:</p>



<ul class="wp-block-list">
<li>On the fly code generation</li>



<li>GraphQL &lt;-> Kotlin navigation</li>



<li>Unused field inspection</li>



<li>High Field latency inspection</li>



<li>Normalized cache viewer</li>



<li>Schema download </li>



<li>Automatic migration</li>
</ul>



<p>That last point means you can now use the plugin to automate most of your v3 -&gt; v4 migration.</p>



<p><img loading="lazy" decoding="async" src="https://lh7-us.googleusercontent.com/docsz/AD_4nXdaWp_FZSNQWfiwe6FNOOsEcoK1pc4K1wAsu7BX6Am-8yP7Rdjs0ZPGbgppgMND00Yvs4iBQbOlY9IBVwwYhjUNrHUq8_vIeAGxaxKNvL7S_aG00mq18dCdD8PYBtBbQO5-_8XWu5e1wL2MtRvZykK-86SW?key=12X6ltZW9oZBbxKegGgpWw" width="668" height="463"></p>



<h2 class="wp-block-heading"><a href="#api-consolidation" aria-hidden="true" class="aal_anchor" id="api-consolidation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>API consolidation</h2>



<p>With the release of Apollo Kotlin 4, we&#8217;ve achieved a significant milestone where our core APIs—including code generation, parsers, and interceptors—are now stable. This stability means we don’t anticipate any major overhauls like the transition from version 2 to 3, though the landscape of Kotlin and GraphQL continues to evolve rapidly. Developments such as <a href="https://youtrack.jetbrains.com/issue/KT-68296">union types for errors</a> or <a href="https://github.com/graphql/nullability-wg/discussions/58">semantic nullability schemas</a> may necessitate breaking changes in the future.</p>



<p>Looking ahead, our goal is to roll out smaller, more frequent updates, including major versions. This approach will keep the core APIs consistent, enabling us to introduce new features and adapt more swiftly to changes in the environment. To facilitate this, we’ve updated the package name from <code>com.apollographql.apollo3</code> to <code>com.apollographql.apollo</code>.<br><br>With Apollo Kotlin 4, we are also introducing an evolution policy. This policy will steer the development of future versions and ensure that we provide clear deprecation notices, helping you to transition smoothly and confidently.</p>



<h2 class="wp-block-heading"><a href="#multiplatform-graphql-parser" aria-hidden="true" class="aal_anchor" id="multiplatform-graphql-parser"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Multiplatform GraphQL parser</h2>



<p>Previously, Apollo Kotlin relied on<a href="https://github.com/graphql/graphql-js" data-type="link" data-id="https://github.com/graphql/graphql-js"> <code>graphql-js</code></a> for parsing GraphQL documents. In version 2, we transitioned to using <a href="https://www.antlr.org/">Antlr</a> to generate parsers from <code>.g4</code> grammars.</p>



<p>With Apollo Kotlin 4, we’ve taken a significant leap forward by developing our <a href="https://github.com/apollographql/apollo-kotlin/pull/5047">own recursive descent</a> parser.</p>



<p>The new parser not only performs up to <a href="https://github.com/apollographql/apollo-kotlin/pull/5047#issue-1780385717">twice </a>as fast as the previous Antlr-based parser in certain scenarios, but it’s also entirely written in Kotlin, ensuring full multiplatform support. This means you can seamlessly integrate it into your Kotlin multiplatform projects just like any other KMP dependency.</p>



<p>Here’s how you can add the new parser to your project:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin">kotlin {
  sourceSets {
    getByName(&quot;commonMain&quot;) {
      dependencies {
        implementation(&quot;com.apollographql.apollo:apollo-ast&quot;)
      }
    }
  }
}</code></pre>



<p>And here’s how to utilize it at runtime:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin">  // Parse a document
  val document = &quot;query { hello }&quot;.toGQLDocument()

  // transform/inspect it
  // And serialize it again
  println(document.toUtf8())</code></pre>



<h2 class="wp-block-heading"><a href="#introducing-wasmjs-support" aria-hidden="true" class="aal_anchor" id="introducing-wasmjs-support"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Introducing WasmJs support</h2>



<p>Apollo Kotlin 4 now includes support for the WasmJs target, expanding your capabilities to use the generated models and <code>apollo-runtime</code> in a Wasm application. Experience this new feature firsthand by trying out the Confetti wasm demo at <a href="https://wasm.confetti-app.dev/">https://wasm.confetti-app.dev/</a> (<a href="https://github.com/joreilly/Confetti">GitHub</a>).</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="874" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-874x1024.png" alt="" class="wp-image-23864" srcset="https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-874x1024.png 874w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-256x300.png 256w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-768x900.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-1311x1536.png 1311w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-1748x2048.png 1748w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47-1200x1406.png 1200w, https://wp.apollographql.com/wp-content/uploads/2024/07/Screenshot-2024-07-31-at-17.27.47.png 1886w" sizes="auto, (max-width: 874px) 100vw, 874px" /></figure>



<h2 class="wp-block-heading"><a href="#enhancing-nullability-handling" aria-hidden="true" class="aal_anchor" id="enhancing-nullability-handling"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Enhancing nullability handling</h2>



<p>In GraphQL, <a href="https://graphql.org/learn/best-practices/#nullability">fields are traditionally nullable by default</a>. However, the standards set in 2015 don’t always align with the needs of 2024, especially as <a href="https://github.com/graphql/nullability-wg/">the GraphQL community seeks to enhance </a>type safety for languages like TypeScript, Swift, and Kotlin.</p>



<p>Apollo Kotlin 4 introduces two experimental directives, <code>@semanticNonNull</code> and <code>@catch</code>, designed to simplify interactions with nullable fields.</p>



<p>The <code>@semanticNonNull</code> directive is a server-side directive, indicating that a field is guaranteed to be non-null unless an error happens. This directive can be incorporated into your <code>.graphqls</code> schema extensions, enhancing the clarity and reliability of your data models:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin"># name is never null unless an error happens
extend type User @semanticNonNullField(name: &quot;name&quot;)</code></pre>



<p>On the code generation front, Apollo Kotlin recognizes <code>@semanticNonNullField</code> and accordingly generates non-null Kotlin properties, ensuring that your application code remains type-safe and concise.</p>



<p>Additionally, the <code>@catch</code> directive is a client-side directive for opting into specific error handling strategies during operations. By using <code>@catch</code> in your <code>.graphql</code> operations, you can manage how errors are handled directly within the data context—whether by mapping errors to <code>null</code>, re-throwing them, or using another method:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-kotlin">query GetUser {
  user {
    # map name to FieldResult&lt;String?&gt; instead of stopping parsing
    name @catch(to: RESULT)
  }
}</code></pre>



<p>For a deeper understanding of these enhancements and their implications on your projects, please refer to our detailed <a href="https://www.apollographql.com/docs/kotlin/v4/advanced/nullability#handle-errors-and-receive-partial-data-with-catch">nullability documentation page</a>.</p>



<h2 class="wp-block-heading"><a href="#looking-ahead" aria-hidden="true" class="aal_anchor" id="looking-ahead"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Looking ahead</h2>



<p>Beyond the updates already discussed, Apollo Kotlin 4 introduces several exciting features including support for<a href="https://github.com/graphql/graphql-spec/pull/825"> <code>@oneOf</code></a>, new WebSockets APIs, new low-level Apollo compiler plugin APIs, and new Gradle APIs. For a detailed list of all the enhancements, make sure to read the full changelog.</p>



<p>One significant area poised for further development is the normalized cache, which continues to present challenges. While Apollo Kotlin 3 introduced <a href="https://www.apollographql.com/docs/kotlin/caching/declarative-ids/">&nbsp;<code>@typePolicy</code> and <code>@fieldPolicy</code> for declarative ids</a>, certain scenarios still demand the use of complex programmatic APIs.</p>



<p>Additionally, issues such as garbage collection and invalidation remain unresolved. We aim to address these in version 5.</p>



<p>With the modularization of Apollo Kotlin development has shifted to <a href="https://github.com/apollographql/apollo-kotlin-normalized-cache-incubating/">a separate repository</a>, enabling more agile iteration and improvement.<br>For the latest updates and future plans, please refer to <a href="https://github.com/apollographql/apollo-kotlin/blob/main/ROADMAP.md">the ROADMAP</a> document on what is being worked on.</p>



<h2 class="wp-block-heading"><a href="#join-the-community" aria-hidden="true" class="aal_anchor" id="join-the-community"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Join the community</h2>



<p>Have a question or wish to discuss GraphQL, Kotlin, or the<a href="https://github.com/apollographql/apollo-kotlin/blob/main/ROADMAP.md"> ROADMAP</a>? We encourage you to connect with us and join the conversation:</p>



<ul class="wp-block-list">
<li><a href="https://github.com/apollographql/apollo-android/issues">Github</a></li>



<li><a href="http://community.apollographql.com/new-topic?category=Help&amp;tags=mobile,client">Community forums</a></li>



<li>Join the <a href="https://app.slack.com/client/T09229ZC6/C01A6KM1SBZ">Apollo KotlinLang slack channel</a> (click <a href="https://slack.kotl.in/">here</a> for an invite).</li>
</ul>



<p>We&#8217;re here to support you and look forward to your insights and contributions!</p>


Apollo Kotlin 4 is now available


<p>On, June 12, 2024, we hosted our <a href="https://www.apollographql.com/events/apollo-graphos-summer-update-operational-excellence-for-graphql-federation">GraphOS summer launch event</a>, where we announced new features designed to improve the performance and operational excellence of GraphQL platforms. These new capabilities improve how API platform teams implement and optimize GraphQL federation, providing faster baseline performance and greater control over API request execution in a supergraph.</p>



<h2 class="wp-block-heading"><a href="#graphql-federation-usage-on-the-rise" aria-hidden="true" class="aal_anchor" id="graphql-federation-usage-on-the-rise"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL Federation: Usage on the rise</h2>



<p>GraphQL adoption in the enterprise is at an inflection point, driven by the proliferation of federated GraphQL architectures – a pattern originally introduced by Apollo GraphQL in 2019 with the launch of Apollo Federation and <a href="https://www.apollographql.com/graphos">GraphOS</a>. In a <a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery">recent report</a>, Gartner® predicts that 30% of enterprises using GraphQL will utilize GraphQL federation by 2027, up from less than 5% in 2024. Apollo believes this trend suggests the number of enterprises using GraphQL federation as their API access layer will increase by 12x.</p>



<p>Apollo Federation is a specification for modularly and declaratively mapping existing application services into a unified GraphQL API access layer, known as a supergraph. This architecture empowers platform engineering teams to provide client applications with self-serve access to services through a single GraphQL endpoint, facilitating the rapid evolution of complex end-user experiences. By decoupling backend development from frontend complexity, teams can independently manage and contribute services to the supergraph via subgraphs, representing core business entities such as Product, User, or Cart.</p>



<p>In our summer launch, we focused on the Operational Excellence pillar of the <a href="https://saf.apollographql.com/">Supergraph Architecture Framework</a>. The <a href="https://www.apollographql.com/docs/graphos/enterprise/supergraph-architecture-framework/operational-excellence">Operational Excellence pillar</a> focuses on empowering subgraph and stewardship teams. A well-architected graph isn&#8217;t only technically excellent—it&#8217;s also operationally excellent. Processes and tools should be in place to ensure that the supergraph is easy to use, understand, and maintain. These principles help ensure that the graph is a successful tool for building new experiences quickly.</p>



<h2 class="wp-block-heading"><a href="#key-announcements" aria-hidden="true" class="aal_anchor" id="key-announcements"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Key Announcements</h2>



<h3 class="wp-block-heading"><a href="#query-batching-ga" aria-hidden="true" class="aal_anchor" id="query-batching-ga"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Query Batching: GA</h3>



<p>GraphOS now supports end-to-end (client-to-subgraph) <a href="https://www.apollographql.com/docs/router/executing-operations/query-batching">query batching</a>, which is essential for ensuring consistency in component-based architecture where individual micro-frontends (MFE) make requests separately to fetch data relevant to them. By handling several queries in one request, this feature has the additional performance benefit of reduced network traffic and server load.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-us.googleusercontent.com/docsz/AD_4nXcMs0LzYIGqdyyR5_ULkftZoSb34V-0mHkjOc6wSHysBXe3PSoZ0uABtVJXFzeKO4_HN820CVzHBq1uom6ZOktomLhPU7wju0j8BcbT7ph8h9WRJT8UVZTFP8gk7LD_ukgKayrPxU0YhaHKcf8Ihqt7aQrY?key=PFk4g9hPuyvLkr-tso1A2A" alt=""/></figure>



<h3 class="wp-block-heading"><a href="#enhanced-telemetry-and-insights-ga" aria-hidden="true" class="aal_anchor" id="enhanced-telemetry-and-insights-ga"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Enhanced Telemetry and Insights: GA</h3>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="Improve GraphQL observability with Telemetry in GraphOS Router" width="580" height="326" src="https://www.youtube.com/embed/bdHWjn9lVvM?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<p>The enhancements to <a href="https://www.apollographql.com/docs/router/configuration/telemetry/overview">custom telemetry</a> in GraphOS Router provide platform teams with deeper visibility into the performance of their supergraphs. New support for custom <a href="https://www.apollographql.com/docs/router/configuration/telemetry/instrumentation/events">events</a> gives you full customization over signalling when something of note happens in the Apollo Router&#8217;s request lifecycle. <img loading="lazy" decoding="async" src="https://lh7-us.googleusercontent.com/docsz/AD_4nXcH37HOKu_mbsFQs_VA9UWf-DCOBgYfvxCycR3HOeOM0i7u_zEIm8jgOySM8mVfUy7QhL48QdMNmlPu8t_E6AJRcV3ayaB2Ntl2AaaYUTkrv6ynGSyuFE3JmdVO2snCghn6_FqMja19MKeY53qk3L7YczXZ?key=PFk4g9hPuyvLkr-tso1A2A" width="1638" height="670"></p>



<p>New custom <a href="https://www.apollographql.com/docs/router/configuration/telemetry/instrumentation/instruments">instruments</a> collects custom data and reports measurements to a metric backend.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh7-us.googleusercontent.com/docsz/AD_4nXcYaXIRpEMeymT44OAbW73Y54rXd_cTX44WnjrUkPUdHJ8ZOk2bjnRuZHdjePwPR6PRDKGYQQU-cicr0cUMDWonOh7MYzhcpI_csuy02t4bE2oWRR9Ts4Jh2Iz8W6t33Po4vkRwkpg9tvi6iClO8b--J9Y?key=PFk4g9hPuyvLkr-tso1A2A" alt=""/></figure>



<p>Combined, enhanced telemetry allows client teams to investigate runtime errors and performance issues autonomously, reducing the debugging burden on core platform teams.&nbsp;</p>



<p>Additionally, GraphOS Studio now offers more <a href="https://www.apollographql.com/blog/new-graphql-observability-and-insights-in-graphos-studio">comprehensive checks and insights</a>, giving teams greater control over supergraph operation validation to mitigate production errors.</p>



<h3 class="wp-block-heading"><a href="#entity-caching-with-per-subgraph-ttl-public-preview" aria-hidden="true" class="aal_anchor" id="entity-caching-with-per-subgraph-ttl-public-preview"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Entity Caching with Per-Subgraph TTL: Public Preview</h3>



<p>Configuring response caching in a supergraph can be challenging due to the varied refresh rates of different fields. <a href="https://www.apollographql.com/docs/router/configuration/entity-caching">Subgraph entity caching</a> addresses this by allowing platform teams to cache entities centrally while setting granular TTLs for each subgraph. For example, a Product entity can have a long TTL for its Name field and a short TTL for its Inventory field, so long as they are resolved by different subgraphs.</p>



<h3 class="wp-block-heading"><a href="#demand-control-public-preview" aria-hidden="true" class="aal_anchor" id="demand-control-public-preview"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Demand Control: Public Preview</h3>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="Manage costly GraphQL operations with Demand Control in GraphOS Router" width="580" height="326" src="https://www.youtube.com/embed/ms8yCYFuVUo?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<p>Platform teams often need to protect their graphs against highly complex queries that can cause service disruption if left unchecked. Our new native cost calculation and limiting features make it easier for teams to observe the average cost of operations in their graph and implement cost controls centrally to avoid misuse of their GraphQL endpoints.</p>



<h2 class="wp-block-heading"><a href="#transforming-api-platform-operations" aria-hidden="true" class="aal_anchor" id="transforming-api-platform-operations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Transforming API Platform Operations</h2>



<p>These new features mark a significant step forward in how organizations can improve the operational excellence with which they manage federated GraphQL architectures. By providing advanced tools for caching, cost control, and query batching, Apollo GraphOS empowers platform teams to build, operate, and evolve supergraphs efficiently.</p>



<p>To learn more about these features and more, including schema visualization, context directives, and checks and insights, watch the <a href="https://www.apollographql.com/events/apollo-graphos-summer-update-operational-excellence-for-graphql-federation?utm_campaign=2024-06-05_apollo-graphos-summer-update-operational-excellence-for-graphql-federation&amp;utm_medium=blog">Summer Launch webinar</a> hosted by VP Product, Rob Brazier.&nbsp;</p>


GraphOS Summer 2024 Launch Recap


<p>We are experiencing a transformative period in application development, driven by the rise of AI across industries. This shift has made the API layer crucial for delivering innovative and personalized applications. At Apollo GraphQL, we aim to equip API platform teams with the tools they need to leverage GraphQL and GraphQL federation, helping them stay ahead in this AI-driven world.</p>



<p>Our customers and partners frequently highlight the need to maximize their APIs&#8217; value in a way that is easy to use, scalable, and drives bottom-line growth. They want to increase productivity, improve the developer experience, and enhance software quality, all while delivering fast and tailored digital experiences. Organizations like Expedia, The New York Times, and Wayfair choose our GraphOS platform to achieve these goals.</p>



<p>In light of these trends, <a href="http://www.apollographql.com/blog/apollo-graphql-announces-major-graphos-update-enhancing-observability-and-performance-for-enterprise-scale-graphql-federation">our latest GraphOS release</a> is a significant step forward. It improves observability and performance for enterprise-scale GraphQL federation and simplifies running a GraphQL platform with <a href="https://www.apollographql.com/docs/graphos/enterprise/supergraph-architecture-framework/operational-excellence/">operational excellence</a>. Gartner predicts that by 2026, over 30% of the increase in API demand will come from artificial intelligence and tools using large language models.<sup data-fn="3ded1729-df22-4efb-b57d-4a37b20c9290" class="fn"><a href="#3ded1729-df22-4efb-b57d-4a37b20c9290" id="3ded1729-df22-4efb-b57d-4a37b20c9290-link">1</a></sup> From building a chatbot, to AI-enabled personalization or transactions, or what’s to come in the future with autonomous agents, organizations require a resilient platform like GraphOS to connect their APIs and deliver a self-service graph that can power any number of applications.&nbsp;</p>



<p>We are excited to also welcome to our team <a href="https://www.linkedin.com/in/jenniferhewlette/" data-type="link" data-id="https://www.linkedin.com/in/jenniferhewlette/">Jennifer Hewlette</a> as Chief Marketing Officer. Jennifer brings over twenty years of experience in building enterprise marketing strategies from pre-revenue to public high-tech companies such as DataRobot and Cisco. At DataRobot, known for its generative and predictive AI platform, she led marketing, go-to-market enablement, and education, focusing on delivering exceptional value to customers and partners. Joining us at a time of our rapid global growth and extensive cross-industry market adoption, her expertise in category expansion and deep understanding of AI’s business impact will be instrumental in advancing our mission to bring the benefits of our supergraph technology to help developers help the world.&nbsp;</p>



<p>In Jennifer’s words:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p>“I have spent the majority of my career forging the new – new markets, new technologies, and new ecosystems. Apollo GraphQL is already a leader beloved by developers with more than 25M downloads each month, and trusted by hundreds of enterprise customers like Netflix, Indeed, Intuit, and Wayfair. The technology can help any brand that strives to deliver personalized, performant digital customer and AI experiences. I look forward to working with our customers, prospects, and ecosystem partners to accelerate business value and create new experiences.”</p>
</blockquote>



<p>We have welcomed seasoned veterans to our <a href="https://www.apollographql.com/leadership">leadership team</a> over the last year, with a rich pedigree in building world-class developer and enterprise companies from Atlassian, Twilio, Stripe, and Grammarly. These leaders have a remarkable track record of crafting customer-focused strategies that drive growth and innovation. Their expertise will be crucial as we help our users maximize the value of their API strategies and expand our market presence.</p>



<p>We&#8217;re excited to share these developments with our community and deepen our engagement with our users, customers, and partners. I’m delighted to invite you to join us in New York City this fall for <a href="http://www.graphqlsummit.com">GraphQL Summit 2024</a>. At this event, we’ll unveil our latest innovations and explore the future of GraphQL. It’s a unique opportunity to connect, learn, and collaborate as we push the boundaries of what&#8217;s possible in application development.</p>



<p>Join us in welcoming Jennifer Hewlette as our new Chief Marketing Officer as we embark on this exciting new chapter!</p>


<ol class="wp-block-footnotes"><li id="3ded1729-df22-4efb-b57d-4a37b20c9290"><a href="https://www.gartner.com/en/newsroom/press-releases/2024-03-20-gartner-predicts-more-than-30-percent-of-the-increase-in-demand-for-apis-will-come-from-ai-and-tools-using-llms-by-2026">https://www.gartner.com/en/newsroom/press-releases/2024-03-20-gartner-predicts-more-than-30-percent-of-the-increase-in-demand-for-apis-will-come-from-ai-and-tools-using-llms-by-2026</a> <a href="#3ded1729-df22-4efb-b57d-4a37b20c9290-link" aria-label="Jump to footnote reference 1">↩︎</a></li></ol>

Embracing The Future And Welcoming Our New CMO


<p><em>Caching, Native Cost Calculation and Limiting, and Telemetry Capabilities Revolutionize API Management and Streamline Building Cross-Platform Digital Application Experiences</em></p>



<p>Today at PlatformCon, <a href="https://apollographql.com">Apollo GraphQL</a>, the creator of GraphQL federation, announced new features in <a href="https://www.apollographql.com/graphos/">Apollo GraphOS</a> are now generally available to better leverage GraphQL’s developer productivity and performance benefits at any scale. This release provides API platform teams with visibility, usability, and performance benefits for GraphQL federation, enabling the engineering teams they serve to maximize the value of their APIs across their business.</p>



<p>As the leading GraphQL federation platform, GraphOS provides an abstraction layer for API complexity, enabling product engineering teams to rapidly build and iterate features based on customer demand. <a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery">Gartner® predicts that </a>30% of enterprises using GraphQL will utilize GraphQL federation by 2027, up from less than 5% in 2024.<sup>1 </sup>Apollo believes this trend suggests the number of enterprises using GraphQL federation as their API access layer will increase by 12x. GraphOS provides everything enterprise teams need to deliver GraphQL federation at any scale.&nbsp;</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p>“GraphQL federation removes the friction between the frontend and backend that we see in distributed architectures,” said Matt DeBergalis, Chief Technology Officer and co-founder at Apollo GraphQL. “This latest GraphOS release enables API platform teams to operationalize GraphQL federation’s benefits faster, so they can focus less on building custom tooling and more on their customers’ needs.”</p>
</blockquote>



<p>This latest GraphOS release includes significant improvements around observability, usability, and performance, enabling API platform teams to operate GraphQL federation more easily than ever before.&nbsp; “At enterprise-scale, every millisecond of latency in your consumer’s digital experiences impacts the bottom line,” said Rob Brazier, VP of Product at Apollo GraphQL. “With this release of Apollo GraphOS, we’ve made it even easier for API platform teams to observe and optimize the performance of federated graphs.”&nbsp;</p>



<p><strong>Apollo’s latest release provides operational excellence for GraphQL federation</strong></p>



<p>GraphQL federation is becoming a de facto architecture for platform engineering teams to simplify API governance across distributed architectures. Client teams can fetch all the data they need from a single endpoint, and this paradigm enables API platform teams to enforce better governance, provide better visibility into service usage, as well as use standardized tools for performance. GraphOS provides a complete solution for delivering GraphQL federation at any scale:</p>



<div class="wp-block-group is-vertical is-layout-flex wp-container-core-group-is-layout-2 wp-block-group-is-layout-flex">
<ul class="wp-block-list">
<li><strong>Better application performance</strong> – Apollo introduces an improved and simplified form of API caching built for GraphQL federation. GraphOS’s caching layer spans any number of APIs and now, in public preview, supports entity caching. Entities are object types that are composed from multiple GraphQL APIs and are the business objects or “nouns of every business.” API platform teams can store entities such as their inventory, products, or user records in a Redis data store. API platform teams can set how long these entities are cached in the data store, enabling API platform teams to significantly improve performance across an entire fleet of applications. &#8220;We&#8217;ve rolled out entity caching in production and are observing a decrease in median response time,&#8221; said Nimit Barochia, Senior Principal Software Engineer at Dow Jones. &#8220;The major improvement is how much less traffic we send to our subgraphs. Like a 8-10x decrease in some cases.&#8221;</li>
</ul>



<ul class="wp-block-list">
<li><strong>Cost control </strong>– API platform teams need a means to ensure that costly GraphQL operations don’t slow performance or create a denial of service. Platform teams need a means to limit cost of GraphQL operations processed by the GraphOS Router. Apollo is adding in public preview native cost calculation and limiting to GraphOS to make it easy for platform teams to centrally implement this, rather than relying on underlying services.</li>



<li><strong>Stronger support and improved performance</strong> – Micro-frontends provide a frontend architecture that refines performance and composability across mobile and web applications. To improve performance, micro-frontend UIs typically batch multiple client operations, issued close together, into a single API request. GraphOS is adding better support for these use cases, enabling GraphOS to handle batched requests from clients to a supergraph. It also further augments performance by ensuring that batches are kept intact when processed and passed on to the required subgraphs.</li>



<li><strong>Enhanced telemetry</strong> – API platform teams need both standardized and custom metrics to better optimize federated graphs for performance and business objectives. GraphOS now provides unparalleled visibility to debug and optimize federated graphs, enabling these teams to import these metrics into their Application Performance Monitoring tool of choice for better decision-making.&nbsp;</li>



<li><strong>Significant improvements to the GraphOS management plane</strong> – In Apollo Studio, schema checks and insights enable API teams to build, test, and ship changes to their federated graph with confidence. This release features significant UX improvements and better insights, enabling API teams to ship changes faster without introducing breaking changes to downstream clients.</li>
</ul>
</div>



<p><strong>Apollo customers to focus on innovation instead of API aggregation or orchestration</strong></p>



<p>AI is driving rapid innovation across industries, making the API layer critical for delivering competitive, personalized applications. Apollo aims to help API platform teams leverage GraphQL federation’s benefits across engineering organizations, empowering their teams to lead their organizations into the AI era.&nbsp;</p>



<p><strong>Learn more with Apollo&nbsp;</strong></p>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/events/apollo-graphos-summer-update-operational-excellence-for-graphql-federation?utm_campaign=2024-06-12_Webinar_Apollo-GraphOS-Summer-Update-Operational-Excellence&amp;utm_medium=email&amp;utm_source=sales">Attend a webinar</a> on June 12 to learn more about what’s new in GraphOS and see new features demoed.&nbsp;</li>



<li>Join Apollo <a href="https://lu.ma/platformcon-watch-party-apollo">live on June 13 </a>in NYC as it celebrates the largest conference for platform engineering, PlatformCon, and hear from customers COX Automotive, The New York Times, and Wayfair on how they’re finding success with Apollo’s federated GraphQL technology.</li>



<li>And the largest gathering of GraphQL enthusiasts and API platform teams is coming. Join Apollo at <a href="https://summit.graphql.com/">GraphQL Summit</a>, October 8-10, where engineering teams can learn from industry leaders spearheading successful GraphQL deployments at scale.</li>
</ul>



<p><sup>1</sup>Gartner, When to Use GraphQL to Accelerate API Delivery, By Shameen Pillai, et al, March 7, 2024. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved.</p>



<h1 class="wp-block-heading"><a href="#about-apollo-graphql" aria-hidden="true" class="aal_anchor" id="about-apollo-graphql"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>About Apollo GraphQL</h1>



<p><a href="https://apollographql.com">Apollo GraphQL </a>helps developers help the world by providing a better API platform across teams. Apollo’s open-source software is downloaded 25M times per month and its commercial GraphQL technologies power the most innovative brands today. Teams at Netflix, Snap, and the New York Times ship personalized, omnichannel experiences faster with a supergraph – a self-service GraphQL platform that spans any number of backend services. Serving over 5T requests in 2023, the Apollo GraphOS<sup>TM</sup> platform simplifies API development with workflows and infrastructure to build, test, and ship supergraphs at any scale. Based in San Francisco, Apollo is backed by Insight Partners, Andreessen Horowitz, Matrix Partners, and Trinity Ventures. Learn more at: <a href="https://www.apollographql.com">https://www.apollographql.com</a>.</p>


Apollo GraphQL Announces Major GraphOS Update, Enhancing Observability and Performance for Enterprise-Scale GraphQL Federation


<p>Apollo Client 3.10 has just been released, and we want to provide you with an overview of what&#8217;s new:</p>



<ul class="wp-block-list">
<li>Introducing new experimental schema-based testing utilities</li>



<li>New API: <code>client.watchFragment</code></li>



<li><code>createQueryPreloader</code> reaches &#8220;stable&#8221; status</li>
</ul>



<p>Let&#8217;s take a look:</p>



<h2 class="wp-block-heading"><a href="#introducing-new-experimental-schema-based-testing-utilities" aria-hidden="true" class="aal_anchor" id="introducing-new-experimental-schema-based-testing-utilities"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Introducing new experimental schema-based testing utilities</h2>



<p>In Apollo Client 3.10, we are introducing new schema-based testing utilities under the <code>@apollo/client/testing/experimental</code> import.</p>



<p>This adds two new tools:</p>



<p><strong><code>createTestSchema</code></strong> allows you to enhance a <code>GraphQLSchema</code> class with mock scalars and mock resolvers. </p>



<p>You can modify the resolvers inside your tests to simulate changing results.</p>



<p>This approach is an alternative to the current testing approach with <code>MockProvider</code>, allowing you to write tests similar to how you would implement your backend &#8211; applying skills you already have and can use in other situations.</p>



<p>You can then use this schema with <a href="https://mswjs.io/" data-type="link" data-id="https://mswjs.io/">Mock Service Worker</a> to simulate a GraphQL server, or you can use our new <strong><code>createSchemaFetch</code></strong> function to create a <code>fetch</code> function to be used inside of your tests.</p>



<p>Both of these approaches allow you to use your real link chain instead of a mocked one.</p>



<p>You can read more on this testing approach in <a href="https://github.com/apollographql/apollo-client/issues/11705" data-type="link" data-id="https://github.com/apollographql/apollo-client/issues/11705">the schema-driven testing RFC</a> and <a href="https://www.apollographql.com/docs/react/development-testing/schema-driven-testing" data-type="link" data-id="https://www.apollographql.com/docs/react/development-testing/schema-driven-testing">the documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#new-api-client-watchfragment" aria-hidden="true" class="aal_anchor" id="new-api-client-watchfragment"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>New API: <code>client.watchFragment</code></h2>



<p>We also add a new function to the <code>ApolloClient</code> class: <code>watchFragment</code>.</p>



<p>This function enables the functionality of the <code>useFragment</code> hook to be used in Vanilla JavaScript or other frameworks. </p>



<p>A PR to add a <code>watchFragment</code> functionality to <code>apollo-angular</code> has already been opened, and more will follow soon!</p>



<h2 class="wp-block-heading"><a href="#createquerypreloader-reaches-stable-status" aria-hidden="true" class="aal_anchor" id="createquerypreloader-reaches-stable-status"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><code>createQueryPreloader</code> reaches &#8220;stable&#8221; status</h2>



<p>In Apollo Client 3.9, we introduced the <code>createQueryPreloader</code> API as &#8220;alpha&#8221;, and since we&#8217;ve heard your positive feedback, with 3.10, we&#8217;re releasing it as &#8220;stable.&#8221;</p>



<p><code>createQueryPreloader</code> is used to start a query outside of React (e.g. in a Router action) and then later attach to the generated <code>queryRef</code> with the <code>useReadQuery</code> hook.</p>



<p>You can read more about it in the <a href="https://www.apollographql.com/docs/react/data/suspense/#initiating-queries-outside-react" data-type="link" data-id="https://www.apollographql.com/docs/react/data/suspense/#initiating-queries-outside-react">documentation</a>.</p>


What’s new in Apollo Client 3.10


<p>In the realm of software development, evolution is not just desirable; it&#8217;s inevitable. Technologies advance, methodologies shift, and systems need to adapt to meet changing demands. In this ever-evolving landscape, Apollo Federation 2.7 introduces a groundbreaking feature: progressive <code>@override</code> ✨</p>



<p>Rolling out any change to a production subgraph, including field migration, risks degrading the performance of your graph. Progressive <code>@override</code> enables you to migrate any part of your graph to a new service and customize how traffic is gradually rolled over to the new service.</p>



<h2 class="wp-block-heading" id="Understanding-@override:-A-Primer"><a href="#understanding-override-a-primer" aria-hidden="true" class="aal_anchor" id="understanding-override-a-primer"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Understanding <code>@override</code>: A Primer</h2>



<p>Before delving into the nuances of progressive <code>@override</code>, let&#8217;s take a moment to revisit the concept of <code>@override</code>. <code>@override</code> provide a mechanism for migrating fields from one subgraph to another. By applying an <code>@override</code> directive to a specific field, traffic for that field is rerouted to the designated service, facilitating the breakdown of monolithic architectures or the migration of fields between subgraphs.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql"># Inventory subgraph
type Product @key(fields: &quot;id&quot;) {
  id: ID!
  inStock: Boolean! @override(from: &quot;Products&quot;)
}</code></pre>



<p>In the example above, we’re migrating the <code>Product.inStock</code> field from the <code>Products</code> subgraph to the <code>Inventory</code> subgraph. Rerouting all traffic from one subgraph to another all at once could overload the overriding subgraph.</p>



<h2 class="wp-block-heading" id="Override-only-a-portion-of-traffic"><a href="#override-only-a-portion-of-traffic" aria-hidden="true" class="aal_anchor" id="override-only-a-portion-of-traffic"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Override only a portion of traffic</h2>



<p>Anything that ships to production, ideally, has a gradual rollout with a certain percentage of traffic. This gives us the ability to roll back any bad deployments with a smaller impact in case everything is just broken (we’ve all been there 😅).</p>



<p>Progressive <code>@override</code> makes this simple for our Apollo Router to handle. Simply label your <code>@override</code> directive with the supported <code>percent(x)</code> syntax.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql"># Inventory subgraph
type Product @key(fields: &quot;id&quot;) {
  id: ID!
  inStock: Boolean! @override(from: &quot;Products&quot;, label: &quot;percent(1)&quot;)
}</code></pre>



<p>Now our router will begin routing approximately 1% of all traffic to our new Inventory subgraph for the <code>Product.inStock</code> field. When we want to ramp that up, we can simply update our schema and once we reach 100%, we can remove the <code>inStock</code> field from the original <code>Product</code> subgraph 🎉</p>



<h2 class="wp-block-heading" id="Customize-progressive-@override-with-a-feature-flag-service"><a href="#customize-progressive-override-with-a-feature-flag-service" aria-hidden="true" class="aal_anchor" id="customize-progressive-override-with-a-feature-flag-service"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Customize progressive <code>@override</code> with a feature flag service</h2>



<p>It’s great that we can define a given percentage of traffic, but maybe we want to enable some items to bypass this percentage. You may want your beta application to always route to the new faster service 🏃</p>



<p>The router provides an interface for coprocessors and rhai scripts to resolve arbitrary labels. This means you can provide anything as the label and have the router interact with your external coprocessor to resolve the label. For an example implementation of a coprocessor that resolves labels using LaunchDarkly, see <a href="https://github.com/apollographql/router/tree/main/examples/coprocessor-override-launchdarkly/README.md">the example</a> in the router repo.</p>



<h2 class="wp-block-heading" id="Championing-the-Monolith-Breakup"><a href="#championing-the-monolith-breakup" aria-hidden="true" class="aal_anchor" id="championing-the-monolith-breakup"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Championing the Monolith Breakup</h2>



<p>A common use case we see with progressive <code>@override</code> is breaking down a GraphQL monolith. Everyone starts their GraphQL adoption journey with a monolith and although that can take you far, there are challenges as the usage of the graph increases. Eventually there is a desire to break a service off of the monolith, whether it’s to address a performance issue or maybe to utilize a new 3rd party service.</p>



<p>The easiest way to evaluate breaking up the monolith is to start with a known view that has some meaningful value in the overall application. You’ll want to keep the shape of the operation the same for the client so that you can just use a new URL for that single view&#8217;s GraphQL query. Let’s take this screen as an example:</p>


<div class="wp-block-image">
<figure class="aligncenter size-full"><img loading="lazy" decoding="async" width="444" height="673" src="https://wp.apollographql.com/wp-content/uploads/2024/04/Screenshot-2024-04-08-at-10.08.19-AM-1.png" alt="" class="wp-image-23637" srcset="https://wp.apollographql.com/wp-content/uploads/2024/04/Screenshot-2024-04-08-at-10.08.19-AM-1.png 444w, https://wp.apollographql.com/wp-content/uploads/2024/04/Screenshot-2024-04-08-at-10.08.19-AM-1-198x300.png 198w" sizes="auto, (max-width: 444px) 100vw, 444px" /></figure></div>


<pre class="wp-block-prismatic-blocks"><code class="language-graphql">query ProductDetails {
  product(id: &quot;space-boots&quot;) {
      sku
      name
      details
      rating
      price # The field we want to migrate
    }
}</code></pre>



<p>We want to migrate the <code>Product.price</code> field from our existing monolith to a new microservice. Ideally, this would require no changes to our client or monolith codebase. This is possible with progressive override and the architecture federation provides. Most commonly, teams will begin sending the traffic of the single client view to the hosted Apollo Router instance.</p>



<p>The Apollo Router can handle bridging traffic between your monolith and the new GraphQL service. Some teams will even opt to switch all of a single clients traffic to the router as a step of their progressive rollout (ie. switching the URL in <code>@apollo/client</code> to use the newly hosted router). Even though the router acts as a proxy for the rest of the clients traffic, it paves a golden path for adding new services that further break down the monolith.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="652" height="760" src="https://wp.apollographql.com/wp-content/uploads/2024/04/Group-1-1-1.png" alt="" class="wp-image-23626" srcset="https://wp.apollographql.com/wp-content/uploads/2024/04/Group-1-1-1.png 652w, https://wp.apollographql.com/wp-content/uploads/2024/04/Group-1-1-1-257x300.png 257w" sizes="auto, (max-width: 652px) 100vw, 652px" /></figure>



<p>For our example, we need to create a new subgraph that resolves the <code>Product.price</code> field. This will require us defining <code>Product</code> as an <a href="https://www.apollographql.com/docs/federation/entities">entity</a> using the <code>@key</code> directive and adding the <code>@override</code> directive to <code>Product.price</code>. This requires no changes to our existing monolith or it’s schema:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-"># Existing Monolith
type Product { 
	sku: ID!
	name: String
	details: String
	rating: Float
	price: Float
}
type Query {
	products: [Product]
	product(id: ID!): Product
}</code></pre>



<p><em>There are a lot of </em><a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs"><em>supported servers</em></a><em> you can use to build your GraphQL subgraph in your language of choice like Java, C#, Python and more.</em></p>



<p>Once our router re-configures with the composed schema, it will have the metadata of the <code>label</code> we added (<code>percent(25)</code>). The Apollo Router will then use this information to change the generated query plan based on the percentage label 🎉</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="980" height="650" src="https://wp.apollographql.com/wp-content/uploads/2024/04/Apr-08-2024-14-36-00-1.gif" alt="" class="wp-image-23628"/></figure>



<p>Now the <code>Product.price</code> field of our graph can resolve from a new microservice in our infrastructure and we can progressively rollout this change with simple updates to the schema. Once we’ve moved to 100%, we can eventually <em><strong>delete</strong></em> that code from our monolith 🔥</p>



<h2 class="wp-block-heading" id="Wrapping-up"><a href="#wrapping-up" aria-hidden="true" class="aal_anchor" id="wrapping-up"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Wrapping up</h2>



<p>Progressive override brings a powerful new tool for better flexibility and control in service migration. Embracing incremental adoption in our migrations helps developers navigate the complexities of the organization&#8217;s constantly evolving stack. This also enables platform engineering efforts to tackle self-service migrations for APIs to production 🤯. What would you migrate if you could?</p>



<p>Progressive <code>@override</code> is an <a href="https://www.apollographql.com/docs/router/enterprise-features">Enterprise feature</a> of the Apollo Router and requires an organization with a <a href="https://www.apollographql.com/pricing/?referrer=docs-content">GraphOS Enterprise plan</a>. If your organization doesn&#8217;t have an Enterprise plan, you can test it out by signing up for a free <a href="https://www.apollographql.com/docs/graphos/org/plans/#enterprise-trials">Enterprise trial</a>.</p>



<p></p>


Safer migrations of fields using progressive rollouts


<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="573" src="https://wp.apollographql.com/wp-content/uploads/2024/04/API-Days-NY-Apollo-GraphQL-Speakers-1024x573.png" alt="" class="wp-image-23618" srcset="https://wp.apollographql.com/wp-content/uploads/2024/04/API-Days-NY-Apollo-GraphQL-Speakers-1024x573.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/04/API-Days-NY-Apollo-GraphQL-Speakers-300x168.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/04/API-Days-NY-Apollo-GraphQL-Speakers-768x430.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/04/API-Days-NY-Apollo-GraphQL-Speakers.png 1186w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>API Days NY is a must-attend for those looking to network with API leaders and learn how top enterprises are leveraging federated GraphQL in their API platforms. As you can see from the agenda highlights below, it will be an exciting two day event.&nbsp;</p>



<ul class="wp-block-list">
<li>Our founder and CTO, Matt DeBergalis, will share his keynote &#8220;The Year Ahead for GraphQL Federation: Uniting APIs for the AI Era”</li>



<li>API leaders from Netflix, Wayfair and Apollo will present sessions on optimizing performance, creating effective api schemas and building an internal community for effective API governance</li>



<li>Apollo is offering a free workshop to guide you through building your first GraphQL query and beyond</li>



<li><a href="https://bit.ly/43IhuX4">Register to join us for a meetup &amp; happy hour</a> to meet with peer API leaders and GraphQL experts</li>
</ul>



<p>Swing by the Apollo booth to connect, and read on for more details.</p>



<h3 class="wp-block-heading"><a href="#keynote-the-year-ahead-for-graphql-federation-combining-apis-for-the-ai-era" aria-hidden="true" class="aal_anchor" id="keynote-the-year-ahead-for-graphql-federation-combining-apis-for-the-ai-era"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Keynote: The Year Ahead for GraphQL Federation: Combining APIs for the AI Era</strong></h3>



<p><em>Matt DeBergalis, Founder and CTO, Apollo GraphQL</em></p>



<p>Forget what you’ve heard about GraphQL – it’s not a REST alternative, graph database, or just for front-end developers. GraphQL is about combining the APIs you already have.</p>



<p>In this talk, you’ll learn how a federated GraphQL architecture brings a platform approach to API composition, where it fits into the API stack, and what is coming next to help teams build tomorrow’s AI products and experiences on today’s APIs.</p>



<h3 class="wp-block-heading"><a href="#session-the-graphql-overhead-myth-or-reality" aria-hidden="true" class="aal_anchor" id="session-the-graphql-overhead-myth-or-reality"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Session: The GraphQL Overhead: Myth or Reality?</strong></h3>



<p><em>Marc-André Grioux, Senior Software Engineer &amp; Author, Netflix</em></p>



<p>GraphQL is a powerful tool to enable declarative data fetching on the client and dynamic data representation on the server. This power must have an overhead. In this talk, investigate what this overhead is made of, how impactful it can be to scaling an API platform and services, and how to mitigate it as much as possible while retaining the benefits of GraphQL.</p>



<h3 class="wp-block-heading"><a href="#session-the-secrets-to-graph-success-from-inception-to-general-availability" aria-hidden="true" class="aal_anchor" id="session-the-secrets-to-graph-success-from-inception-to-general-availability"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Session: The Secrets to Graph Success, from Inception to General Availability</strong></h3>



<p><em>Leah Hurwich-Adler, Senior Product Leader</em></p>



<p>Building an API platform for a Fortune 100 retailer, capable of handling over 600 million requests per day, requires a highly distributed ecosystem and Federated GraphQL. Drawing from firsthand experience, Leah will share insights on building an internal API community, setting up governance models, and igniting leaders&#8217; enthusiasm for your platform vision. Join this talk to uncover the keys to launching a successful GraphQL platform, through lessons that merge technology with strategic and leadership insights.</p>



<h3 class="wp-block-heading"><a href="#session-benefits-of-idiomatic-code-first-graphql-development" aria-hidden="true" class="aal_anchor" id="session-benefits-of-idiomatic-code-first-graphql-development"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Session: Benefits of Idiomatic Code First GraphQL Development</strong></h3>



<p><em>Derek Kuc, Principal Engineer, Apollo GraphQL</em></p>



<p>When building a GraphQL server, two main approaches exist: starting with an SDL and matching resolver logic, or generating the schema directly from code. In this talk, explore the benefits of idiomatic code-first GraphQL development, focusing on GraphQL Kotlin examples. Discover how this approach enhances developer experience and API consistency.</p>



<h3 class="wp-block-heading"><a href="#workshop-build-an-api-composition-layer-with-apollo-graphql" aria-hidden="true" class="aal_anchor" id="workshop-build-an-api-composition-layer-with-apollo-graphql"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Workshop: Build an API Composition Layer with Apollo GraphQL</strong></h3>



<p><em>Michael Berger, Solutions Engineer, Apollo GraphQL</em></p>



<p>Use GraphQL to accelerate developer velocity by creating a composition layer for your microservices. Orchestrate data by creating a query that spans your REST APIs and delivers exactly the data your application requires. Learn how to build your first GraphQL query and why GraphQL is valuable to your microservice architecture.</p>



<h3 class="wp-block-heading"><a href="#nyc-meetup-and-happy-hour" aria-hidden="true" class="aal_anchor" id="nyc-meetup-and-happy-hour"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>NYC Meetup and Happy Hour</strong></h3>



<p><a href="https://bit.ly/43IhuX4">Register to join the Apollo team, Graph Champions, and apidays attendees</a> on April 30 at 6 PM following the conference for bites and beverages at nearby restaurant The Reading Room (16 E 46th St, New York, NY 10017 &#8211; located in the Gotham Hotel)</p>



<h3 class="wp-block-heading"><a href="#still-deciding-get-your-free-pass-now-before-they-run-out" aria-hidden="true" class="aal_anchor" id="still-deciding-get-your-free-pass-now-before-they-run-out"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Still deciding? Get your free pass now before they run out!&nbsp;&nbsp;</strong></h3>



<p>The full conference ticket includes access to the Keynotes, Track Sessions, Workshops and Networking Breakfasts and Lunches on April 30 &amp; May 1. Email <a href="mailto:champions@apollographql.com">champions@apollographql.com</a> to learn more and request a pass.</p>


Join Us at API Days in New York City, April 30 & May 1, 2024


<h2 class="wp-block-heading"><a href="#industry-leaders-to-showcase-tangible-business-impact-of-graphql-federation" aria-hidden="true" class="aal_anchor" id="industry-leaders-to-showcase-tangible-business-impact-of-graphql-federation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><em>Industry Leaders to Showcase Tangible Business Impact of GraphQL Federation</em></h2>



<p>In the wake of a recent report by Gartner<sup>®</sup>, <a href="https://apollographql.com">Apollo GraphQL</a>, the creator of GraphQL federation, is announcing the 7th annual GraphQL Summit, scheduled for October 8–10, 2024, in New York City. This premier three-day event gathers the largest assembly of GraphQL enthusiasts and API platform teams. Engineering teams can learn from industry leaders spearheading successful GraphQL deployments at scale and hear from Apollo GraphQL on its product roadmap and vision for the future of GraphQL and GraphQL federation.</p>



<p>According to the Gartner report, GraphQL&#8217;s adoption is on the rise, since “By 2027, more than 60% of enterprises will use GraphQL in production, up from less than 30% in 2024.” The report also predicts that “By 2027, 30% of enterprises using GraphQL will utilize GraphQL federation, up from less than 5% in 2024.”1<sup data-fn="5626a7a6-afc4-465e-84b4-2219decdae0e" class="fn"><a href="#5626a7a6-afc4-465e-84b4-2219decdae0e" id="5626a7a6-afc4-465e-84b4-2219decdae0e-link">1</a></sup> As GraphQL federation marks its<a href="https://www.apollographql.com/blog/celebrating-five-years-of-apollo-federation"> 5th anniversary,</a> Apollo GraphQL remains at the forefront of this transformative technology.</p>



<p>Previous GraphQL Summits have featured internet giants like Netflix, Intuit, and Wayfair, sharing invaluable insights into deploying GraphQL at scale to support distributed architectures. Rather than a sprawl of backends-for-frontends or experience APIs, these teams implemented GraphQL federation, an architecture that combines APIs and enables any number of client teams to query them from a single endpoint. Engineering leaders and API platform teams can learn how to use this architecture to drive developer velocity, enhance the customer experience across any number of applications, or handle the technical side of mergers and acquisitions, where IT is saddled with many disparate siloed systems that were never designed to talk to each other.</p>



<p>This year’s GraphQL Summit aims to support this burgeoning adoption with sessions led by industry luminaries across various sectors, including retail, automotive, and banking.&nbsp; Featured speakers include Stephanie Saunders, Engineering Manager at Coinbase; Mike Cohen, Technical Fellow at Indeed; and Marc-Andre Giroux, Senior Software Developer at Netflix, as well as the co-founders of Apollo GraphQL, Geoff Schmidt and Matt DeBergalis, who will share their insights and expertise on the future of GraphQL and GraphQL federation. Attendees can expect tracks and workshops covering best practices on security, governance, and API platform engineering; real-world use cases and the latest advancements in GraphQL technology; along with a new focus on leveraging GraphQL federation to support artificial intelligence.&nbsp;</p>



<figure class="wp-block-pullquote"><blockquote><p>Geoff Schmidt, CEO and co-founder of Apollo GraphQL, remarks: “As enterprise technology evolves, the rise of GraphQL represents a pivotal shift towards more efficient, scalable, and interconnected systems. The latest insights from Gartner reaffirm what we at Apollo GraphQL have long believed: GraphQL federation is not just a trend, but a fundamental technology shaping the future of digital experiences. Apollo GraphQL is committed to fostering an environment where developers and enterprises can learn, grow, and succeed with GraphQL. The upcoming GraphQL Summit is a reflection of this commitment, featuring talks from industry leaders like Coinbase and Netflix, and promises to be an invaluable opportunity for API platform engineers and leaders to discover how GraphQL federation revolutionizes API architectures for seamless, innovative systems that are driving the future of digital experiences.”</p></blockquote></figure>



<p>All GraphQL enthusiasts are invited to join the conversation by submitting to speak at the Summit. Whether an industry veteran or a newcomer, this is a chance to share insights, experiences, and innovations with the GraphQL community.</p>



<p>For more information about the GraphQL Summit or to submit your proposal to speak, please visit our website: <a href="http://www.graphqlsummit.com">www.graphqlsummit.com</a>.</p>



<h2 class="wp-block-heading"><a href="#resources" aria-hidden="true" class="aal_anchor" id="resources"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Resources</h2>



<ul class="wp-block-list">
<li>Read the<a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery"> latest Gartner report</a>, When to Use GraphQL to Accelerate API Delivery</li>



<li>Learn more about <a href="https://www.apollographql.com/blog/celebrating-five-years-of-apollo-federation">Apollo Federation</a>, Apollo’s implementation of GraphQL Federation&nbsp;</li>



<li>Stay up to date on the <a href="http://www.graphqlsummit.com">GraphQL Summit </a>agenda and learn more about it <a href="https://www.apollographql.com/blog/announcing-graphql-summit-2024-in-new-york-city">here</a></li>



<li><a href="https://www.apollographql.com/graphos/">Build </a>a GraphQL API platform today</li>



<li><a href="https://www.apollographql.com/tutorials/certifications/apollo-graph-professional/learning-path/">Become certified </a>as an Apollo GraphQL developer</li>



<li><a href="https://discord.com/invite/yFZJH2QYrK">Join</a> the Apollo GraphQL Community on Discord</li>
</ul>



<h2 class="wp-block-heading"><a href="#about-apollo-graphql" aria-hidden="true" class="aal_anchor" id="about-apollo-graphql"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>About Apollo GraphQL</h2>



<p><a href="https://apollographql.com">Apollo GraphQL </a>helps developers help the world by providing a better API platform across teams. Apollo’s open-source software is downloaded 25M times per month and its commercial GraphQL technologies power the most innovative brands today. Teams at Netflix, Snap, and the New York Times ship personalized, omnichannel experiences faster with a supergraph – a self-service GraphQL platform that spans any number of backend services. Serving over 5T requests in 2023, the Apollo GraphOS<sup>TM</sup> platform simplifies API development with workflows and infrastructure to build, test, and ship supergraphs at any scale. Based in San Francisco, Apollo is backed by Insight Partners, Andreessen Horowitz, Matrix Partners, and Trinity Ventures. Learn more at: <a href="https://www.apollographql.com">https://www.apollographql.com</a>.</p>


<ol class="wp-block-footnotes"><li id="5626a7a6-afc4-465e-84b4-2219decdae0e">Gartner, When to Use GraphQL to Accelerate API Delivery, By Shameen Pillai, et al, March 7, 2024. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved. <a href="#5626a7a6-afc4-465e-84b4-2219decdae0e-link" aria-label="Jump to footnote reference 1">↩︎</a></li></ol>

Image portays GraphQL Summit by Apollo logo and includes text that reads the conference for API platform engineering builders and leaders. October 8-10, 2024. Convene 225 Liberty New York City.

Apollo GraphQL Announces the Next GraphQL Summit Amid Rapid GraphQL Enterprise Adoption 


<p>GraphQL federation has emerged as the industry consensus for composing APIs at scale. Organizations such as Netflix, Expedia, and Wayfair quickly adopted this architecture to abstract API complexity and further adoption is on the rise.<a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery"> Gartner predicts</a> that “By 2027, 30% of enterprises using GraphQL will use GraphQL federation, up from less than 5% in 2024.”<sup data-fn="29ebcf61-2dba-471e-a128-d8d3f07a6d34" class="fn"><a href="#29ebcf61-2dba-471e-a128-d8d3f07a6d34" id="29ebcf61-2dba-471e-a128-d8d3f07a6d34-link">1</a></sup> This pattern didn’t emerge by accident; it was created and refined here at Apollo GraphQL. The first lines of <a href="https://www.apollographql.com/docs/federation/">Federation</a> code were published five years ago, so it’s the right moment to take a step back and examine the past, present, and future of this transformative technology.</p>



<h1 class="wp-block-heading"><a href="#graphql-federation-enables-a-platform-strategy" aria-hidden="true" class="aal_anchor" id="graphql-federation-enables-a-platform-strategy"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL federation enables a platform strategy</h1>



<p>Data storage and retrieval needs exploded decades ago, so SQL emerged. Container usage exploded years ago, so Kubernetes emerged. API development is exploding, so GraphQL federation has arrived. It’s declarative, composable, and self-service. Federation isn’t just an idea anymore: it’s a solution that has been proven, at scale, time and again. And according to Gartner, “Federation enables centralized governance, team autonomy (teams can own their own subgraphs), composability, and adaptability to evolving requirements at different speeds.”<sup>1</sup>&nbsp;&nbsp;</p>



<p>We at Apollo GraphQL believe GraphQL federation is now synonymous with GraphQL at enterprise scale. Companies such as Zillow, Square, Priceline.com, and Booking.com rely on Apollo Federation to power their API platforms. Read more about <a href="https://www.apollographql.com/blog/mlbs-api-strategy-hitting-a-home-run-transformation-with-graphql-midfield">how Federation powers Major League Baseball’s API strategy</a> and <a href="https://www.apollographql.com/blog/how-intuit-handled-their-busiest-time-of-year-with-apollo-router">how Intuit handled their busiest time of year with Apollo Router</a>.</p>



<p>These brands chose GraphQL to serve their product and platform goals, allowing them to ship better user experiences faster and without the overhead that legacy API architectures incentivize. Federation is:</p>



<ul class="wp-block-list">
<li><strong>Unified.</strong> Federation preserves the GraphQL experience client teams love by making this data accessible via a single endpoint.</li>



<li><strong>Modular.</strong> Federation makes it easier to break up a monolithic architecture. This enables teams to contribute to the graph independently at scale.</li>



<li><strong>Iterative.</strong> Teams can evolve their graph with confidence, surfacing backwards compatibility concerns early in the process thanks to robust composition rules.</li>
</ul>



<p>Whether you have one service or one thousand, they can all be composed into a single entry point without compromising their existing service boundaries. GraphQL is declarative, flexible, and supported by an open specification. Even if you have a small number of services (as few as one!), Federation can enrich your systems with new features out of the box. This piece isn’t a primer on how to use Apollo Federation, though &#8211; we highly recommend our <a href="https://www.apollographql.com/tutorials/">course catalog in Odyssey</a> for that.</p>



<h2 class="wp-block-heading"><a href="#" aria-hidden="true" class="aal_anchor" id=""><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><img decoding="async" src="https://lh7-us.googleusercontent.com/pagAz5iafYg9GqprnGVOzqsuCB4zbY83Bqh88ohnNXtv_iqW0o4xpAk9-8K1H5LRaybG7AbFjLTq41heJwJeuxob7qNlAQSdTx5frbfy-vkQ-U9o3YOjm-Y6lbWseBPLMMGBp6j3HXPxTMlvhJwUtLU" alt="Image portrays three visuals. The first visual is on GraphQL architecture and includes text that reads build a unified but modular graph of your data and services. The second visual showcases GraphQL infrastructure and includes text that reads Secure, scale, and govern the graph across any number of applications. The third visual showcases GraphQL workflows and includes text that reads enable teams to contribute to and consume the graph in a self-service way." width="&quot;624&quot;&quot;" height="253"></h2>



<h1 class="wp-block-heading"><a href="#how-we-got-here" aria-hidden="true" class="aal_anchor" id="how-we-got-here"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How we got here</h1>



<p>Federation wasn’t built overnight. Here’s a timeline of milestones we reached along the way:</p>



<h2 class="wp-block-heading"><a href="#2019" aria-hidden="true" class="aal_anchor" id="2019"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2019</h2>



<p><strong>Initial Apollo Federation commits published</strong>. After years of design and months of implementation and building on the vision Martijn Walraven <a href="https://www.youtube.com/watch?v=OFT9bSv3aYAa">spoke about</a> at GraphQL Summit 2018, our first lines of Federation <a href="https://github.com/apollographql/apollo-server/pull/2742">code</a> became complete enough to publish. Shortly afterwards we <a href="https://www.apollographql.com/blog/apollo-federation-f260cf525d21">released</a> Apollo Federation and Apollo Gateway, creating the GraphQL federation category. At GraphQL Summit 2019, <a href="https://www.youtube.com/watch?v=LKQKn1oFXJU">Jeff Hampton</a> and <a href="https://www.youtube.com/watch?v=EDqw-sGVq3k&amp;t=1047s">Matt DeBergalis</a> dove deep into the use case for GraphQL federation, how it works, and what solutions it offers</p>



<h2 class="wp-block-heading"><a href="#2020" aria-hidden="true" class="aal_anchor" id="2020"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2020</h2>



<p><strong>More expressive graphs</strong>. As developers embraced Federation and our tooling matured, we converged on a more elegant and complete set of <a href="https://www.apollographql.com/docs/federation/federated-types/federated-directives">directives</a> for creating federated graphs. Concepts like entities, owners, and required input data were fully fleshed out with feedback from our enterprise design partners and refined over time.</p>



<h2 class="wp-block-heading"><a href="#2021" aria-hidden="true" class="aal_anchor" id="2021"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2021</h2>



<p><strong>Apollo Federation 2.0 </strong><a href="https://www.apollographql.com/blog/announcing-federation-2"><strong>released</strong></a>. This version of Federation was created in close collaboration with the excellent engineers at Netflix. Apollo Federation 2 helps organizations operate even better across teams, leveraging shared types and the ability to migrate parts of a federated schema from one owner to another.</p>



<h2 class="wp-block-heading"><a href="#2022" aria-hidden="true" class="aal_anchor" id="2022"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2022</h2>



<p><strong>Apollo Router became </strong><a href="https://www.apollographql.com/blog/apollo-router-is-now-generally-available"><strong>generally available</strong></a>. Apollo Router has since become the standard-bearer for enterprise GraphQL at scale and is an indispensable part of the stack for a growing number of organizations.</p>



<h2 class="wp-block-heading"><a href="#2023" aria-hidden="true" class="aal_anchor" id="2023"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2023</h2>



<p><strong>Federated subscriptions </strong><a href="https://www.apollographql.com/blog/federated-subscriptions-in-graphos-real-time-data-at-scale"><strong>shipped</strong></a>. This enabled realtime data from anywhere in your infrastructure to all your clients, all made possible by protocol innovations and made available with a polished full-stack developer experience.</p>



<h1 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next</h1>



<p>Apollo is proud to be a founding member of the <a href="https://graphql.org/foundation/">GraphQL Foundation</a> and to be represented on the GraphQL Specification’s Technical Steering Committee and GraphQL Working Group. Since the composition and execution behaviors in Apollo Federation are becoming increasingly adopted by a wide array of users and toolmakers, there is a clear benefit for developing a common standard focused specifically on this domain.</p>



<p>Contributors from Apollo are working with others in the community to <a href="https://github.com/graphql/composite-schemas-spec">collaborate on a proposal</a> for a common specification within the GraphQL Working Group. We are beyond excited at the innovation that this effort will unlock, and thrilled that the community is moving towards a common understanding of the importance of this technology category.</p>



<h1 class="wp-block-heading"><a href="#a-universe-of-possibilities" aria-hidden="true" class="aal_anchor" id="a-universe-of-possibilities"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>A universe of possibilities</h1>



<p>Apollo is the leading GraphQL platform in the industry, serving the highest-volume, most demanding production workloads of today while developing the software that will power tomorrow’s use cases. In a rapidly changing world, enterprise organizations can count on the creators of Apollo Federation to continue to invest in solutions that meet and exceed the needs of the world’s largest platforms, all while empowering a robust and open GraphQL community.</p>


<ol class="wp-block-footnotes"><li id="29ebcf61-2dba-471e-a128-d8d3f07a6d34">Gartner, When to Use GraphQL to Accelerate API Delivery, By Shameen Pillai, et al, March 7, 2024. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved. <a href="#29ebcf61-2dba-471e-a128-d8d3f07a6d34-link" aria-label="Jump to footnote reference 1">↩︎</a></li></ol>

Five Years of Apollo Federation: the Standard for Enterprise API Platforms


<p>At last year’s GraphQL Summit, we learned why <a href="https://www.apollographql.com/blog/redefining-api-strategy-why-netflix-platform-engineering-chose-federated-graphql">Netflix placed a “big bet” on GraphQL federation</a>. We heard about <a href="https://www.apollographql.com/blog/how-intuit-handled-their-busiest-time-of-year-with-apollo-router">Intuit’s measured rollout of Apollo Router</a>. And we learned how <a href="https://www.youtube.com/watch?v=-4R6rLMZ9mc">federated subscriptions</a> enable client teams to deliver real-time updates to their apps – no matter where that data is stored. This year’s <a href="http://www.graphqlsummit.com">GraphQL Summit</a> is in New York City, and we expect an even better event this year.</p>



<p>After just five years, GraphQL federation is becoming a de facto skill to manage API complexity in distributed architectures. In fact, Gartner predicts that <a href="https://www.apollographql.com/resources/gartner-when-to-use-graphql-to-accelerate-api-delivery">30% of enterprises will incorporate GraphQL federation</a> into their stacks within three years. This architecture didn’t just take off at digital-native companies like Netflix, PayPal, and Expedia. It’s now a critical part of the API programs across industries like retail, healthcare, CPG, automotive, and many others. Organizations like Major League Baseball and Volvo Cars chose GraphQL federation to help them deliver immersive, omni-channel, and feature-rich digital experiences at any scale.</p>



<p>So what do the next five years look like for federated graphs? How can larger organizations leverage this architecture to roll out the next generation of personalized, AI-driven applications? That’s the theme of this year’s GraphQL Summit on October 8-10.</p>



<h2 class="wp-block-heading"><a href="#graphql-summit-the-ultimate-conference-for-api-platform-teams-and-decision-makers" aria-hidden="true" class="aal_anchor" id="graphql-summit-the-ultimate-conference-for-api-platform-teams-and-decision-makers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphQL Summit: The ultimate conference for API platform teams and decision-makers</h2>



<p>If you’re interested in learning how some of the most innovative companies in the world tackle these problems with GraphQL federation, don’t miss this year’s <a href="http://www.graphqlsummit.com">GraphQL Summit</a>. This event provides an insider’s look behind the API platforms and strategies that power some of the biggest digital brands on the internet today. Join a community of your peers to learn how they’re thinking about GraphQL in the AI era.</p>



<h3 class="wp-block-heading"><a href="#learn-connect-impact" aria-hidden="true" class="aal_anchor" id="learn-connect-impact"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Learn, connect, impact</h3>



<p>This year’s GraphQL Summit will be power-packed with useful talks, workshops, and networking opportunities. Whether you’ve been using GraphQL federation for years or are just evaluating it, you’ll benefit from real-world anecdotes and practical advice for managing a supergraph at any scale. This year’s Summit features talk tracks and hands-on workshops that cover architecture, platform management, human factors, and client development. There is also a new AI track, highlighting how to use GraphQL federation to power the next generation of applications.&nbsp;</p>



<p>GraphQL Summit isn’t just about technical know-how though. GraphQL federation is becoming a de facto component of a modern API platform. By attending this conference, you will learn how to modernize your API strategy to better reduce technical debt, improve developer velocity, drive a better user experience across applications, and help your organization better adapt to the ever-changing digital landscape.</p>



<h3 class="wp-block-heading"><a href="#and-drumrollhere-are-our-confirmed-speakers" aria-hidden="true" class="aal_anchor" id="and-drumrollhere-are-our-confirmed-speakers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>And *drumroll*…here are our confirmed speakers:</h3>



<ul class="wp-block-list">
<li>Marc-André Giroux, Senior Software Developer from Netflix and author of <em>Production-Ready GraphQL</em>&nbsp;</li>



<li>Stephanie Saunders, Engineering Manager at Coinbase</li>



<li>Mike Cohen, Senior Technical Fellow from Indeed</li>
</ul>



<p>Be sure to pay attention to Apollo on <a href="https://x.com/apollographql">X</a> and/or <a href="https://www.linkedin.com/company/apollo-graphql">LinkedIn</a> to find out our next batch of confirmed speakers. If you would like to share your GraphQL federation knowledge to the world, submit a talk at <a href="http://www.graphqlsummit.com">www.graphqlsummit.com</a>.&nbsp;</p>



<p><a href="https://summit.graphql.com/">Early bird tickets </a>are available until May 20th. We look forward to seeing you in New York City!</p>


Announcing GraphQL Summit 2024 in New York City


<p>GraphQL’s secret sauce is its ability to act as an abstraction layer for service-oriented backends, translating a sea of microservices into a more human-friendly representation of an organization’s data and capabilities. However, as a graph inevitably expands across more and more of the backend, it becomes increasingly difficult for the platform and backend teams that own it to fully understand its structure.&nbsp;</p>



<p>This pain is particularly acute at organizations deploying a federated GraphQL API (also known as a supergraph) at a massive scale with <a href="https://apollographql.com/docs/federation">GraphQL Federation</a>. The distributed nature of developing supergraphs makes it possible to scale them across many independent backend teams and domains, but it also significantly increases the complexity of the relationships in the schema and makes it difficult to find value in existing schema visualization tools which are designed for traditional monolithic graphs.&nbsp;</p>



<p>As the creators of Federation, we want to give API developers a better way to visually explore their supergraph. Today, we’re excited to release native schema visualization in Apollo GraphOS Studio, <strong>free</strong> ( 🎉) for all users. API architects and developers can now use <a href="https://www.apollographql.com/graphos">Apollo GraphOS</a> to visually explore the types, fields, and connections in their graph without running their graph locally, enabling introspection, or spinning up a separate visualization tool.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1493" height="814" src="https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis.png" alt="" class="wp-image-23493" srcset="https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis.png 1493w, https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis-300x164.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis-1024x558.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis-768x419.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/03/graph-vis-1200x654.png 1200w" sizes="auto, (max-width: 1493px) 100vw, 1493px" /></figure>



<h2 class="wp-block-heading"><a href="#centrally-explore-your-federated-graph" aria-hidden="true" class="aal_anchor" id="centrally-explore-your-federated-graph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Centrally explore your federated graph</h2>



<p>Historically, generating a schema visualization for a federated graph required jumping through some hoops. You either had to run the graph with introspection enabled (<a href="https://www.apollographql.com/blog/why-you-should-disable-graphql-introspection-in-production">generally not recommended</a> for production graphs) or copy-paste the supergraph SDL into a hosted visualization tool. For extra points, you could spin up your own visualization service and integrate it with your graph’s deployment pipeline, but even then you would probably experience limited returns as most out-of-the-box graph visualization libraries aren’t equipped to handle the scale and complexity of a supergraph.</p>



<p>With GraphOS Studio, you and your team can explore an always-up-to-date visualization of your graph with integrated capabilities like subgraph filtering and entity highlighting that simplify navigation for supergraphs. You can also copy and share a direct link to any view within the visualization to help other developers, product managers, and non-technical contributors understand the structure of the graph.</p>



<figure class="wp-block-video"><video autoplay controls loop muted src="https://wp.apollographql.com/wp-content/uploads/2024/03/vis-highlight-entities-1.mp4" playsinline></video></figure>



<h2 class="wp-block-heading"><a href="#visualize-graph-performance" aria-hidden="true" class="aal_anchor" id="visualize-graph-performance"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Visualize graph performance</h2>



<p>In addition to making large graphs more intelligible, the schema visualizer in GraphOS Studio also helps you uncover more actionable information by integrating metrics for your graph. From the Highlight drop-down in the UI, you can choose to highlight fields by error rate, request rate, and P95 latency, helping you understand which parts of the graph may need to be debugged or optimized.</p>



<figure class="wp-block-video"><video autoplay controls loop muted src="https://wp.apollographql.com/wp-content/uploads/2024/03/vis-highlight-usage-1.mp4" playsinline></video></figure>



<p>To dig further into errors and performance, you can navigate to the insights page for any field directly from the schema visualization UI.</p>



<figure class="wp-block-video"><video autoplay controls loop muted src="https://wp.apollographql.com/wp-content/uploads/2024/03/vis-to-insights.mp4" playsinline></video></figure>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p>Schema visualization is available today for all GraphOS users! To get started, log in or create a graph in <a href="https://studio.apollographql.com">GraphOS Studio</a>, and navigate to Schema &gt; Visualization. As always, we would love to hear your feedback so we can improve our visualization tools in future iterations. Don’t hesitate to drop us a question or comment in our community <a href="https://discord.gg/graphos">Discord</a>.</p>



<p>Happy visualizing!</p>


Visualizing federated GraphQL APIs with GraphOS Studio


<p><a href="https://apollographql.com">Apollo GraphQL</a>, the creator of GraphQL Federation, today announced its membership with the Cloud Native Computing Foundation (CNCF) as a Silver member. This strategic alliance reinforces Apollo GraphQL’s commitment to fostering innovation, enhancing API efficiency, and promoting the importance of GraphQL in platform engineering.&nbsp;</p>



<p>Platform engineering has emerged as one of the top strategic trends for 2024, for which the CNCF recently issued a<a href="https://tag-app-delivery.cncf.io/whitepapers/platforms/"> set of recommendations</a> and a <a href="https://tag-app-delivery.cncf.io/whitepapers/platform-eng-maturity-model/">maturity model </a>defining it. Apollo GraphQL helps API platform teams apply these recommendations to the API layer with Apollo GraphOS, its flagship product. Rather than delivering APIs as a barrage of new endpoints to manage, the Apollo GraphOS platform empowers teams to use GraphQL to build an API composition layer called a &#8216;supergraph&#8217;. This supergraph enables backend teams to connect APIs, and then makes them available to client teams via a single endpoint. Apollo GraphQL now offers a vision to significantly increase developer velocity using a supergraph in its new white paper, <a href="https://www.apollographql.com/resources/platform-engineering-for-apis">“Platform Engineering for APIs: Using GraphQL to Drive Developer Efficiency.”</a>&nbsp;</p>



<p>This approach introduces a self-service, self-documenting system, departing from traditional methods of building experience APIs or backends-for-frontends. It enables client teams to use a declarative query language to fetch the required data for their apps, reducing the cognitive load on product engineering teams. A supergraph also provides a scalable composition layer for backend teams, providing an architecture that can support any number of client applications. Using Apollo GraphOS, platform teams gain the tools to secure, scale, and operationalize a supergraph across any number of teams and applications.</p>



<p>Apollo GraphQL also recently launched a better workflow for backend teams to contribute to the graph with <a href="https://www.apollographql.com/blog/graphos-schema-proposals-a-principled-development-workflow-for-graphql-api-platforms?utm_campaign=2024-02-12_blog_graphos-schema-proposals&amp;utm_medium=social&amp;utm_source=linkedin">schema proposals</a> &#8211; a new centralized change management workflow that streamlines the process of proposing, reviewing, and approving schema changes to a supergraph.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p>“Platforms are transforming every layer of the stack and the supergraph provides the next chapter of the story — it&#8217;s the architecture of choice for combining services and APIs into coherent, integrated application experiences using GraphQL,” said Matt DeBergalis, CTO and co-founder at Apollo GraphQL. “Joining the Cloud Native Computing Foundation (CNCF) is an important milestone forward for Apollo GraphQL to bring GraphQL into an ecosystem focused on building and shaping the future of cloud-native composable platforms.”</p>
</blockquote>



<h2 class="wp-block-heading"><a href="#see-what-customers-are-talking-about" aria-hidden="true" class="aal_anchor" id="see-what-customers-are-talking-about"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>See what customers are talking about</h2>



<p>Apollo GraphQL will be a sponsor and exhibit at the eminent <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/">KubeCon + CloudNativeCon Europe 2024</a>, the Cloud Native Computing Foundation&#8217;s flagship conference that gathers adopters and technologists from leading open source and cloud native communities. Visitors to Apollo GraphQL’s booth will see the platform that enables API platform teams, such as <a href="https://www.apollographql.com/blog/mlbs-api-strategy-hitting-a-home-run-transformation-with-graphql-midfield">MLB</a> and <a href="https://www.apollographql.com/blog/how-intuit-handled-their-busiest-time-of-year-with-apollo-router">Intuit</a>, connect their APIs and deliver a self-service graph that can power any number of applications. Visitors will be able to have one-on-one conversations with the Apollo GraphQL team and will also be eligible to win great prizes.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#resources" aria-hidden="true" class="aal_anchor" id="resources"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Resources</h2>



<ul class="wp-block-list">
<li>Download the white paper, <a href="https://www.apollographql.com/resources/platform-engineering-for-apis">Platform Engineering for APIs</a></li>



<li>Learn more and engage with the Apollo GraphQL team at booth #G33 at <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/">KubeCon + CloudNativeCon Europe 2024</a> from March 19-22</li>



<li><a href="https://www.apollographql.com/supergraph/">Learn</a> more about supergraphs</li>



<li><a href="https://www.apollographql.com/graphos/">Build </a>a GraphQL API platform today</li>



<li><a href="https://www.apollographql.com/tutorials/certifications/apollo-graph-professional/learning-path/">Become certified </a>as an Apollo GraphQL developer</li>



<li><a href="https://discord.com/invite/yFZJH2QYrK">Join</a> the Apollo GraphQL Community on Discord</li>



<li>For more information on the CNCF or to see the full list of new members, read the <a href="https://www.cncf.io/announcements/2024/03/20/45-new-members-join-the-cloud-native-computing-foundation/">press release</a></li>
</ul>



<h2 class="wp-block-heading"><a href="#about-apollo-graphql" aria-hidden="true" class="aal_anchor" id="about-apollo-graphql"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>About Apollo GraphQL</strong></h2>



<p><a href="https://apollographql.com">Apollo GraphQL </a>helps developers help the world by providing a better API platform across teams. Apollo’s open-source software is downloaded 25M times per month and its commercial GraphQL technologies power the most innovative brands today. Teams at Netflix, Snap, and the New York Times ship personalized, omnichannel experiences faster with a supergraph – a self-service GraphQL platform that spans any number of backend services. Serving over 5T requests in 2023, the Apollo GraphOS platform simplifies API development with workflows and infrastructure to build, test, and ship supergraphs at any scale. Based in San Francisco, Apollo is backed by Insight Partners, Andreessen Horowitz, Matrix Partners, and Trinity Ventures. Learn more at: <a href="https://www.apollographql.com">https://www.apollographql.com</a>.</p>


Apollo GraphQL to join Cloud Native Computing Foundation Membership as Silver Sponsor


<p>As an engineering organization grows, the quality of its internal developer platforms directly influences its ability to execute. It’s why <a href="https://www.gartner.com/en/articles/what-is-platform-engineering">80% of large software organizations are expected to establish platform engineering teams by 2026</a> and why many existing platform teams are turning to federated GraphQL APIs, known as <a href="https://www.apollographql.com/docs/resources/glossary/#supergraph">supergraphs</a>, to build self-service API platforms. Client teams leverage these platforms to quickly build features without orchestrating APIs, and backend teams autonomously contribute services from their respective domains via modules called subgraphs.</p>



<p>However, contributions that affect the <em>shape</em> of your supergraph (i.e. the schema) still require cross-team coordination to ensure (1) we are designing the schema in a way that continues to benefit developer velocity, (2) that we don’t break client apps, and (3) that our changes don’t conflict with other backend teams’ subgraph schemas. The modularity of the supergraph can make this coordination tricky since each subgraph schema may live in a different codebase, and not every required contributor or approver may have access to each of those codebases.</p>



<p>Apollo aims to make it easy for any number of teams to better collaborate and contribute to a supergraph. Today, we are excited to announce general availability of <a href="https://www.apollographql.com/docs/graphos/delivery/schema-proposals">GraphOS Schema Proposals</a> – a new centralized change management workflow in GraphOS Studio that streamlines the process of proposing, reviewing, and approving schema changes to a supergraph.</p>



<h2 class="wp-block-heading"><a href="#centrally-manage-changes-with-integrated-checks" aria-hidden="true" class="aal_anchor" id="centrally-manage-changes-with-integrated-checks"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Centrally manage changes with integrated checks</h2>



<p>Developers contributing to a supergraph are typically distributed across multiple teams, making it difficult to take advantage of traditional change management workflows that application teams use across a particular codebase. Although these workflows provide the right tooling, they are implemented at too granular of a level, failing to provide the visibility into the overall impact to the supergraph that platform teams require.&nbsp;</p>



<p>GraphOS Schema Proposals provide a purpose-built change management workflow for the API platform layer, allowing developers and platform engineers across multiple teams to propose, review, and approve schema changes.</p>



<h3 class="wp-block-heading"><a href="#propose-and-test-schema-changes" aria-hidden="true" class="aal_anchor" id="propose-and-test-schema-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Propose and test schema changes</h3>



<p>Proposing a schema change in GraphOS is the first step to making a change to a supergraph. GraphOS Studio now has an integrated schema editor that subgraph developers can use to make changes to existing subgraph schemas or even create new subgraph schemas from scratch.&nbsp;</p>



<p>The schema editor is integrated with all of the other great features of GraphOS Studio, allowing authors to see GraphQL-aware diffing in real time and run linter checks as they work.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="820" src="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor.png" alt="" class="wp-image-23342" srcset="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor.png 1600w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor-300x154.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor-1024x525.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor-768x394.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor-1536x787.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-editor-1200x615.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<p>Whenever someone saves a revision on a proposal, GraphOS Studio will automatically run <a href="https://www.apollographql.com/docs/graphos/delivery/schema-checks/">schema checks</a> to validate that the proposed schema changes will compose with other existing subgraphs and won’t break client operations.</p>



<h3 class="wp-block-heading"><a href="#review-and-approve-schema-changes" aria-hidden="true" class="aal_anchor" id="review-and-approve-schema-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Review and approve schema changes</h3>



<p>Once someone on your team has drafted a schema proposal, the author can mark it as <code>OPEN FOR FEEDBACK</code><em> </em>to make it visible to other subgraph, platform, and client developers with the proper permissions. If the proposal needs approval from specific reviewers like a team lead or a potentially affected client developer, the author can request a review from those users.&nbsp;</p>



<p>If your organization has a governance policy that requires certain users to approve every schema change for a graph – a platform team lead, for example – graph admins can add those users as <em>default</em> reviewers from the graph settings page. Admins can also set a minimum number of reviewers required for a proposal to be <code>APPROVED</code>.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="662" src="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request.png" alt="" class="wp-image-23344" srcset="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request.png 1600w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request-300x124.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request-1024x424.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request-768x318.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request-1536x636.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-review-request-1200x497.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<p>Once the minimum number of approvals has been reached and any mandatory default reviewers have approved the proposal, the proposal is marked as <code>APPROVED</code> and is ready for publishing.</p>



<h2 class="wp-block-heading"><a href="#publish-approved-changes" aria-hidden="true" class="aal_anchor" id="publish-approved-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Publish approved changes</h2>



<p>In addition to editing and reviews, GraphOS Schema Proposals also provides developers with a streamlined workflow for implementing approved changes locally and safeguards to prevent unapproved changes from being published.</p>



<p>Once a developer has created a proposal, subgraph developers can use Apollo’s Rover CLI to quickly <a href="https://www.apollographql.com/docs/graphos/delivery/schema-proposals/implementation#pull-proposed-schemas-with-rover">pull associated subgraph schemas</a> with rover subgraph fetch. From this point, subgraph developers can then follow the standard steps for developing and delivering changes to their subgraph:</p>



<ol class="wp-block-list">
<li>Make local changes to subgraph server code, including updating or writing new resolvers</li>



<li>Run GraphOS schema checks locally using the Rover CLI (including a new Proposals task to verify that schema changes have a matching approved proposal in GraphOS)</li>



<li>Publish the subgraph schema to GraphOS</li>



<li>Deploy changes to your subgraph server</li>
</ol>



<p><em>(Note: the Schema Proposals workflow </em><strong><em>does not</em></strong><em> automate the above steps, but </em><a href="https://www.apollographql.com/docs/rover/ci-cd/"><em>they can be automated in your CI/CD pipelines using the Rover CLI</em></a><em>)</em></p>



<h3 class="wp-block-heading"><a href="#preventing-publishing-of-unapproved-changes" aria-hidden="true" class="aal_anchor" id="preventing-publishing-of-unapproved-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Preventing publishing of unapproved changes</h3>



<p>Although the proposals workflow does not automate the deployment process for schema changes, the new Proposal task in the schema checks workflow does provide a safeguard against publishing unapproved changes. Graph Admins can enable or disable the Proposal task in graph settings, and they can also configure the severity of the check to <code>Error</code> or <code>Warn</code>.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="797" src="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff.png" alt="" class="wp-image-23346" srcset="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff.png 1600w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff-300x149.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff-1024x510.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff-768x383.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff-1536x765.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-diff-1200x598.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<p>Setting the Proposal task severity to <code>Error</code> will cause schema checks to fail if any schema changes do not have a matching approved proposal. This includes schema checks that are run locally as well as when a schema is published to GraphOS, ensuring that unapproved changes are never published to the supergraph.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="488" src="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity.png" alt="" class="wp-image-23348" srcset="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity.png 1600w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity-300x92.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity-1024x312.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity-768x234.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity-1536x468.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-check-severity-1200x366.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p>Schema Proposals are generally available today for all <a href="https://apollographql.com/pricing">GraphOS Enterprise</a> customers. To create a proposal, navigate to your graph in GraphOS Studio, and open the Proposals page from the left navigation. For a full walkthrough of creating and managing proposals, head over to the <a href="https://www.apollographql.com/docs/graphos/delivery/schema-proposals/">Schema Proposals documentation</a>.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="429" src="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav.png" alt="" class="wp-image-23350" srcset="https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav.png 1600w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav-300x80.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav-1024x275.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav-768x206.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav-1536x412.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/02/proposals-nav-1200x322.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<p>To learn more about GraphOS Schema Proposals and agile API platform development, <a href="https://bit.ly/42E9vd9">join Apollo’s webinar</a> on February 22, 2024 with Parul Schroff, product manager for GraphOS Schema Proposals! Here are a few things the talk will cover:</p>



<ul class="wp-block-list">
<li>How federated GraphQL enables platform engineering teams to build a self-serve API platform</li>



<li>How Apollo GraphOS can help your team operationalize delivering a federated graph</li>



<li>How to leverage GraphOS Schema proposals to streamline federated schema design, review, and implementation</li>
</ul>



<p>We hope to see you there!</p>


GraphOS Schema Proposals: a principled development workflow for GraphQL API platforms


<p>Over the past two years, the emergence of AI-driven tools has significantly transformed the tech landscape. Among these innovations, tools designed specifically for code generation—such as Copilot, CodeLlama, and others—have garnered particular attention from developers.&nbsp;</p>



<p>According to a survey conducted by GitHub, 92% of U.S.-based developers are already using AI coding tools both in and outside of work <a href="https://github.blog/2023-06-13-survey-reveals-ais-impact-on-the-developer-experience/">(source)</a>.</p>



<p>These tools offer immense value for tasks like rapid prototyping and brainstorming, serving as powerful allies in the development process. However, despite their advanced capabilities, a notable gap exists in their ability to generate high-quality GraphQL schemas.</p>



<p>I&#8217;m sure most, if not all of us, wish to craft the finest GraphQL schema possible—even if it&#8217;s just for a prototype. If you’ve watched my <a href="https://www.youtube.com/watch?v=p4jP2xnImAM">“Let&#8217;s Build a Supergraph Using ChatGPT” talk at GraphQL Summit</a>, you might know some of the ways you can steer tools like ChatGPT to improve the output of the generated code.</p>



<p>But let&#8217;s be real. The results aren&#8217;t always perfect, and it almost feels like ChatGPT clings onto some less-than-desirable practices! Consider this scenario: when I request ChatGPT to construct a schema for a note-taking application, this is the outcome:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">type Query {
  getNotes: [Note]
  getNoteById(id: ID!): Note
  getTags: [Tag]
}

type Mutation {
  createNote(title: String!, body: String!): Note
  createTag(name: String!): Tag
  addTagToNote(noteId: ID!, tagId: ID!): Note
}

type Note {
  id: ID!
  title: String!
  body: String!
  tags: [Tag]
}

type Tag {
  id: ID!
  name: String!
  notes: [Note]
}
</code></pre>



<p>Clearly, this schema has room for improvement. It includes generally discouraged practices like utilizing &#8216;get&#8217; in query fields and lacking important elements like pagination. It also overlooks important components such as mutation payloads and input types, essential for successful schema evolution.</p>



<p>During my presentation, I shared our experience with fine-tuning GPT-3.5 for optimized GraphQL schema generation. We did notice improvements on schema generation from the standard models, but it wasn&#8217;t flawless. On numerous occasions, the model failed to meet our set guidelines for schema generation or it was generating schemas that were less than ideal.</p>



<p>So we’ve been working more to make the output much better and make sure it would follow the best practices as often as possible, and we are finally ready to share it with you all!</p>



<p>To try it is pretty simple! <a href="https://discord.gg/SzeywawCa6">Join our Discord server</a>, go to the <strong>#ai-schema-design</strong> forum and post a message describing the schema you’d like to create, for example:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p><strong>Title:</strong> Note taking application&nbsp;</p>



<p>I&#8217;m building a note taking application. Users can create notes, and each note has a title and a body. Users can also create tags, and each tag has a name. Users can add tags to notes, and notes can have multiple tags.</p>
</blockquote>



<p>Then after submitting the bot will create a schema based on your inputs! The more specific you are the better the schema will be 😊And you’ll be able to keep iterating with the bot to improve the schema or even to see some operation that you could run with your schema</p>



<p>Here’s an example of the schema generator in action:</p>



<figure class="wp-block-video"><video autoplay controls loop muted src="https://wp.apollographql.com/wp-content/uploads/2024/02/CleanShot-2024-02-05-at-18.48.38.mov" playsinline></video></figure>



<p>I hope this will be useful for your schema design journey, and remember we’ll always be happy to help you with your schemas, so feel free to ping me or any other Developer Advocate in <a href="https://discord.gg/SzeywawCa6">our Discord server</a>.&nbsp;</p>


Fun with AI – Generating GraphQL Schemas in Discord


<p>Modern apps must support real-time use cases like flight changes, team collaboration, or live score updates for the big game. GraphQL subscriptions push events in a more efficient and performant way compared to traditional client-side polling of RESTful services that try to pull new events every few seconds. Instead of polling, clients can subscribe to the specific data they require, and the graph immediately delivers those events as they occur, reducing backend load and providing faster real-time updates.</p>



<p>Traditionally, GraphQL subscriptions have been implemented with WebSockets, an approach with many issues, including compression, debugging, scalability, and compatibility with firewalls, load-balancers, and other networking infrastructure.</p>



<p>We addressed the frontend portion of the WebSocket problem in June 2023, when we announced <a href="https://www.apollographql.com/blog/federated-subscriptions-in-graphos-real-time-data-at-scale" target="_blank" rel="noreferrer noopener">Federated subscriptions in GraphOS</a> with support for a new <a href="https://www.apollographql.com/docs/react/data/subscriptions/#subscriptions-via-multipart-http" target="_blank" rel="noreferrer noopener">HTTP multipart protocol</a> based on the underlying protocol for GraphQL @defer support in <a href="https://www.apollographql.com/docs/router/executing-operations/defer-support/" target="_blank" rel="noreferrer noopener">Apollo Router</a>. This makes hosting a real-time API in any cloud environment easier, with all the benefits of a standard HTTP connection.</p>



<p>However, on the backend, Apollo Router supports legacy WebSocket protocols for compatibility with existing subgraph APIs, which is inefficient at scale. For example, if a subscription can’t be <a href="https://www.apollographql.com/docs/router/executing-operations/subscription-support/#subscription-deduplication" target="_blank" rel="noreferrer noopener">deduplicated</a>, 1 million client subscriptions would require 1 million backend WebSockets connections.&nbsp;</p>



<p>Today, we are excited to announce the GA release of Apollo Router 1.37 with <a href="https://www.apollographql.com/docs/router/executing-operations/subscription-callback-protocol/" target="_blank" rel="noreferrer noopener">HTTP callback support</a>, designed in partnership with the GraphQL community. HTTP callback support solves the backend WebSocket problem and dramatically reduces the number of open subgraph connections. This results in the same great performance but with more efficiency at scale and reduces real-time cloud spend for router and subgraph deployments.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="2560" height="1118" src="https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-scaled.jpg" alt="" class="wp-image-23275" srcset="https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-scaled.jpg 2560w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-300x131.jpg 300w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-1024x447.jpg 1024w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-768x335.jpg 768w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-1536x671.jpg 1536w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-2048x894.jpg 2048w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-1200x524.jpg 1200w, https://wp.apollographql.com/wp-content/uploads/2024/01/Frame-11-1980x865.jpg 1980w" sizes="auto, (max-width: 2560px) 100vw, 2560px" /></figure>



<p>Subscription callbacks offer new levels of flexibility and interoperability between the router and underlying services. By default, federated subscriptions use WebSockets, which requires two long-lived connections for every client: one between the client and the router and one between the router and the subgraph. Additionally, these long-lived connections aren’t well suited for serverless infrastructures.&nbsp;</p>



<p>With HTTP callbacks, on the other hand, the router no longer manages a WebSocket connection with subgraphs, and it’s flexible enough to be used with other Pub/Sub architectures that can support HTTP requests.</p>



<h2 class="wp-block-heading"><a href="#http-callbacks-for-federated-subscriptions" aria-hidden="true" class="aal_anchor" id="http-callbacks-for-federated-subscriptions"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>HTTP Callbacks for Federated Subscriptions</h2>



<p>Here’s what you’ll need to use federated subscriptions with self-hosted instances of Apollo Router:</p>



<ol class="wp-block-list">
<li>An active Apollo GraphOS Enterprise plan</li>



<li>A federated GraphQL API with
<ol class="wp-block-list">
<li>One or more HTTP callback-compatible GraphQL servers, such as <a href="https://www.apollographql.com/docs/apollo-server/api/plugin/subscription-callback" target="_blank" rel="noreferrer noopener">Apollo Server</a> &gt;= 4.10.0 or <a href="https://github.com/apollographql/federation-jvm/tree/main/spring-subscription-callback#usage" target="_blank" rel="noreferrer noopener">Spring GraphQL</a> &gt;= 4.3.0</li>



<li><a href="https://github.com/apollographql/router/releases/tag/v1.37.0" target="_blank" rel="noreferrer noopener">Apollo Router v1.37</a> or greater</li>
</ol>
</li>



<li>The latest version of Apollo Client (Web, iOS, or Kotlin) with HTTP-based subscriptions support.</li>
</ol>



<p>If you don’t have a GraphOS Enterprise plan and you need to self-host the Apollo Router for an enterprise-scale deployment, try out <a href="https://studio.apollographql.com/signup?type=enterprise-trial&amp;referrer=blog" target="_blank" rel="noreferrer noopener">GraphOS Enterprise</a> for free for 28 days.</p>



<h3 class="wp-block-heading"><a href="#migrating-from-the-preview-to-ga" aria-hidden="true" class="aal_anchor" id="migrating-from-the-preview-to-ga"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Migrating from the preview to GA</h3>



<p>If your application already uses the preview of subscription callbacks, there are a few things to change in your Router configuration to migrate to the GA:</p>



<ol class="wp-block-list">
<li>Change the name of the option from <code>subscription.mode.preview_callback</code> to <code>subscription.mode.callback</code>. Failure to use the updated option name when running the router will result in an error, and the router won&#8217;t start.</li>



<li>Update the <code>public_url</code> field to include the full URL of your callback endpoint. Previously, in the preview, the public URL used by the router was the automatic concatenation of the <code>public_url</code> and <code>path</code> fields. In GA, the behavior has changed, and the router uses the value set in <code>public_url</code>. This enables you to configure your public URL, for example, if you have a proxy in front of the router and want to configure redirection with the public URL.</li>



<li>Configure the new <code>heartbeat_interval</code> field to set the period that a heartbeat must be sent to the callback endpoint for the subscription operation. The default heartbeat interval is 5 seconds. You can turn off heartbeats, for example, if you’re operating in a serverless architecture without long-lived processes, by setting <code>heartbeat_interval: disabled</code>.</li>
</ol>



<h2 class="wp-block-heading"><a href="#try-it-today" aria-hidden="true" class="aal_anchor" id="try-it-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Try it today!</h2>



<p>We’re excited for you to try <a href="https://www.apollographql.com/docs/router/executing-operations/subscription-callback-protocol/" target="_blank" rel="noreferrer noopener">HTTP callbacks in GraphOS</a> and would love to hear your thoughts. If you have any questions or feedback for the team, feel free to reach out to us in our<a href="https://discord.com/invite/graphos" target="_blank" rel="noreferrer noopener"> Discord</a>.</p>


Reduce real-time cloud spend with Federated Subscriptions support for HTTP Callbacks


<p>With the release of Apollo Client 3.9, we&#8217;re excited to announce a host of new features and improvements, including:</p>



<ul class="wp-block-list">
<li>Suspense-enabled data fetching in response to user interaction with <code>useLoadableQuery</code></li>



<li>Preloading data outside of React with <code>createQueryPreloader</code> and <code>preloadQuery</code></li>



<li>Memory usage optimizations</li>



<li>A new&nbsp;<code>useQueryRefHandlers</code>&nbsp;hook for accessing <code>refetch</code> and <code>fetchMore</code> for a given <code>queryRef</code></li>



<li>Multipart subscriptions network adapters for Relay and urql</li>



<li><code>MockedProvider</code> improvements</li>
</ul>



<p>Let&#8217;s dive in!</p>



<h2 class="wp-block-heading"><a href="#suspense-enabled-data-fetching-in-response-to-user-interaction-with-useloadablequery" aria-hidden="true" class="aal_anchor" id="suspense-enabled-data-fetching-in-response-to-user-interaction-with-useloadablequery"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Suspense-enabled data fetching in response to user interaction with <code>useLoadableQuery</code></h2>



<p>When it comes to Suspense-enabled data fetching in Apollo Client, <code>useSuspenseQuery</code> and <code>useBackgroundQuery</code> are useful for loading data as soon as the component calling the hook mounts. But what about loading a query in response to user interaction? For example, you may want to start loading some data when a user hovers on a link.</p>



<p>Introducing the <code>useLoadableQuery</code> hook 🎉 For more information, see <a href="https://www.apollographql.com/docs/react/data/suspense#fetching-in-response-to-user-interaction">its documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#preloading-data-outside-of-react-with-createquerypreloader-and-preloadquery" aria-hidden="true" class="aal_anchor" id="preloading-data-outside-of-react-with-createquerypreloader-and-preloadquery"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Preloading data outside of React with <code>createQueryPreloader</code> and <code>preloadQuery</code></h2>



<p>Starting with Apollo Client 3.9, queries can be initiated outside of React. This allows your app to begin fetching data <em>before</em> React renders your components, and can provide performance benefits.</p>



<p>To preload queries, you first need to create a preload function with <code>createQueryPreloader</code>. <code>createQueryPreloader</code> takes an <code>ApolloClient</code> instance as an argument and returns a function that, when called, initiates a network request.</p>



<p>The preload function returns a <code>queryRef</code> that is passed to <a href="https://www.apollographql.com/docs/react/api/react/hooks/#usereadquery"><code>useReadQuery</code></a> to read the query data and suspend the component while loading. <code>useReadQuery</code> will ensure that your component is kept up-to-date with cache updates for the preloaded query.</p>



<p>This feature pairs nicely with popular routers such as React Router and TanStack Router, both of which provide APIs for loading data before route components render (such as the <a href="https://reactrouter.com/en/main/route/route#loader"><code>loader</code> function</a> from React Router). It provides the benefits of earlier fetching without sacrificing the ability to automatically re-render when future cache updates occur.</p>



<p>This feature is in alpha in 3.9 and may be subject to change before 3.10. If you&#8217;d like to provide feedback before it&#8217;s stabilized, please visit <a href="https://github.com/apollographql/apollo-client/issues/11519">#11519</a> and add a comment.</p>



<p>For more information, see <a href="https://www.apollographql.com/docs/react/data/suspense#initiating-queries-outside-react">its documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#introducing-a-new-usequeryrefhandlers-hook" aria-hidden="true" class="aal_anchor" id="introducing-a-new-usequeryrefhandlers-hook"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Introducing a new&nbsp;<code>useQueryRefHandlers</code>&nbsp;hook</h2>



<p><code>useQueryRefHandlers</code> is a hook that returns <code>refetch</code> and <code>fetchMore</code> functions for a given <code>queryRef</code>. It&#8217;s useful for gaining access to these handlers for a <code>queryRef</code> that was created by <code>createQueryPreloader</code>, or to avoid passing these handlers down through your component tree.</p>



<p>For more information, see <a href="https://www.apollographql.com/docs/react/api/react/hooks/#usequeryrefhandlers">its documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#memory-usage-optimizations" aria-hidden="true" class="aal_anchor" id="memory-usage-optimizations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Memory usage optimizations</h2>



<p>Spanning over twenty memory-related pull requests, 3.9 includes a host of improvements and optimizations related to memory usage.</p>



<p>You can find a comprehensive list in <a href="https://www.apollographql.com/blog/author/lenz">Lenz</a>&#8216;s December <a href="https://www.apollographql.com/blog/apollo-3-9-beta-feature-spotlight-the-memory-story">blog post</a>, but at a high level this work includes many fixes and improvements and introduces <strong>the ability to granularly configure Apollo Client’s internal memoization</strong>.</p>



<p>Memoization is always a trade-off between processing time and memory, and some of our old cache limits erred on the side of consuming more memory. While the new defaults should be sufficient for most applications, we know that some will need to make different trade-offs so we made each cache size individually configurable, both before and after the Apollo Client has been initialized. </p>



<p>For more information, see our new <a href="https://www.apollographql.com/docs/react/caching/memory-management/">documentation page for memory management</a> and share your <code>ApolloClient.getMemoryInternals()</code> values <a href="https://github.com/apollographql/apollo-client/issues/11444">in this issue</a>!</p>



<h2 class="wp-block-heading"><a href="#multipart-subscriptions-network-adapters-for-relay-and-urql" aria-hidden="true" class="aal_anchor" id="multipart-subscriptions-network-adapters-for-relay-and-urql"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Multipart subscriptions network adapters for Relay and urql</h2>



<p>With the launch of <a href="https://www.youtube.com/watch?v=-4R6rLMZ9mc&amp;list=PLpi1lPB6opQzUOqG3QroLLN06FF-Q_uhX&amp;index=5">federated subscriptions</a> in the Apollo Router last year, Apollo Client added support for GraphQL <a href="https://www.apollographql.com/docs/react/data/subscriptions/#subscriptions-via-multipart-http">subscriptions over HTTP</a>.</p>



<p>In 3.9, we&#8217;re shipping network adapters for Relay and urql to make consuming subscriptions via multipart HTTP a breeze no matter which client library you&#8217;re using. For more information, see <a href="https://www.apollographql.com/docs/react/data/subscriptions/#http">the documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#mockedprovider-improvements" aria-hidden="true" class="aal_anchor" id="mockedprovider-improvements"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><code>MockedProvider</code> improvements</h2>



<p>This release also introduces two frequently requested improvements to the testing utility, <code>MockedProvider</code>:</p>



<ul class="wp-block-list">
<li><strong>Reusing mocks:</strong> By default, a mock is only used once. If you want to reuse a mock for multiple operations, you can now set the <code>maxUsageCount</code> field to a number indicating how many times the mock should be used.</li>



<li><strong>Dynamic variables:</strong> The <code>MockedResponse</code> object now takes a <code>variableMatcher</code> property that is a function that takes the variables and returns a boolean indication if this mock should match the invocation for the provided query. This can be useful when the exact value of the variables being passed are not known, or for asserting specific variables individually.</li>
</ul>



<p>For more on these enhancements, see our complete documentation on <a href="https://www.apollographql.com/docs/react/development-testing/testing/#testing-the-loading-and-success-states">testing React components</a>. Finally, to keep an eye on future testing improvements slated for 3.10, this <a href="https://github.com/apollographql/apollo-client/issues/9738">GitHub issue</a> is the one to watch.</p>



<p>You can browse the <a href="https://github.com/apollographql/apollo-client/releases/tag/v3.9.0">full changelog</a> on GitHub. Happy querying!</p>



<p><a href="https://github.com/apollographql/apollo-client/blob/main/ROADMAP.md#future-3x-releases"></a></p>


What’s new in Apollo Client 3.9


<p>As platforms, teams, and products evolve, we sometimes need new or different ways to deploy our APIs. Strong Continuous Integration / Continuous Deployment (CI/CD) practices and recovery strategies are necessary components of any <a href="https://aws.amazon.com/blogs/mt/establishing-rpo-and-rto-targets-for-cloud-applications/" target="_blank" rel="noreferrer noopener">Recovery Time Objective (RTO) and Recovery Point Objective (RPO)</a>. </p>



<p>The recommended GraphOS <a href="https://www.apollographql.com/tutorials/workshop-summit-graphos-basics/08-changes-process" target="_blank" rel="noreferrer noopener">continuous deployment</a> process uses <a href="https://www.apollographql.com/docs/federation/managed-federation/uplink/" target="_blank" rel="noreferrer noopener">Apollo Uplink</a> to update the Router fleet in place with new supergraph schemas that pass checks in the GraphOS build pipeline along with automated testing in lower environments such as dev or test. However, some organizations have specific deployment needs that rely on an immutable schema for blue-green deploys or canary releases.</p>



<p>Today, Apollo is excited to release enhanced GraphOS Platform APIs that streamline integration with immutable blue-green and canary deployments workflows beyond the in-place continuous GraphOS updates that most customers use today:</p>



<ol class="wp-block-list">
<li><a href="https://studio.apollographql.com/graph/apollo-platform/variant/main/schema/reference/objects/GraphMutation?_gl=1*1yu3yv*_ga*NDMzNzY1NzQ4LjE3MDI5MTM0MDk.*_ga_0BGG5V2W2K*MTcwNTEwMzIwNC4zMi4xLjE3MDUxMDM1NzEuMC4wLjA.#publishSubgraphs" target="_blank" rel="noreferrer noopener">PublishSubgraphsMutation</a> will publish all of the releases’ subgraphs as a single unit and return the associated launch and downstream Contract launches.</li>



<li><a href="https://studio.apollographql.com/graph/apollo-platform/variant/main/schema/reference/objects/Launch#status" target="_blank" rel="noreferrer noopener">PollLaunchStatusQuery</a> will poll for the status of any individual launch by ID.</li>



<li><a href="https://studio.apollographql.com/graph/apollo-platform/variant/main/schema/reference/scalars/GraphQLDocument" target="_blank" rel="noreferrer noopener">FetchSupergraphSDLQuery</a> will fetch the supergraph schema of the launch.</li>
</ol>



<p>These GraphOS Platform API updates are versatile enough to support many deployment strategies.</p>



<p><a href="https://www.apollographql.com/docs/federation/managed-federation/deployment/#example-blue-green-deployment" target="_blank" rel="noreferrer noopener">Blue-green deployment</a> involves maintaining two identical production environments: the &#8220;Blue&#8221; and the &#8220;Green.&#8221; Only one of these environments is live at any given time. When it&#8217;s time to deploy an update to a supergraph, the team releases it to the inactive environment. For instance, the new version is deployed to “Green” if “Blue” is live. Once the new “Green” version is thoroughly tested and deemed stable, the team switches traffic from “Blue” to “Green.” With these updates to the GraphOS Platform API, <a href="https://www.apollographql.com/docs/graphos/metrics/" target="_blank" rel="noreferrer noopener">metrics and insights</a> for both stages, the “Blue” and the “Green,” are available in a consolidated place under a single Production variant, which has a single launch history to track schema changes over time.</p>



<p><a href="https://www.apollographql.com/docs/federation/managed-federation/deployment/#example-canary-deployment" target="_blank" rel="noreferrer noopener">Canary deployment</a>, on the other hand, is a more gradual process. It involves first rolling out the new supergraph updates to a small subset of users rather than switching simultaneously. This subset, or &#8220;canary group,&#8221; receives the update and is closely monitored by the platform team for any issues. If the deployment is successful, the team rolls out the update to a more significant portion of the user base and eventually to all users.</p>



<p>While we recommend rolling forward to recover in most cases, <a href="https://www.apollographql.com/docs/federation/managed-federation/deployment/#rolling-back-a-deployment" target="_blank" rel="noreferrer noopener">rollbacks</a> can be helpful in some scenarios. For example, consider a blue-green deployment where a team deploys the Router and all subgraphs as a single versioned release and houses <strong>immutable schemas</strong> within each Docker image. Then, if the need arises for a rollback, they can simply re-deploy the old Docker images, and the correct supergraph schema will be used. This helps ensure compatibility with existing blue-green workflows that assume an immutable infra mindset.</p>



<p>For platform teams looking to enhance their GraphQL platform stance, stay tuned for additional GraphOS Platform API updates and learn more about <a href="https://www.apollographql.com/docs/federation/managed-federation/deployment/" target="_blank" rel="noreferrer noopener">deployment and rollback examples in the GraphOS documentation</a>.</p>


New GraphOS Platform APIs Enable Blue-Green and Canary Deployments


<p>Building a scalable and effective enterprise <a href="https://www.apollographql.com/blog/introducing-apollo-graphos">supergraph</a> is challenging, and often feels like there are countless numbers of ways to approach the challenges that arise without evidence of efficacy. Companies searching the GraphQL community for recommendations leads to&nbsp; a lack of consistency across the industry and doing things that may prove to be ineffective, thus requiring changes later down the line. These challenges can often be exacerbated by the lack of consensus both internally and externally, making it difficult to know what works best.</p>



<p>Apollo aims to simplify this process for both existing and new GraphQL practitioners and today we’re excited to share the <a href="https://saf.apollographql.com">Supergraph Architecture Framework (SAF)</a>, which is the culmination of years of learning by Apollo’s Solutions Architecture team after working with some of the largest enterprise organizations in the world as a way to answer questions about how to best enable your organization to scale GraphQL effectively.</p>



<h2 class="wp-block-heading"><a href="#what-is-the-saf" aria-hidden="true" class="aal_anchor" id="what-is-the-saf"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What is the SAF?</h2>



<p>The SAF explains key concepts, design principles, and architectural best practices for running a supergraph in production. The five SAF pillars provide an ideal foundation for a supergraph, ensuring your team can get up and running successfully in less time.&nbsp;</p>



<p>The SAF is a short assessment to help you and your organization better understand how to improve your supergraph, grouped into five pillars. These questions are based on best practices we’ve seen at other companies who have deployed a supergraph at enterprise scale.</p>



<p>The pillars are:&nbsp;</p>



<ul class="wp-block-list">
<li><strong>Operational Excellence</strong>: How you efficiently operate, maintain, and manage your supergraph. This pillar primarily focuses on the interpersonal skills and processes that are paramount to running a successful supergraph.</li>



<li><strong>Security</strong>: How you secure your organization’s supergraph to prevent misuse.&nbsp;</li>



<li><strong>Reliability</strong>: How you build and maintain a scalable supergraph with high availability in mind.</li>



<li><strong>Performance</strong>: How you can create a performant supergraph and ensure performance is monitored at your organization.</li>



<li><strong>Developer Efficiency</strong>: This discusses ways to increase your developer velocity through process improvements.&nbsp;</li>
</ul>



<p>Once completed, you’ll be able to get a report of how your organization is performing, alongside a list of action items and their associated impact and level of effort.</p>



<p>The SAF is intended to be run multiple times as your journey progresses, and can be helpful at any stage of the process; whether that be the beginning or midway through implementation, or reviewing an existing implementation to make changes.</p>



<h2 class="wp-block-heading"><a href="#how-do-i-get-started" aria-hidden="true" class="aal_anchor" id="how-do-i-get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How do I get started?</h2>



<p>To get started with the SAF, visit <a href="https://saf.apollographql.com">https://saf.apollographql.com</a>, log in with your Apollo Studio organization, and begin your assessment. Once you’ve started, you’ll be shown a list of questions and multiple choices to fill out, such as the questions below.&nbsp;</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1018" height="581" src="https://wp.apollographql.com/wp-content/uploads/2024/01/image-1.png" alt="" class="wp-image-23187" srcset="https://wp.apollographql.com/wp-content/uploads/2024/01/image-1.png 1018w, https://wp.apollographql.com/wp-content/uploads/2024/01/image-1-300x171.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/01/image-1-768x438.png 768w" sizes="auto, (max-width: 1018px) 100vw, 1018px" /></figure>



<p>Once finished, you’ll get a report, which can be exported as a PDF, that you can share with members of your organization:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="846" height="716" src="https://wp.apollographql.com/wp-content/uploads/2024/01/image.png" alt="" class="wp-image-23185" srcset="https://wp.apollographql.com/wp-content/uploads/2024/01/image.png 846w, https://wp.apollographql.com/wp-content/uploads/2024/01/image-300x254.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/01/image-768x650.png 768w" sizes="auto, (max-width: 846px) 100vw, 846px" /></figure>



<p>The SAF provides free guidelines to immediately improve your organization’s supergraph. Leverage Apollo’s experience, and ensure your work is backed by other companies’ learnings. </p>



<p><br>Visit the <a href="http://saf.apollographql.com">Supergraph Architecture Framework</a> site to get started. If you’re an enterprise customer, please reach out to your Apollo account team to review your results.</p>


The Apollo Supergraph Architecture Framework


<ul class="wp-block-list">
<li><em>GraphQL Leader Adds Executives from Atlassian and Twilio; Aditya Phadke Appointed Chief Customer Officer and Rob Brazier Named VP of Product</em></li>



<li><em>Unwavering GraphQL Adoption and Customer Focus Continue to Drive Major Product Enhancements at Apollo GraphQL&nbsp;</em></li>
</ul>



<p>Apollo GraphQL, the supergraph company, today announced it has made two significant additions to its leadership team, welcoming Aditya Phadke as Chief Customer Officer and Rob Brazier as VP of Product. These new appointments build on the successes felt in 2023, as GraphQL saw a rise in usage and success within API platform teams for globally recognized brands like <a href="https://www.youtube.com/watch?v=b78Q7qY4IpI&amp;list=PLpi1lPB6opQzUOqG3QroLLN06FF-Q_uhX&amp;index=7">Netflix</a>, <a href="https://www.youtube.com/watch?v=sNqcow1psEA&amp;list=PLpi1lPB6opQzUOqG3QroLLN06FF-Q_uhX&amp;index=24">Wayfair</a>, and <a href="https://www.youtube.com/watch?v=GB-THCI0Mw0&amp;list=PLpi1lPB6opQzUOqG3QroLLN06FF-Q_uhX&amp;index=36">Intuit</a>.</p>



<p>Phadke joins Apollo GraphQL from Atlassian, where he played a crucial role in unlocking customer success and building its pre-sales &amp; post-sales customer motions as it scaled from a startup to a public market leader worth $62B; he will be responsible for building the post-sales group fostering long-term customer relationships and evolving the customer adoption journey. Brazier most recently joins from Grammarly, where he led their developer platform efforts and, prior to that, was the VP of Product at Twilio, where he focused on Twilio Flex, Voice and Video, and other product lines for the company. He brings his background in platforms, developer-facing products and cloud, alongside experience with top-down and bottom-up sales motions, to further advance all aspects of the Apollo GraphQL product portfolio that is seeing significant adoption as the leader of GraphQL products in the market. Additionally, Robbie Petrie joined as Chief Financial Officer earlier in 2023 from Twilio to round out the leadership team.</p>



<figure class="wp-block-pullquote"><blockquote><p>“In 2024, brands are delivering personalized, AI-driven applications across multiple channels to keep up in today&#8217;s market. They’re finding that it’s hard to do this at the pace today’s world requires without a new approach to APIs. Rather than building handwritten experience APIs for each customer interface, enterprises are taking a platform approach with GraphQL so they can gain composability, developer velocity, and efficient integration of diverse cloud resources. And that’s why they’re turning to Apollo GraphQL as the creators of the industry standard GraphQL platform for the future,” said Geoff Schmidt, CEO and co-founder at Apollo GraphQL. “We are expanding our executive team to better service our customers and meet demands for their long-term growth and success. Aditya brings a track record of nurturing customer relationships and Rob brings years of developer platform success and expertise. Both make ideal additions to the Apollo GraphQL leadership team to help developers build the next generation of applications and deliver profound, efficient, and meaningful user experiences.”</p></blockquote></figure>



<p>Half of the Fortune 100 embraced GraphQL in 2023 and Apollo GraphQL experienced 40% growth in new customers. Significant customers include <a href="https://www.youtube.com/watch?v=CJRgtuSMV_Q">Ford Credit, Sony Playstation,</a> and <a href="https://www.youtube.com/watch?v=w07Z572q3kg&amp;list=PLpi1lPB6opQzUOqG3QroLLN06FF-Q_uhX&amp;index=2">Realtor.com</a>, who along with 40 others, talked about how Apollo GraphQL is helping their businesses at the GraphQL Summit in 2023. Apollo GraphQL provides an API integration layer across teams with its supergraph – a GraphQL layer that sits atop existing APIs and enables developers to fetch data from a single endpoint. By building a supergraph with the Apollo GraphOS platform instead of handwriting a sprawl of countless backends-for-frontends or experience APIs, software teams and platform engineers can focus less time on service aggregation or orchestration and more on the features that fuel growth. Apollo GraphQL’s product portfolio and services now include:&nbsp;</p>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/blog/federated-subscriptions-in-graphos-real-time-data-at-scale"><strong>Real-time data at scale with federated subscriptions in GraphOS</strong></a> &#8211; GraphOS has subscriptions which allow developers to deliver up-to-the-second updates to application experiences without writing new code, regardless of how many APIs they consume.</li>



<li><strong>Comprehensive platform approach to API Security</strong> &#8211; GraphOS allows platform teams to deliver velocity at scale without compromising security and compliance. GraphOS Authorization now centrally <a href="https://www.apollographql.com/blog/centrally-enforce-policy-as-code-for-graphql-apis">enforces policy as code for GraphQL APIs</a>. Enterprises can also eliminate unauthorized access to services with persisted queries, which provide <a href="https://www.apollographql.com/blog/graphos-persisted-queries-are-generally-available">a registered list of known queries</a> that can access the graph in production.&nbsp;</li>



<li><strong>API conformance and governance </strong>&#8211; As GraphQL gains traction among more and more developers, enterprise teams must provide tools to ensure code quality and consistency at all times. API platform owners can now automate and streamline code review with <a href="https://www.apollographql.com/blog/standardize-graphql-schema-linting-policies-with-graphos">schema linting in GraphOS</a>.</li>



<li><strong>Significant performance gains and capabilities with Apollo Router</strong> &#8211; Apollo Router, a high-performance GraphQL gateway and query planner, has successfully undergone rigorous testing for over a year in highly demanding production environments. The significant investments made in enhancing runtime performance and efficiency reflect Apollo’s commitment to delivering maximum cost savings and ensuring low-latency user experiences.</li>



<li><a href="https://www.apollographql.com/blog/announcing-official-apollo-federation-support-for-net-with-hot-chocolate-and-federation-2"><strong>Official Support for Microsoft .NET</strong></a><strong>:</strong> Apollo GraphQL recently furthered its commitment to the Microsoft ecosystem by announcing formal support for a .NET library, ensuring that over 6 million .NET developers can effectively contribute to a supergraph. Apollo GraphQL now supports 40+ GraphQL frameworks, enabling diverse teams to contribute to their API platforms.</li>
</ul>



<p>Apollo GraphQL has received recognition by third-party research firms and saw significant growth in its vibrant community:</p>



<ul class="wp-block-list">
<li>Apollo GraphQL was named a GraphQL API Sample Vendor for 3 consecutive years in the <a href="https://www.gartner.com/en/documents/4564799">Gartner® Hype Cycle™ for APIs, 2023</a>.<sup>1 </sup>Additionally, a Gartner survey found that “API design and API management skills” were rated one of the most highly important software engineering skill, second only to application security skills.<sup>2</sup></li>



<li>Apollo GraphQL’s developer adoption continues to grow with 25M open-source downloads per month and 5T requests served in GraphOS. Additionally, GraphQL is on the rise as an emerging skill with 4K new jobs posted on LinkedIn.com requiring it, 21k users completing courses on Apollo GraphQL’s <a href="https://apollographql.com/tutorials">learning platform Odyssey</a>, and 4k users earning certifications as an Apollo GraphQL Developer.</li>



<li>Apollo GraphQL was named one of <a href="https://www.fastcompany.com/90847317/most-innovative-companies-enterprise-2023">Fast Company’s Most Innovative Companies in Enterprise of 2023</a>.</li>
</ul>



<p>To learn more, visit <a href="http://www.apollographql.com">www.ApolloGraphQL.com</a> and the below resources.</p>



<p><strong>Further Resources:</strong></p>



<ul class="wp-block-list">
<li><a href="https://www.apollographql.com/supergraph/">Learn</a> more about supergraphs</li>



<li><a href="https://www.apollographql.com/graphos/">Build </a>a GraphQL API platform today</li>



<li><a href="https://www.apollographql.com/tutorials/certifications/apollo-graph-professional/learning-path/">Become certified </a>as an Apollo GraphQL developer</li>



<li><a href="https://discord.com/invite/yFZJH2QYrK">Join</a> the Apollo GraphQL Community on Discord</li>
</ul>



<p><sup>1 </sup>Gartner, <a href="https://www.gartner.com/en/documents/4564799">Hype Cycle for APIs</a>, 2023, By Mark O&#8217;Neill, John Santoro, July 25, 2023. Gartner and Hype Cycle are registered trademarks of Gartner, Inc. and/or its affiliates in the U.S. and internationally and are used herein with permission. All rights reserved. Note: Apollo GraphQL was referred to as Apollo in the 2022 and 2021 Gartner Hype Cycle for APIs and was recognized for Graph APIs.</p>



<p><sup>2 </sup>Gartner, <a href="https://www.gartner.com/en/documents/4539999">Top Software Engineering Skills and Skill-Building Techniques</a>, By Shivica Mathur, July 18, 2023.</p>



<p><em>Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.</em></p>



<p><strong>About Apollo GraphQL</strong></p>



<p><a href="https://apollographql.com">Apollo GraphQL </a>helps developers help the world by providing a better API platform across teams. Apollo’s open-source software is downloaded 25M times per month and its commercial GraphQL technologies power the most innovative brands today. Teams at Netflix, Snap, and the New York Times ship personalized, omnichannel experiences faster with a supergraph – a self-service GraphQL platform that spans any number of backend services. Serving over 5T requests in 2023, the Apollo GraphOS platform simplifies API development with workflows and infrastructure to build, test, and ship supergraphs at any scale. Based in San Francisco, Apollo is backed by Insight Partners, Andreessen Horowitz, Matrix Partners, and Trinity Ventures. Learn more at: <a href="https://www.apollographql.com">https://www.apollographql.com</a>.</p>


This image displays a headshot of Aditya Phadke and a headshot of Rob Brazier, new executives on the Apollo GraphQL team. Consistent with the visual image, the text displayed says "Welcome to Apollo GraphQL!"

Apollo GraphQL Expands Leadership Team To Meet Demand for GraphQL in the Enterprise


<p>Although many in the industry consider GraphQL a replacement for existing API technologies, it is at its most powerful when used as a central orchestration layer between apps and existing services. This layer, implemented as a federated graph (or <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">supergraph</a>, for short), acts as a self-service API platform that accelerates development velocity for both frontend and backend teams. However, speed of delivery can’t come at the expense of a strong authorization model that protects personal identifiable information, financial data, and other sensitive information.</p>



<p><a href="https://www.apollographql.com/graphos">Apollo GraphOS</a> provides GraphQL-native workflows to implement access control declaratively across an entire supergraph. Rather than relying only on distributed enforcement or fragile custom gateway logic to secure the graph, teams using GraphOS can enforce policies at the type or field level in their router by decorating schemas with the <code>@requiresScopes</code>, <code>@authenticated</code>, and new <code>@policy</code> directives. These directives provide the freedom to integrate with any authorization system, including policy engines like <a href="https://casbin.org/">Casbin</a> or <a href="https://www.openpolicyagent.org/">Open Policy Agent</a> (OPA). By proactively enforcing policies as code, API platform teams can ensure compliance at all times without sacrificing developer velocity.</p>



<p>These directives are generally available for all GraphOS Enterprise customers starting today.</p>



<h2 class="wp-block-heading"><a href="#durable-auditable-authorization-for-supergraphs" aria-hidden="true" class="aal_anchor" id="durable-auditable-authorization-for-supergraphs"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Durable, auditable authorization for supergraphs</h2>



<p>Supergraphs expose a unified, versionless GraphQL endpoint for all connected services. While this offers a host of benefits for frontend development, it makes it tricky to centralize authorization with traditional API gateways designed to enforce policies at the endpoint level. These gateways are unaware of the shape of the supergraph, so policies need to be mapped to individual types and fields with custom logic that must be kept in lockstep coordination with any schema changes.</p>



<p>An authorization model that is instead integrated directly into a supergraph’s schema is far more durable and can still be centrally audited and enforced in the router. <code>@authenticated</code> and <code>@requiresScopes</code>, <a href="https://www.apollographql.com/blog/announcement/backend/build-centralized-graphql-authorization-with-apollo-graphos/">which we launched in preview</a> earlier this year, allow you to define access control policies for types and fields directly in the schema, restricting access to only authenticated requests or requests with certain scopes, respectively. Subgraph developers simply add the directives to the parts of the schema they want to enforce.</p>



<p>For example, let’s say you’re building a simple social media app. The app should allow unauthenticated users to view a post&#8217;s title, author, and content, but only authenticated users to see the number of views a post has received, and only certain users with required permissions to view email addresses. The relevant part of your schema may look something like this:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">type Query {
  me: User @authenticated 
  post(id: ID!): Post
}

type User {
  id: ID!
  username: String
  email: String @requiresScopes(scopes: [[&quot;read:email&quot;]])
  posts: [Post!]!
}

type Post {
  id: ID!
  author: User!
  title: String!
  content: String!
  views: Int @authenticated 
}</code></pre>



<p>However, many organizations may require more complex policy evaluation and often leverage external tools like OPA or Casbin. For these more complex scenarios, GraphOS now supports a third authorization directive: <code>@policy</code>.</p>



<h2 class="wp-block-heading"><a href="#offload-policy-definition-and-resolution-with-policy" aria-hidden="true" class="aal_anchor" id="offload-policy-definition-and-resolution-with-policy"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Offload policy definition and resolution with @policy</h2>



<p>The new <code>@policy</code> directive allows you to integrate your predefined policies from policy engines like OPA and Casbin into your supergraph schema and enforce them in your router. For example, let’s say in your example social media app, you only want users to have access to their own personal information and credit card information. Validating this requires more than the scopes of an access token, so you can use <code>@policy</code> to offload policy resolution for the relevant parts of your schema:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">type Query {
  me: User @authenticated @policy(policies: [[&quot;read_profile&quot;]])
  post(id: ID!): Post
}

type User {
  id: ID!
  username: String
  email: String @requiresScopes(scopes: [[&quot;read:email&quot;]])
  posts: [Post!]!
  credit_card: String @policy(policies: [[&quot;read_credit_card&quot;]])
}

type Post {
  id: ID!
  author: User!
  title: String!
  content: String!
  views: Int @authenticated
}</code></pre>



<p>The <code>@policy</code> directive allows you to use your supergraph as a central enforcement point for any services you’ve connected to your graph without refactoring the authorization model that you’ve already defined.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="800" src="https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram.png" alt="" class="wp-image-23033" srcset="https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram.png 1600w, https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/12/external-policy-diagram-1200x600.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<p><code>@policy</code> loosely couples policy enforcement in your GraphOS router and the policy definition in your existing policy engine, giving you the flexibility to evolve how your application resolves policies without altering your GraphQL schema or infrastructure. For example, if your application needs to perform complex authorization validation, such as inspecting specific values in headers, <code>@policy</code> can be used to validate in a coprocessor or Rhai script.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p>Schema-driven authorization with <code>@authenticated</code>, <code>@requiresScopes</code>, and <code>@policy</code> is generally available for all GraphOS Enterprise customers today. To start centralizing authorization enforcement with GraphOS, head over to the <a href="https://www.apollographql.com/docs/router/configuration/authorization">Authorization in the Apollo Router documentation</a>.</p>



<p>If you’re new to GraphOS, you can <a href="https://studio.apollographql.com/signup?type=enterprise-trial&amp;_gl=1*1czaoty*_ga*NjU4MjMwOTQ0LjE2MzIxNTUyNDc.*_ga_0BGG5V2W2K*MTcwMTk3NjAwMy4xMDU4LjEuMTcwMTk3NjEwNy4wLjAuMA..">try out GraphOS Enterprise</a> free for 28 days.</p>


Centrally enforce policy as code for GraphQL APIs


<p>As <a href="https://www.youtube.com/watch?v=CJRgtuSMV_Q">API platform teams continue to back Apollo Federation</a> as the standard for GraphQL architecture at scale, graphs have rapidly become more sophisticated — expanding across innumerable teams, services, clients, and business units. As sophistication increases, so too does the need for powerful and user-friendly observability, tailored to the needs of graph owners. </p>



<p>Today, Apollo is excited to release a new and improved insights dashboard in GraphOS Studio to provide scalable observability tools to API owners operating a supergraph.</p>



<p>Within the new insights dashboard you’ll find:</p>



<ul class="wp-block-list">
<li>A consolidated and streamlined experience for accessing operation and field insights</li>



<li>Fast and intuitive search for quickly finding a specific field or operation</li>



<li>Filterable field and operation lists</li>



<li>Significant improvements to list load times for large graphs</li>
</ul>



<p>And much more!</p>



<figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex">
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="642" data-id="22859" src="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new-1024x642.png" alt="" class="wp-image-22859" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new-1024x642.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new-300x188.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new-768x481.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new-1200x752.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-main-new.png 1493w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="642" data-id="22861" src="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new-1024x642.png" alt="" class="wp-image-22861" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new-1024x642.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new-300x188.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new-768x481.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new-1200x752.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-search-new.png 1493w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="642" data-id="22863" src="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new-1024x642.png" alt="" class="wp-image-22863" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new-1024x642.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new-300x188.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new-768x481.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new-1200x752.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/insights-filter-new.png 1493w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>
</figure>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p>The new insights experience is available today for all GraphOS users. To get started, <a href="https://www.apollographql.com/signin">sign into GraphOS Studio</a> and navigate to Insights in the left navigation.</p>



<p>Happy querying!</p>


New GraphQL observability and insights in GraphOS Studio


<p>Apollo Federation is an open specification for exposing API services as a single GraphQL access layer, known as a supergraph. In a supergraph, you connect and curate your services through smaller, modular graphs called subgraphs. There’s a vibrant ecosystem of community-led frameworks that let you write subgraphs in <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs">every common language</a>, bolstered by official Apollo Federation support libraries for JavaScript and Java. </p>



<p>Today, we’re excited to announce a new <a href="https://www.nuget.org/packages/ApolloGraphQL.HotChocolate.Federation">official Apollo Federation support library for Hot Chocolate</a> — a popular .NET GraphQL framework — including full <a href="https://www.apollographql.com/blog/announcement/backend/announcing-federation-2/">Federation 2</a> support for field migrations, entity interfaces, and more flexible type ownership!</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="753" src="https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-1024x753.png" alt="" class="wp-image-22807" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-1024x753.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-300x221.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-768x565.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-1536x1130.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs-1200x883.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/dotnet-subgraphs.png 1728w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#a-growing-ecosystem-of-frameworks" aria-hidden="true" class="aal_anchor" id="a-growing-ecosystem-of-frameworks"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>A growing ecosystem of frameworks</h2>



<p>With the help of Apollo&#8217;s official Federation support libraries, the community has added Federation support to over <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs">30+ GraphQL frameworks</a> that you can use to build subgraphs today.</p>



<p>The Apollo-maintained <code>subgraph-js</code> library <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs/#javascript--typescript">enables Federation in JavaScript/TypeScript subgraphs</a>:</p>



<ul class="wp-block-list">
<li>Adds Federation support to Apollo Server, Express GraphQL, NestJS, Yoga, and more.</li>



<li>Builds on top of the core <code>graphql-js</code> library, to enable the entire JavaScript ecosystem.</li>



<li>Apollo helps actively maintain <code>graphql-js</code> as a key reference implementation across language ecosystems.</li>
</ul>



<p>The Apollo-maintained <code>federation-jvm</code> library <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs/#java--kotlin">powers Federation in Java/Kotlin subgraphs</a>:</p>



<ul class="wp-block-list">
<li>Adds Federation support to Spring GraphQL, Netflix’s DGS Framework, and more.</li>



<li>Builds on top of the core <code>graphql-java</code> library to enable the whole Java ecosystem.</li>
</ul>



<h3 class="wp-block-heading"><a href="#expanding-official-support-to-net" aria-hidden="true" class="aal_anchor" id="expanding-official-support-to-net"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Expanding official support to .NET</h3>



<p>With momentum building in the .NET community, more and more subgraphs are being created using community support for Federation in popular GraphQL packages like GraphQL .NET and Hot Chocolate. To better support the growing number of .NET subgraphs, we&#8217;re excited to announce official Apollo support for .NET with a new v1.0 <a href="https://www.nuget.org/packages/ApolloGraphQL.HotChocolate.Federation">Apollo Federation support library for Hot Chocolate</a>. It’s an open source library that adds Federation support to the main Hot Chocolate GraphQL server and is based on the previous community-led implementation for backwards compatibility. We’ve fixed a few things, overhauled the docs, and added support for Federation 2!</p>



<p>Official <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs/#c--net">compatibility testing for C# / .NET</a> shows comprehensive Federation 2 support for Hot Chocolate:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="779" src="https://wp.apollographql.com/wp-content/uploads/2023/10/image-15-1024x779.png" alt="" class="wp-image-22809" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/image-15-1024x779.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/image-15-300x228.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/image-15-768x584.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/image-15-1200x913.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/image-15.png 1422w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#quick-start-template-for-hot-chocolate-subgraphs" aria-hidden="true" class="aal_anchor" id="quick-start-template-for-hot-chocolate-subgraphs"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Quick start template for Hot Chocolate subgraphs</h2>



<p>The <a href="https://www.apollographql.com/docs/rover/commands/template">Rover CLI</a> now supports .NET and a new <a href="https://github.com/apollographql/subgraph-csharp-hotchocolate-annotation">Hot Chocolate subgraph template</a> that includes:</p>



<ul class="wp-block-list">
<li>Annotation-based Federation for clean idiomatic C# code.</li>



<li>GitHub actions configured for CI/CD using GraphOS schema checks and publishing.</li>



<li>Railway one click deploy template.</li>
</ul>



<p>To bootstrap a new Hot Chocolate subgraph project, run:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash">rover template use --template subgraph-csharp-hotchocolate-annotation</code></pre>



<p>Federation 2 is configured into your Hot Chocolate subgraph in <code>Program.cs</code></p>



<pre class="wp-block-prismatic-blocks"><code class="language-csharp">using ApolloGraphQL.HotChocolate.Federation;

var builder = WebApplication.CreateBuilder(args);

builder.Services
    .AddGraphQLServer()
    .AddApolloFederationV2() 
    // register your types and services
    ;

var app = builder.Build();
app.MapGraphQL();
app.Run();</code></pre>



<p>Root query fields for your subgraph are defined in <code>Query.cs</code>, which federate into your supergraph for apps to use:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-csharp">public class Query
{
    public Thing? Thing([ID] string id, Data repository)
        =&gt; repository.Things.FirstOrDefault(t =&gt; t.Id.Equals(id));
}</code></pre>



<p>Entity classes like <code>Thing.cs</code> define a <code>Key</code> , <code>ID</code>, and <code>Reference Resolver</code> to enable joining data across subgraphs:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-csharp">[Key(&quot;id&quot;)]
public class Thing
{
    [ID]
    public string Id { get; }

    public string? Name { get; }

    [ReferenceResolver]
    public static Thing? GetThingById(
        string id,
        Data repository)
        =&gt; repository.Things.FirstOrDefault(t =&gt; t.Id.Equals(id));
}</code></pre>



<h2 class="wp-block-heading"><a href="#upgrade-an-existing-hot-chocolate-subgraph-to-federation-2" aria-hidden="true" class="aal_anchor" id="upgrade-an-existing-hot-chocolate-subgraph-to-federation-2"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Upgrade an existing Hot Chocolate subgraph to Federation 2</h2>



<p>Update your <code>.csproj</code> file:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-markup">  &lt;ItemGroup&gt;
    &lt;PackageReference Include=&quot;HotChocolate.AspNetCore&quot; Version=&quot;13.5.1&quot; /&gt;
    &lt;PackageReference Include=&quot;ApolloGraphQL.HotChocolate.Federation&quot; Version=&quot;1.0.0&quot; /&gt;
  &lt;/ItemGroup&gt;</code></pre>



<p>Use the new official Apollo Federation support library and configure your subgraph to use Federation 2:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-csharp">using ApolloGraphQL.HotChocolate.Federation;

var builder = WebApplication.CreateBuilder(args);

builder.Services
    .AddGraphQLServer()
    .AddApolloFederationV2() 
    // ...
    ;

var app = builder.Build();
app.MapGraphQL();
app.Run();</code></pre>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What&#8217;s next?</h2>



<p>Starting today, Apollo will continue to maintain official Federation subgraph support for Hot Chocolate. You can expect ongoing improvements and fixes, as well as full support for the latest Apollo Federation spec changes.</p>



<p>We also plan to work with the community to add <a href="https://www.apollographql.com/docs/federation/building-supergraphs/supported-subgraphs/#c--net">Federation 2 support for other popular .NET packages like GraphQL .NET</a>.</p>



<h2 class="wp-block-heading"><a href="#learn-more" aria-hidden="true" class="aal_anchor" id="learn-more"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Learn more</h2>



<ul class="wp-block-list">
<li>Checkout the <a href="https://www.nuget.org/packages/ApolloGraphQL.HotChocolate.Federation">updated docs</a> to learn more!</li>



<li>If you have a specific question about the library or code, please start a discussion in the <a href="https://community.apollographql.com/">Apollo community forums</a> or start a conversation on our <a href="https://discord.gg/graphos">Discord server</a>.</li>



<li>If you have improvements you’d like to see please let us know by <a href="https://github.com/apollographql/federation-hotchocolate/issues/new">opening a GitHub issue</a>!</li>
</ul>


Announcing official Apollo Federation support for .NET with Hot Chocolate and Federation 2!


<p>Unbounded operations are generally considered a benefit of GraphQL, giving client developers unprecedented flexibility when experimenting and developing apps. However, while this flexibility is greatly appreciated in development environments, allowing it in production adds unnecessary surface area to GraphQL endpoints which generally serve only first-party clients.</p>



<p>Instead, your production graph should adhere to the principle of least privilege. If your first-party apps only require <code>QueryA</code>, <code>QueryB</code>, and <code>QueryC</code> to operate properly, your graph should only allow <code>QueryA</code>, <code>QueryB</code>, and <code>QueryC</code>. Any tolerance for ad hoc operations creates unnecessary exposure.</p>



<p>If you have a GraphQL monolith serving just a few clients, building a custom safelisting system to enforce this behavior is relatively straightforward. However, as the graph scales to serve dozens of clients and takes on a supergraph architecture, the complexity of maintaining such a system becomes prohibitive.</p>



<p>Apollo now offers a scalable solution for mitigating the risks of unbounded operations in supergraphs: <strong>GraphOS Persisted Queries</strong>. Persisted queries enable your platform team to limit the attack surface area of your supergraph by centrally registering trusted GraphQL operations and safelisting them in any instance of the Apollo Router.</p>



<h2 class="wp-block-heading"><a href="#a-graphql-platform-approach-to-api-security" aria-hidden="true" class="aal_anchor" id="a-graphql-platform-approach-to-api-security"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>A GraphQL platform approach to API security</h2>



<p>A supergraph is a self-service API platform designed to empower frontend and backend teams to consume and build services independently, but equally important is its ability to systematically centralize access control policy enforcement. By choosing to leverage the supergraph for policy enforcement, API platform teams can protect any number of backend services with layers of access control without heavy-handed manual review.</p>



<p>GraphOS Persisted Queries is one such layer that centralizes policies defining which <em>operations</em> should be allowed access to the supergraph. Rather than relying on platform teams to create and maintain this policy manually, GraphOS provides a workflow for <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries#implementation-steps">discovering and registering known operations</a> that can be integrated directly into client CI/CD pipelines.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="444" src="https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-1024x444.png" alt="" class="wp-image-22725" srcset="https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-1024x444.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-300x130.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-768x333.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-1536x667.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-2048x889.png 2048w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-1200x521.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/10/Screenshot-2023-10-11-at-2.49.57-PM-1980x859.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#flexibility-in-development-discretion-in-production" aria-hidden="true" class="aal_anchor" id="flexibility-in-development-discretion-in-production"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Flexibility in development, discretion in production</h2>



<p>In most cases, your production API only needs to execute a finite number of GraphQL operations from a set pool of stable, first-party applications. In this environment, safelisting limits the exposure of your graph by blocking any unknown operations.&nbsp;</p>



<p>However, in development environments, it’s important to allow developers the flexibility to experiment with unbounded operations. To do so, you can configure your router to simply <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries#security-levels">log any unregistered operations</a> rather than block them. This is also useful when you’re getting started with Persisted Queries, and you haven’t yet registered all known operations from existing clients. However, it can be useful to pair this mode with some <a href="https://www.apollographql.com/docs/router/configuration/operation-limits/">operation limits</a> that prevent any intentional or unintentional misuse of the graph.</p>



<h2 class="wp-block-heading"><a href="#expanding-security-options-for-your-graphql-platform" aria-hidden="true" class="aal_anchor" id="expanding-security-options-for-your-graphql-platform"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Expanding security options for your GraphQL platform</h2>



<p>GraphOS Persisted Queries are one of the many ways you can <a href="https://www.apollographql.com/blog/graphql/security/enforcing-graphql-security-best-practices-with-graphos/">use GraphOS to improve the security posture of your GraphQL platform</a>. Persisted Queries are generally available for GraphOS Enterprise today and coming soon for GraphOS Cloud. To get started, head over to the <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries/">GraphOS documentation</a>.</p>



<p>For platform teams looking to further leverage their supergraph to improve API security, stay tuned for additional GraphOS security features and look out for more GraphQL security content at <a href="https://summit.graphql.com/event/c51538f6-4b76-44e3-871e-54180c77cad8/summary">GraphQL Summit</a>.</p>


GraphOS Persisted Queries are generally available


<p><em>An Integrated Blueprint from Kong and Apollo</em> </p>



<p>Not a day goes by where the tech press fails to mention industry advancements in AI, connected devices, or personalization. Consumers can now use AI to create anything from digital illustrations to vacation ideas. At the core of these initiatives is one tried-and-true constant – APIs. If an organization cannot safely and securely deliver service updates across any number of interfaces, these modernization initiatives will fail to gain traction.</p>



<p>APIs are more heterogeneous than ever though. An enterprise considering incorporating gRPC APIs may still have legacy SOAP APIs in the mix. A new feature could require data from 20 different services – all of which are managed by different teams at different cadences using varying protocols. If a Product Manager wants to incorporate data from legacy APIs as well as new options like ChatGPT, how can API platform teams provide a standardized means to iterate, secure access, and scale all of them? And then how do they ensure that client teams can get the data they need in a self-service fashion?</p>



<p>Kong and Apollo are industry leaders in the API space. Our customers come to us with these very real problems everyday. The API ecosystem often positions REST and GraphQL as competing technologies, but they are highly complementary and are instrumental in developing a modern API platform that accomplishes the goals above. Through a balanced exploration of Kong&#8217;s perspective on flexible, heterogeneous API ecosystems and Apollo&#8217;s expertise in GraphQL, we’ve captured the vendor-neutral best practices that combine API management and GraphQL into a unified reference architecture for building and operating a modern API platform.</p>



<p>Learn more with our joint <a href="https://new.apollographql.com/leveraging-graphql-for-next-generation-api-platforms.pdf">paper and reference architecture</a> that shows how to:</p>



<ol class="wp-block-list">
<li>Leverage GraphQL and a supergraph as a new layer in the stack atop existing microservices and API management.</li>



<li>Streamline the developer experience in building and consuming APIs.</li>



<li>Ensure secure, efficient runtime connectivity and implement robust governance mechanisms with API management best practices.</li>
</ol>



<p> </p>


Leveraging GraphQL for Next-Generation API Platforms


<p><em>December 2023 update: GraphOS authorization enforcement is <strong>now generally available</strong>, including the <code>@requiresScopes</code>, <code>@authenticated</code>, and <strong>new</strong> <code>@policy</code> directives. <a href="https://www.apollographql.com/blog/announcement/backend/centrally-enforce-policy-as-code-for-graphql-apis/">Read the GA announcement</a>.</em></p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p>Implementing a durable access control system for APIs is critical to prevent data breaches, monetary losses, and potential denial of services. GraphQL presents API owners with a unique challenge in this regard because it is designed for maximum flexibility.</p>



<p>In general, there are two choices for enforcing access control for GraphQL APIs, neither of which scale particularly well. You can write custom logic to centralize enforcement — which must be kept in lock-step coordination with changes to the graph — or you can distribute enforcement across multiple GraphQL endpoints — eliminating much of the flexibility GraphQL provides to app developers.</p>



<p>Apollo GraphOS and <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">supergraph architecture</a> are eliminating this trade-off. Starting today, graph owners can enforce centralized authorization across any number of connected services in the graph.</p>



<p><a href="https://www.apollographql.com/docs/router/configuration/authorization/">Authz enforcement</a> is available<strong> in preview today</strong> for all customers on the GraphOS Enterprise plan running self-hosted instances of Apollo Router.</p>



<h2 class="wp-block-heading"><a href="#durable-graph-native-authz" aria-hidden="true" class="aal_anchor" id="durable-graph-native-authz"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Durable, graph-native authz</h2>



<p>When you operate a supergraph with GraphOS, you can now use the <code>@requiresScopes</code> and <code>@authenticated</code> <a href="https://www.apollographql.com/docs/router/configuration/authorization/#authorization-directives">directives</a> to define the authorization model for individual types and fields in each of your services declaratively. Rather than relying on custom logic or per-service access control, GraphOS uses these directives to compose a single federated authorization model. It then enforces that model in your <a href="https://www.apollographql.com/docs/router/">graph router</a> at the edge of the API stack to optimize query execution and improve defense-in-depth.</p>



<h3 class="wp-block-heading"><a href="#limit-access-to-certain-scopes" aria-hidden="true" class="aal_anchor" id="limit-access-to-certain-scopes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Limit access to certain scopes</h3>



<p>The <strong><code>@requiresScopes</code> </strong>directive is useful in cases where certain data or experiences should be available to a subset of users, but not all. It allows you to define granular access control by specifying an array of scopes that are required to access the type or field. If GraphOS receives a request that is missing the required scopes for certain fields, it will automatically filter out those fields before executing the operation. [<a href="https://www.apollographql.com/docs/router/configuration/authorization/#example-requiresscopes-use-case">Example use case</a>]&nbsp;</p>



<h3 class="wp-block-heading"><a href="#require-authentication" aria-hidden="true" class="aal_anchor" id="require-authentication"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Require authentication</h3>



<p>The <strong><code>@authenticated</code></strong> directive is useful when you need to limit access to unauthenticated users (or when you want to cut off unauthenticated access entirely). It provides binary access control, limiting marked types and fields to authenticated requests. When GraphOS receives an unauthenticated request, it filters out all fields marked with <code>@authenticated</code> before execution. [<a href="https://www.apollographql.com/docs/router/configuration/authorization/#example-authenticated-use-case">Example use case</a>]</p>



<h2 class="wp-block-heading"><a href="#optimize-query-execution" aria-hidden="true" class="aal_anchor" id="optimize-query-execution"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Optimize query execution</h2>



<p>The best way to combat DoS attacks is to enforce access control well before traffic ever reaches your mission-critical services. With an access control model defined in your schema, the GraphOS runtime plane acts as a central control point that does just that. In the simplest case, GraphOS will immediately terminate requests lacking the proper authorization to access any fields, preventing them from ever reaching your services. However, GraphOS can also optimize the execution of partially authenticated requests and deduplicate requests to your services.</p>



<h3 class="wp-block-heading"><a href="#eliminate-unauthorized-subqueries" aria-hidden="true" class="aal_anchor" id="eliminate-unauthorized-subqueries"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Eliminate unauthorized subqueries</h3>



<p>Let’s say we’re building the profile page for a social media app that shows profile information like a name and profile image to all users, but only shows the posts associated with the profile to authenticated users. We have one service in our federated graph that handles user information — the Users API — and another that handles post information — the Posts API. We can restrict access to data resolved by the Posts API to authenticated users with <code>@authenticated</code>.</p>



<p>Now, when GraphOS receives the query used to populate the profile page, it will first check if the user has the proper claims to access fields resolved by the Posts API. Here’s the fun part – if the request doesn’t have the proper claims, GraphOS will eliminate the entire subquery to the Posts API, preventing that service from ever seeing the traffic.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="512" src="https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-1024x512.png" alt="" class="wp-image-22526" srcset="https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1-1200x600.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/09/GraphOS-Authorization-subquery-optimization-1.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#deduplicate-subqueries" aria-hidden="true" class="aal_anchor" id="deduplicate-subqueries"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Deduplicate subqueries</h3>



<p>GraphOS also reduces load on your services by accounting for authorization when <a href="https://www.apollographql.com/docs/router/configuration/traffic-shaping/#query-deduplication"><em>deduplicating</em> simultaneous subqueries</a>. If your router is simultaneously processing two or more requests that after authz enforcement require identical subqueries, GraphOS will fulfill both requests using a single subquery.</p>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started</h2>



<p>Implementing centralized GraphQL authorization with GraphOS eliminates the need for maintaining custom gateway code or bespoke authorization models for every one of your services. On top of that, it optimizes the performance of your services by eliminating unnecessary load from unauthorized requests.</p>



<p>Starting today, all customers on the GraphOS Enterprise plan can start using <code>@requiresScopes</code> and <code>@authenticated</code> to enforce declarative, graph-native authorization in the GraphOS runtime plane. To get started, head over to the <a href="https://www.apollographql.com/docs/router/configuration/authorization/">GraphOS documentation</a>.</p>



<p>If you aren&#8217;t a GraphOS Enterprise customer and you want to start building authz enforcement with GraphOS, you can <a href="https://studio.apollographql.com/signup?type=enterprise-trial" data-type="link" data-id="https://studio.apollographql.com/signup?type=enterprise-trial&amp;_gl=1*7g1bty*_ga*NjU4MjMwOTQ0LjE2MzIxNTUyNDc.*_ga_0BGG5V2W2K*MTY5MzkyOTcyOC45NjcuMS4xNjkzOTM1MTEzLjAuMC4w">try it out for free</a> for 28 days.</p>


Build centralized GraphQL authorization with Apollo GraphOS


<p>When you’re building a federated GraphQL API that spans multiple backend teams and services, it can be difficult to ensure that the schema for your graph stays consistent from subgraph to subgraph. For example, how do you ensure that a type defined as an entity in one subgraph is also defined as an entity in all other subgraphs?</p>



<p>Today, we’re making it easier for API platform teams to enforce schema consistency across multiple subgraphs by adding composition rules to the <a href="https://www.apollographql.com/blog/announcement/platform/standardize-graphql-schema-linting-policies-with-graphos/">Apollo GraphOS linter</a>. Now, you can configure the GraphOS checks workflow to flag inconsistent elements across subgraphs, overridden or unused elements, and issues with Federation directives.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="658" src="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-1024x658.png" alt="" class="wp-image-22422" srcset="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-1024x658.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-300x193.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-768x493.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-1536x987.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM-1200x771.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.29.38-PM.png 1650w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#configure-composition-rule-severity" aria-hidden="true" class="aal_anchor" id="configure-composition-rule-severity"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Configure composition rule severity</h2>



<p>Like other linter rules in GraphOS, you can enable or disable each composition rule independently and set its severity to <code>Warn</code> or <code>Error</code>. Violations of rules set to <code>Error</code> will cause the checks workflow to fail outright (useful for changes pushed to production graphs) while <code>Warn</code> violations will allow the checks workflow to pass but output a warning.</p>



<figure class="wp-block-image size-large is-style-default"><img loading="lazy" decoding="async" width="1024" height="543" src="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM-1024x543.png" alt="" class="wp-image-22425" srcset="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM-1024x543.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM-300x159.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM-768x407.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM-1200x636.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-23-at-5.30.44-PM.png 1400w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#integrate-with-development-workflows" aria-hidden="true" class="aal_anchor" id="integrate-with-development-workflows"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Integrate with development workflows</h2>



<p>Composition rules are enforced by GraphOS linter checks, which you can integrate into your existing delivery processes:</p>



<ol class="wp-block-list">
<li><strong>CI/CD pipelines</strong> — Centrally enforce composition rules in your existing CI/CD pipelines by <a href="https://www.apollographql.com/docs/rover/ci-cd/">installing Rover in your CI/CD environment</a>.&nbsp;</li>



<li><strong>The GraphOS registry</strong> — Enforce composition rules for all schema changes pushed to the GraphOS registry — the final checkpoint before your schema is used in production.</li>
</ol>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p>Composition rules for the GraphOS schema linter are available starting today for all GraphOS users. To get started, head to the Checks Configuration page for your graph in GraphOS Studio or <a href="https://www.apollographql.com/docs/graphos/delivery/linter-rules/#composition-rules">read the docs</a> for a step-by-step setup guide.</p>


Enforce schema consistency across federated graphs with GraphOS


<p>Last year, we announced the End-of-Life for Apollo Server 3, originally scheduled for October 22, 2023. Apollo Server has widespread adoption, and we&#8217;ve heard feedback that some in the community would appreciate more time for the migration process. In light of this, <strong>we&#8217;re extending the End-of-Life date for Apollo Server 3 to October 22, 2024</strong>. Apollo will continue to provide security patches and fixes for major regressions until October 2024, after which Apollo Server 3 will no longer be maintained by Apollo. </p>



<p>To learn how to migrate to Apollo Server 4, see the <a href="https://www.apollographql.com/docs/apollo-server/migration/">migration guide</a>. Additionally, you can find more information about End-of-Life stages in the <a href="https://www.apollographql.com/docs/resources/product-launch-stages/#end-of-life">Apollo Launch Stages definitions</a>.</p>



<p>At Apollo, our priorities have always been driven by the community and businesses that rely on us. We value your input and encourage you to keep sharing it with us. If you haven&#8217;t already, join the official <a href="https://discord.gg/graphos">Apollo GraphQL Discord</a> to keep the conversation going.</p>


Apollo Server 3 end-of-life extension


<p>GraphQL is designed to offer a more flexible, self-serve developer experience, but its open-ended approach often raises questions about its security model. The most common objection is that GraphQL APIs allow unbounded operations — a trait that can degrade performance or result in denial-of-service if too many complex queries are sent to the endpoint. A <a href="https://www.apollographql.com/blog/the-supergraph-a-new-way-to-think-about-graphql/">supergraph architecture</a> can compound this risk since it generally composes many services across an organization, significantly increasing the potential complexity of executing queries.</p>



<p>In order to deliver performance and security at all times, API platform teams should have the means to eliminate exposure to the potential performance impacts of excessively complex queries. In the spirit of a true platform, teams should be able to <strong>proactively define safelisted queries upfront in a way that encourages iteration in development but provides mission-critical security in production</strong><em>.&nbsp;</em></p>



<h2 class="wp-block-heading"><a href="#proactively-safelist-with-graphos" aria-hidden="true" class="aal_anchor" id="proactively-safelist-with-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Proactively safelist with GraphOS</h2>



<p>Today, Apollo is introducing a new approach for preventing unbounded access to GraphQL APIs: <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries"><strong>GraphOS persisted query safelisting</strong></a>. With persisted query safelisting, API teams can prevent service degradation from complex queries by centrally safelisting known operations in <a href="https://www.apollographql.com/docs/router/">Apollo Router</a> — Apollo’s blazing-fast GraphQL gateway and query planner.&nbsp;</p>



<p>GraphOS offers varying levels of safelist restrictions that enable incremental adoption and flexibility in development environments without sacrificing security in production. The <em>audit-only</em> configuration gives teams a frictionless way to get started with safelisting by logging unknown operation shapes without terminating the request. Meanwhile, production environments demanding maximum security and performance can use an <em>ID-only</em> configuration to accept only requests with a known hash, terminating all others.</p>



<p>Persisted query safelisting is available in preview today for Apollo customers on the GraphOS Enterprise plan – read the docs and try it out! We would love to hear your thoughts and learn how we can make safelisting work better for your use case. Over the coming weeks, we’ll be using your feedback to polish up the user experience ahead of the GA release.&nbsp; <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries">Head to the docs</a> to get started or read on to learn more about how you can configure safelisting for your development lifecycle.</p>



<h2 class="wp-block-heading"><a href="#how-safelisting-works-in-graphos" aria-hidden="true" class="aal_anchor" id="how-safelisting-works-in-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How safelisting works in GraphOS</h2>



<p>Nearly all APIs are designed to serve a finite set of first-party client apps, and, by their very nature, GraphQL services are aware of the shape of data requested by those applications. In this closed development ecosystem, we have the tools to implement a GraphQL gateway that significantly limits surface area by <em>only</em> allowing known operations from our first-party apps.&nbsp;</p>



<h3 class="wp-block-heading"><a href="#register-operations-from-first-party-apps" aria-hidden="true" class="aal_anchor" id="register-operations-from-first-party-apps"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Register operations from first-party apps</h3>



<p>GraphOS gives client teams a self-serve experience for registering queries from their first-party apps to a central graph registry. Simply generate a persisted query manifest file for any app using Apollo Client (web, iOS, or Kotlin) and register it to a graph in GraphOS using the Rover CLI. The persisted query manifest includes a unique <em>persisted query ID</em> hash for each operation which can be used in place of the query string to improve app performance once persisted queries are configured in the router.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="572" src="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-1024x572.png" alt="" class="wp-image-22331" srcset="https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-1024x572.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-300x168.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-768x429.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-1536x858.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-2048x1144.png 2048w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-1200x670.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/08/Screenshot-2023-08-10-at-17.10.30-1980x1106.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#configure-safelisting-incrementally" aria-hidden="true" class="aal_anchor" id="configure-safelisting-incrementally"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Configure safelisting incrementally</h3>



<p>After client teams register known queries to a graph in GraphOS, API platform owners can enable persisted queries for connected instances of Apollo Router. Once enabled, the router pulls the list of persisted query strings and IDs from the graph registry and stores them in memory to be used for safelisting and ID-only operations.&nbsp;</p>



<p>Enforcing severe safelisting rules in the router is as simple as updating a few lines of router config, but to prevent any breaking changes in your apps, it is best to start with a flexible configuration and incrementally move to a more restrictive approach in production. In the remainder of this post, we’ll walk through the various ways you can adapt safelisting to your use case.</p>



<h2 class="wp-block-heading"><a href="#flexible-safelisting-for-every-stage-of-development" aria-hidden="true" class="aal_anchor" id="flexible-safelisting-for-every-stage-of-development"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Flexible safelisting for every stage of development</h2>



<p>Generally, you should configure your router to be more restrictive in production environments and less restrictive in development environments, but your particular use case and GraphQL client may limit how restrictive your router can be. GraphOS offers the ability to enforce more severe or less severe safelisting restrictions depending on your use case.&nbsp;</p>



<h3 class="wp-block-heading"><a href="#audit-only-for-agile-development-and-adoption" aria-hidden="true" class="aal_anchor" id="audit-only-for-agile-development-and-adoption"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Audit-only for agile development and adoption</h3>



<p>In development environments or when you’re just getting started with safelisting, it is generally best to simply log any unregistered operations without terminating them. The audit-only configuration provides this flexibility, helping you determine if any operations are missing from the registry in GraphOS. Here’s how you can configure your router for audit-only:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml"># router.yaml

preview_persisted_queries:
  enabled: true
  log_unknown: true</code></pre>



<h3 class="wp-block-heading"><a href="#lock-down-and-optimize-production-endpoints" aria-hidden="true" class="aal_anchor" id="lock-down-and-optimize-production-endpoints"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Lock down and optimize production endpoints</h3>



<p>When you’re confident that all supported operations are registered in GraphOS, you can enable more restrictive safelisting in production environments.</p>



<h4 class="wp-block-heading"><a href="#maximize-security-and-performance-with-id-only-operations" aria-hidden="true" class="aal_anchor" id="maximize-security-and-performance-with-id-only-operations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Maximize security and performance with ID-only operations</h4>



<p>ID-only operations are the most restrictive, but they also are the most efficient since the router can avoid processing any complex, freeform query strings (similar to <a href="https://www.apollographql.com/docs/router/configuration/distributed-caching/"><em>automatic</em> persisted query caching</a>). In this mode, <strong>clients are required to send requests to the router with <em>only</em> a unique persisted query ID</strong> which the router can use to identify the requested operation. The router will reject any requests with an invalid ID or a freeform query string.&nbsp;</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml"># router.yaml

preview_persisted_queries:
  enabled: true
  safelist:
    enabled: true
    require_id: true</code></pre>



<p>ID-only operations are supported by all Apollo Clients — web, iOS, and Kotlin — but support in other libraries may vary.&nbsp;</p>



<h4 class="wp-block-heading"><a href="#allow-any-known-shapes-for-more-flexible-enforcement" aria-hidden="true" class="aal_anchor" id="allow-any-known-shapes-for-more-flexible-enforcement"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Allow any known shapes for more flexible enforcement</h4>



<p>In the case that your GraphQL client does not support ID-only operations, you can use less stringent shape-based safelisting. Shape-based safelisting is also useful in cases where ID-only operations are excessively restrictive. For example, it may be useful for pre-production apps to query a staging graph using the full query string for easier debugging. In these cases, you can use the default option for safelisting which will accept operations without a persisted query ID as long as they match the shape of a registered operation:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-"># router.yaml

preview_persisted_queries:
  enabled: true
  safelist:
    enabled: true</code></pre>



<h2 class="wp-block-heading"><a href="#defense-in-depth" aria-hidden="true" class="aal_anchor" id="defense-in-depth"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Defense-in-depth</h2>



<p>Safelisting known operations in your router contributes yet another layer to your defense-in-depth strategy for your API platform. However, like any security measure, is most effective when layered with additional checks.</p>



<h3 class="wp-block-heading"><a href="#govern-operation-shape" aria-hidden="true" class="aal_anchor" id="govern-operation-shape"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Govern operation shape</h3>



<p>One of the best checks to combine with safelisting is a general <a href="https://www.apollographql.com/docs/router/configuration/operation-limits/">limit on operation complexity</a>. Setting a maximum height, depth, number of aliases, and number of root fields for any given operation creates a safety net to prevent accidentally or intentionally malformed queries from impacting the performance of your API.&nbsp;</p>



<p>These limits are table-stakes for public endpoints where safelisting isn’t an option but are also helpful in-house to prevent excessively complex operations from accidentally being safelisted.</p>



<h3 class="wp-block-heading"><a href="#limit-scope-of-access" aria-hidden="true" class="aal_anchor" id="limit-scope-of-access"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Limit scope of access</h3>



<p>Safelisting restricts incoming requests to preregistered operations, but for compliance purposes, you may also need to limit the scope of data available in a particular endpoint. For example, if you have a supergraph that contains PCI, you may need a separate endpoint for client apps that removes that information.</p>



<p>With GraphOS you can use <a href="https://www.apollographql.com/docs/graphos/delivery/contracts/">contracts</a> to systematically create filtered endpoints that remove any sensitive or unnecessary information. For each of your filtered endpoints, you can create a tailored query safelist specific to its clients.</p>



<h2 class="wp-block-heading"><a href="#get-started-with-safelisting" aria-hidden="true" class="aal_anchor" id="get-started-with-safelisting"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started with safelisting</h2>



<p>Regardless of where you are in your journey with GraphQL, persisted query safelisting is a great way to reduce your exposure to malformed or malicious requests. Customers on the Apollo GraphOS Enterprise plan or <a href="https://studio.apollographql.com/signup?type=enterprise-trial&amp;referrer=blog">Enterprise Trial</a> can start using safelisting today. To get started, head over to the <a href="https://www.apollographql.com/docs/graphos/operations/persisted-queries">GraphOS docs</a>!</p>


Secure your GraphQL platform by safelisting known queries

Announcing Apollo Client 3.8 With React Suspense Integration

Wait for it… Announcing Apollo Client 3.8 with React Suspense Integration

Federated subscriptions in GraphOS: real-time data at scale


<p>We’re happy to introduce an <a href="https://github.com/apollographql/apollo-kotlin">Apollo Kotlin</a> plugin for Android Studio and IntelliJ IDEA, to help you work with the library and improve your productivity.</p>



<p>This preview release can be tried out today.</p>



<h2 class="wp-block-heading"><a href="#features" aria-hidden="true" class="aal_anchor" id="features"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Features</h2>



<h3 class="wp-block-heading"><a href="#on-the-fly-code-generation" aria-hidden="true" class="aal_anchor" id="on-the-fly-code-generation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>On-the-fly code generation</h3>



<p>Apollo Kotlin is a strongly-typed client library that generates models from your GraphQL queries. This works thanks to a Gradle plugin that triggers the code generation at build time. Normally, after touching a graphql file, to be able to use the up-to-date generated models in your Kotlin code, you would need to manually run the codegen Gradle task.</p>



<p>With the IDE plugin, this is done automatically: the codegen is run in the background whenever you touch your GraphQL queries, so you can use the models immediately.</p>



<figure class="wp-block-video"><video controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/00-on-the-fly-codegen.mov"></video><figcaption class="wp-element-caption">On-the-fly code generation</figcaption></figure>



<h3 class="wp-block-heading"><a href="#migration-helpers" aria-hidden="true" class="aal_anchor" id="migration-helpers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Migration helpers</h3>



<p>Apollo Kotlin 3 was a major version that introduced quite a few changes compared to version 2. While some of <a href="https://www.apollographql.com/docs/kotlin/migration/3.0/">these changes</a> require manual tweaks to the code, a lot of these can be automated. Which is what the “Migrate to Apollo Kotlin 3” action does. If you are still on version 2, now is a good time to migrate!</p>



<figure class="wp-block-video"><video controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/01-migration-apollo2-to-3.mp4"></video><figcaption class="wp-element-caption">Migrate to Apollo Kotlin 3</figcaption></figure>



<p>If you are using Apollo Kotlin 3 with <a href="https://www.apollographql.com/docs/kotlin/migration/3.0/#codegen">the <code>compat</code> codegen</a>, which was meant to ease the migration from version 2 (and will be discontinued in the upcoming version 4 release), the plugin can also help with this: “Migrate to <code>operationBased</code> Codegen”.</p>



<figure class="wp-block-video"><video controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/02-migration-compat-to-operationbased.mov"></video><figcaption class="wp-element-caption">Migrate to operationBased codegen</figcaption></figure>



<h3 class="wp-block-heading"><a href="#navigation" aria-hidden="true" class="aal_anchor" id="navigation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Navigation</h3>



<p>When editing Kotlin code that references GraphQL queries, it is often useful to go to their definition &#8211; for instance, if you need to add a field to the selection. The natural way to do that in Android Studio is to <code>Cmd/Ctrl + click</code> (or <code>Cmd/Ctrl + b</code> on the keyboard) on the symbol. However without any special knowledge of Apollo Kotlin or GraphQL, this would go to the generated code, which is not as useful. Not anymore! The plugin adds target to go to the GraphQL definition:</p>



<figure class="wp-block-video"><video controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/03-go-to-declaration.mov"></video><figcaption class="wp-element-caption">Go to GraphQL definition</figcaption></figure>



<p>Note that the generated code destination is still there, as it is sometimes handy to have a look at it.</p>



<p>We’ve also added these nifty GraphQL icons in the gutter next to operation and fragment references. Click on them to go to the definition.</p>



<p>To go to the Schema instead, use “Go To Type Declaration” (<code>Cmd/Ctrl + Shift + click</code>, or <code>Cmd/Ctrl + Shift + b</code>):</p>



<figure class="wp-block-video"><video controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/04-go-to-type-declaration.mov"></video><figcaption class="wp-element-caption">Go to the schema</figcaption></figure>



<p>The reverse works too if you need it: “Find Usages” on your GraphQL operation will list Kotlin files referencing them:</p>



<figure class="wp-block-video"><video controls src="https://wp.apollographql.com/wp-content/uploads/2023/06/05-find-usages.mov"></video><figcaption class="wp-element-caption">Find code usages</figcaption></figure>



<p>We hope to add “Find Usages” on fields as well in the future.</p>



<h3 class="wp-block-heading"><a href="#more-to-come" aria-hidden="true" class="aal_anchor" id="more-to-come"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>More to come</h3>



<p>We are working on adding more features and your ideas are very welcome! Please don’t hesitate to submit feature requests on <a href="https://github.com/apollographql/apollo-kotlin/issues/new/choose">the issue tracker</a>.</p>



<h2 class="wp-block-heading"><a href="#try-it-out" aria-hidden="true" class="aal_anchor" id="try-it-out"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Try it out!</h2>



<p>To install the plugin:</p>



<ol class="wp-block-list">
<li>During the preview phase, you will need to add a dedicated plugin repository:<br><br>&#8211; <code>Settings</code> &gt; <code>Plugins</code> &gt; <code>⚙️</code> &gt; <code>Manage Plugin Repositories</code> &gt; <code>➕</code> &gt; <code>https://plugins.jetbrains.com/plugins/preview/20645</code><br><br>&#8211; If you want the cutting edge, use this “snapshots” URL instead (new versions once a week): <code>https://raw.githubusercontent.com/apollographql/apollo-kotlin/main/intellij-plugin/snapshots/plugins.xml</code></li>



<li><code>Marketplace</code> &gt; Search for &#8220;Apollo GraphQL&#8221; &gt; <code>Install</code></li>
</ol>



<p>Detailed instructions are available <a href="https://github.com/apollographql/apollo-kotlin/tree/main/intellij-plugin">here</a>.</p>



<h2 class="wp-block-heading"><a href="#conclusion" aria-hidden="true" class="aal_anchor" id="conclusion"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Conclusion</h2>



<p>We hope this plugin will make your experience with Apollo Kotlin a delightful one and will help you build great apps. Stay tuned for more, and as always, your feedback is welcome! You can reach out on <a href="https://github.com/apollographql/apollo-kotlin">GitHub</a>, the <a href="https://discord.gg/graphos">Apollo Community</a>, or the <a href="https://slack.kotl.in/">Kotlin Slack</a>!</p>


Announcing the Apollo Kotlin plugin for Android Studio and IntelliJ IDEA


<p>When it comes to writing code collaboratively, consistency is everything. APIs are no exception. In fact, APIs are perhaps the most important place to ensure consistency, since they act as a vein for collaboration across nearly every developer in an organization&#8217;s ecosystem.</p>



<p>For GraphQL APIs, the schema is at the heart of all collaboration and consumption, but ensuring consistency in a graph that spans many teams, tools, and workflows is no easy task. Today, we’re excited to make things a bit easier by adding <a href="https://www.apollographql.com/docs/graphos/delivery/schema-linter">schema linting</a> to Apollo GraphOS!&nbsp;</p>



<p>As an API platform owner, linter checks in GraphOS will help you keep your schema syntax clean and consistent by validating that schema changes pass pre-defined formatting and naming rules like:</p>



<ul class="wp-block-list">
<li>Field names should be <code>camelCase</code></li>



<li>Input type names should be suffixed with <code>Input</code></li>



<li>The <code>@tag</code> directive should use a pre-approved value for its <code>name</code> argument</li>
</ul>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="868" src="https://wp.apollographql.com/wp-content/uploads/2023/06/image2-1024x868.png" alt="" class="wp-image-21398" srcset="https://wp.apollographql.com/wp-content/uploads/2023/06/image2-1024x868.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/06/image2-300x254.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/06/image2-768x651.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/06/image2-1536x1302.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/06/image2-1200x1017.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/06/image2.png 1628w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p><strong>Starting today, schema linting is available for all orgs on the GraphOS Enterprise and Serverless plans.</strong> Linter checks will automatically run whenever new schema changes are published to GraphOS, but you can also run checks manually on a local schema or in a separate CI/CD pipeline using the Rover CLI.</p>



<h2 class="wp-block-heading"><a href="#consistency-at-every-stage-of-graph-development" aria-hidden="true" class="aal_anchor" id="consistency-at-every-stage-of-graph-development"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Consistency at every stage of graph development</h2>



<p>GraphOS schema linting is designed to integrate seamlessly into your existing processes to ensure that your schema’s syntax stays consistent at every stage of graph development.</p>



<h3 class="wp-block-heading"><a href="#lint-locally-with-the-rover-cli" aria-hidden="true" class="aal_anchor" id="lint-locally-with-the-rover-cli"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Lint locally with the Rover CLI</h3>



<p>No one wants to reread all of the code they just wrote to figure out where they miscapitalized one field. Using <a href="https://www.apollographql.com/docs/rover">the Rover CLI</a>, devs can run schema linting on their local schema as they work to ensure that their changes pass when published.</p>



<p>To run schema linting locally, just <a href="https://www.apollographql.com/docs/rover/getting-started">install Rover</a>, authenticate, and run <a href="https://www.apollographql.com/docs/rover/commands/graphs#graph-lint"><code>rover graph lint</code></a> or <a href="https://www.apollographql.com/docs/rover/commands/subgraphs#subgraph-lint"><code>rover subgraph lint</code></a>.</p>



<h3 class="wp-block-heading"><a href="#integrate-into-ci-cd" aria-hidden="true" class="aal_anchor" id="integrate-into-ci-cd"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Integrate into CI/CD</h3>



<p>Linting locally helps individual developers work quickly, but keeping a cross-team code base consistent requires enforcing linter rules centrally. Similar to other linting tools you may use, GraphOS schema linting can be integrated directly into your existing CI/CD pipelines to ensure that every schema change is checked before being published, no matter who it comes from.</p>



<p>To run schema linting in a third-party CI/CD tool, just <a href="https://www.apollographql.com/docs/rover/ci-cd/">install the Rover CLI as part of your pipeline</a>.</p>



<h3 class="wp-block-heading"><a href="#linter-checks-on-published-schemas-in-graphos" aria-hidden="true" class="aal_anchor" id="linter-checks-on-published-schemas-in-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Linter checks on published schemas in GraphOS&nbsp;</h3>



<p>GraphOS gives you a central source of truth for all of your schemas and, if you have a <a href="https://apollographql.com/docs/federation">federated graph</a>, acts as the final checkpoint for your schema before your graph router uses it in production.&nbsp;</p>



<p>Running linter checks for new changes published to your schema in GraphOS ensures consistency in all of your running graphs.</p>



<p>If you already have schema checks set up in GraphOS, linter checks will automatically be added to your checks workflow! You can review the status of linter checks on the checks page in GraphOS Studio.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="578" src="https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-1024x578.png" alt="" class="wp-image-21412" srcset="https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-1024x578.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-300x169.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-768x434.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-1536x867.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-2048x1156.png 2048w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-1200x678.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/06/linter-checks-screen-1980x1118.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#configuring-the-linter-in-graphos-studio" aria-hidden="true" class="aal_anchor" id="configuring-the-linter-in-graphos-studio"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Configuring the linter in GraphOS Studio</h2>



<p>The linter in GraphOS comes with a pre-defined list of rules that cover common best practices for writing GraphQL schemas. You can customize the severity of each rule independently to <code>Off</code>, <code>Warn</code>, or <code>Error</code> in GraphOS Studio under Checks &gt; Configuration &gt; Linter.</p>



<p>When set to <code>Warn</code>, a rule violation will allow the checks workflow to pass but output a warning, whereas a violation of a rule set to <code>Error</code> will cause the checks workflow to <em>fail</em> outright.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="471" src="https://wp.apollographql.com/wp-content/uploads/2023/06/image1-1024x471.png" alt="" class="wp-image-21403" srcset="https://wp.apollographql.com/wp-content/uploads/2023/06/image1-1024x471.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/06/image1-300x138.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/06/image1-768x353.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/06/image1-1536x706.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/06/image1-1200x552.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/06/image1.png 1766w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>You can also choose to have the linter ignore definitions marked with <code>@deprecated</code> or <code>@inaccessible</code> to prevent errors caused by outdated or private definitions.</p>



<h2 class="wp-block-heading"><a href="#start-linting" aria-hidden="true" class="aal_anchor" id="start-linting"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Start linting!</h2>



<p>Starting today, linting is enabled for every organization on GraphOS Enterprise and Serverless plans. All you need to do to get started is publish a change to your graph! If you have schema checks enabled, you’ll automatically see linter checks as a new step.&nbsp;</p>



<p>If you want to change the linter configuration for your graph, head to the “Checks” tab in GraphOS Studio → Configuration → Linter. Or if you haven’t set up schema checks yet for your graph, check out <a href="https://www.apollographql.com/docs/graphos/delivery/schema-checks">the documentation</a> to get started.</p>


Standardize GraphQL schema linting policies with GraphOS


<p>A GraphQL API with the power to give app developers everything they need in a single query is excellent for delivery velocity, but it also could have the potential to enable improper access to data if not secured correctly.&nbsp;</p>



<p>With supergraph architecture, you can mitigate this risk by implementing the proper security controls in each subgraph, but Apollo GraphOS is helping platform teams add an additional layer of security in front of subgraphs by building controls into the graph router itself.</p>



<p>Router security is one of the key themes in our 2023 GraphOS roadmap, and today we’re excited to ship a preview of our newest router security feature for GraphOS Enterprise: operation size and complexity limiting.</p>



<h2 class="wp-block-heading"><a href="#centralized-protection-from-misuse" aria-hidden="true" class="aal_anchor" id="centralized-protection-from-misuse"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Centralized protection from misuse</h2>



<p>For production graphs, preventing accidental or intentional misuse is a key requirement. If not protected properly, client apps can issue expensive queries that cause excessive load on the server potentially resulting in denial of service. Even in less extreme cases, poorly formed queries can still impact the performance of client apps and lead to a slower user experience.</p>



<p>There are a variety of packages designed to limit operation complexity and cost at the server level; however, as a federated graph grows, it can become increasingly difficult to set, standardize, and maintain these limits across many subgraphs owned by different teams. Luckily, supergraph architecture presents us with the unique opportunity to centralize control in a single point: the router.</p>



<p>Enforcing operation size and complexity limits in the graph router makes it far easier to standardize policies for a large graph and alleviates the burden of coordinating limits across every subgraph.</p>



<h2 class="wp-block-heading"><a href="#limit-depth-height-root-fields-and-aliases" aria-hidden="true" class="aal_anchor" id="limit-depth-height-root-fields-and-aliases"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Limit depth, height, root fields, and aliases</h2>



<p>Just like it sounds! With GraphOS Enterprise, you can now configure your router to limit the depth, height, number of root fields, and number of aliased fields of any incoming GraphQL operation. If an operation exceeds any of the set limits, the router will reject it before attempting to resolve the request with a <code>400 BAD_REQUEST</code> status code.</p>



<p>All of these limits can be configured in the <code>router.yaml</code> file for any router authenticated with your GraphOS Enterprise credentials:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml">preview_operation_limits:
  max_depth: 100
  max_height: 200
  max_root_fields: 40
  max_aliases: 30</code></pre>



<p>Optionally, you can also configure the router to only log a warning message for operations that exceed the set limits rather than rejecting the operation outright:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml">preview_operation_limits:
  # some limits
  warn_only: TRUE</code></pre>



<p><code>warn_only</code> defaults to <code>FALSE</code>, but it can be useful to set it to <code>TRUE</code> in development environments for testing purposes.</p>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started</h2>



<p>The feature preview for operation size and complexity limits is available now for all users with a GraphOS Enterprise plan. To get started, make sure that your router is authenticated with your GraphOS Enterprise credentials and is running the <a href="https://github.com/apollographql/router/releases" target="_blank" rel="noreferrer noopener">latest version of Apollo Router</a>. Then, head to <a rel="noreferrer noopener" href="https://www.apollographql.com/docs/router/configuration/operation-limits" target="_blank">the documentation</a> for detailed information about configuring limits in your <code>router.yaml</code> file.</p>



<p>If you&#8217;re not a GraphOS Enterprise customer yet, <a href="https://www.apollographql.com/contact-sales">get in touch with us</a> to learn more and start a trial!</p>



<p>We’re excited for you to start setting some limits and to hear what you think! If you encounter any problems or have feedback, feel free to <a href="https://github.com/apollographql/router/issues">open an issue</a>. That being said, this feature is still in preview, so there may be some final adjustments before we mark it as GA. To stay up to date, be sure to bookmark the <a href="https://github.com/apollographql/router/blob/dev/CHANGELOG.md">Apollo Router changelog</a>.</p>



<p>Happy querying!</p>


Prevent graph misuse with operation size and complexity limits


<p>Just over a year ago, we introduced Apollo Router, the graph router that is now at the heart of Apollo GraphOS. Unlike its predecessor <a href="https://www.apollographql.com/docs/apollo-server/using-federation/api/apollo-gateway/">Apollo Gateway</a>, Apollo Router was designed to&nbsp;maximize the performance benefits of GraphQL and <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">supergraph architecture</a>, while being secure by default. After switching to the router, one customer reported a <strong>93% reduction in gateway cloud spend</strong>, a <strong>30x reduction in Kubernetes Pod counts</strong>, and 70% less code to maintain – while delivering even faster response times, with <strong>a 70% reduction in request latencies</strong>!&nbsp;</p>



<p>Today, some of the world’s largest companies rely on GraphOS for their mission-critical graph API infrastructure. Routers have processed 100% of Black Friday traffic for top-100 retail companies, and major fintech organizations are trusting their routers to handle tax season.</p>



<p><em>So what’s next?</em></p>



<p>Many of Apollo Router’s initial users are running billions of operations each month with GraphOS. The features in this release focus on the challenges of operating a graph router at massive scale: <strong>defense in depth, maximizing performance, and extensibility</strong>. Today, we are excited to make three new features generally available to GraphOS Enterprise customers running a self-hosted router: JWT auth, distributed APQ caching, and support for external coprocessors.</p>



<h2 class="wp-block-heading"><a href="#supergraph-defense-in-depth" aria-hidden="true" class="aal_anchor" id="supergraph-defense-in-depth"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Supergraph defense-in-depth</h2>



<p><strong>Block malicious traffic at the edge of your graph with new JWT auth support in the router.</strong></p>



<p>Previously, the router could only forward user access tokens (JWT) generated by identity providers like Auth0 or Okta onto subgraphs and underlying REST APIs. Keeping your supergraph secure meant doing JWT checks in every subgraph or REST API which allows attackers deeper into your graph – and missing a single check often results in security holes.</p>



<p>Now, with the router as a <a href="https://doyensec.com/resources/Doyensec_Apollo_Report_Q22022_v4_AfterRetest.pdf">security-hardened</a> entry point to your graph, you can reject malicious traffic early and shield your subgraphs and REST APIs from unwanted traffic. Router v1.12 adds support for <a href="https://www.apollographql.com/docs/router/configuration/authn-jwt">JWT validation, claim extraction, and custom security policies in Rhai scripting</a> to reject bad traffic at the edge of the graph – for enhanced zero-trust and defense-in-depth. Extracting claims once in the router and securely forwarding them to subgraphs has several key benefits, including: </p>



<ul class="wp-block-list">
<li><strong>Reducing operational burden on backend API teams</strong> &#8211; no JWT keys to manage</li>



<li><strong>Reducing latency due to JWT processing</strong> &#8211; since the JWT is processed only once in the router</li>



<li><strong>Speeding up response times</strong> &#8211; by selectively forwarding JWT claims for increased <a href="https://www.apollographql.com/docs/router/configuration/traffic-shaping/#query-deduplication">query deduplication</a></li>
</ul>



<p>These performance benefits compound at scale, particularly if the router is simultaneously processing similar queries.</p>



<h2 class="wp-block-heading"><a href="#maximize-performance-at-scale" aria-hidden="true" class="aal_anchor" id="maximize-performance-at-scale"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Maximize performance at scale</h2>



<p><strong>Reduce p99 latency during peak traffic with Distributed APQ (automatic persisted query) caching with Redis.</strong></p>



<p><a href="https://www.apollographql.com/docs/apollo-server/performance/apq/">APQ</a> can drastically reduce response latency by allowing clients to send only a unique hash over the wire instead of a large query document, providing a fast path to query execution. You may already have in-memory APQ configured for your router, however when load balancing requests over a large fleet of router instances, the in-memory cache won’t be consistently hot. Unlucky users, especially during scaling events, will hit cold caches and experience slower response times as the APQ cache must be built individually in each router instance.</p>



<p>With Router v1.12 , you can now use <a href="https://www.apollographql.com/docs/router/configuration/distributed-caching">distributed APQ caching</a> to improve p99 latencies during peak times. A shared Redis instance can now be used by the entire router fleet to build the APQ cache faster and share existing APQ cache with new router instances that are spun up during scaling events – when they need it most. This ensures the fast path to query execution is consistently available to all users even during peak load.</p>



<h2 class="wp-block-heading"><a href="#extensibility-with-coprocessors" aria-hidden="true" class="aal_anchor" id="extensibility-with-coprocessors"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Extensibility with coprocessors</h2>



<p><strong>Extend the router in your language of choice using new external coprocessor support.</strong></p>



<p>To create common customizations for Apollo Gateway like header propagation and error handling, you have to code plugins and middleware directly into a custom gateway package. These monolithic gateway packages must be built and deployed as a single unit, often requiring coordination across teams. Since everything is run in a single process, errors in the custom code can crash the whole Gateway, and it’s not clear which team should be paged at 3 am to resolve the issue.</p>



<p>With Apollo Router, most common customizations are built directly into the stock binary and <a href="https://www.apollographql.com/docs/router/configuration/overview">can be configured with YAML</a>. YAML config alone allowed one of our largest Enterprise customers to eliminate 70% of their custom Gateway code.</p>



<p>In cases where the YAML config isn’t enough, Router also supports Rhai scripting (similar to Lua in NGINX and Envoy) which can be used for in-memory manipulation of headers, cookies, and more with a well-defined <a href="https://www.apollographql.com/docs/router/customizations/rhai-api">Rhai API reference</a>. Rhai scripts are great for lightweight customizations and provide a safe, sandboxed way to customize the Router’s request flow.</p>



<p>For more powerful customizations, the Router now supports <a href="https://www.apollographql.com/docs/router/configuration/external">external coprocessors</a> written in the programming language of your choice. Coprocessors run with full isolation and a clean separation of concerns, that decouples delivery and provides fault isolation. Low overhead can be achieved by running coprocessors alongside the router on the same host or in the same Kubernetes Pod as a sidecar. Coprocessors can be used to speed Gateway migrations, support bespoke use cases, or integrate the router with existing network services for custom auth (JWT mapping, claim enrichment), service discovery integration, and more!</p>



<p>However, our goal is to eliminate as much custom code as possible, so if you have a common use case that you think should be supported in the stock Apollo Router binary, be sure to <a href="https://github.com/apollographql/router/issues">open an issue</a>.</p>



<h2 class="wp-block-heading"><a href="#enabling-graphos-enterprise-features" aria-hidden="true" class="aal_anchor" id="enabling-graphos-enterprise-features"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Enabling GraphOS Enterprise features</h2>



<p><strong>Upgrade to Router v1.12 and ensure they are connected to GraphOS with an Enterprise plan.</strong></p>



<p>All Apollo GraphOS Enterprise customers can access these features today for self-hosted instances of Apollo Router. If your router is already connected to GraphOS Studio using your <code>APOLLO_KEY</code> and <code>APOLLO_GRAPH_REF</code>, and you’re running the latest version of Apollo Router, no further action is required! You can set up all of these features in your existing router config. See <a href="https://www.apollographql.com/docs/router/enterprise-features">the documentation</a> for additional details.</p>



<p>These are just the first of many router features on the roadmap for GraphOS. We have exciting security and performance features coming up soon for GraphOS Enterprise as well as GraphOS Cloud, so stay tuned!</p>



<h2 class="wp-block-heading"><a href="#optimize-apollo-router-with-tips-from-the-apollo-community" aria-hidden="true" class="aal_anchor" id="optimize-apollo-router-with-tips-from-the-apollo-community"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Optimize Apollo Router with tips from the Apollo community</h2>



<p>The Apollo Router is a core part of the Apollo stack, and we want you to feel confident to trust it with your queries in production. The Apollo Champions community features many customers who have already made this switch and have insights that can help, including the team at Wayfair. They&nbsp;switched to Apollo Router from Gateway before Black Friday. The Wayfair team will discuss how they made the switch as well as the improvements they saw as a result. Be sure to tune in to the <a href="https://bit.ly/3liIeLY" data-type="URL" data-id="https://bit.ly/3liIeLY">Apollo Champion’s Corner on March 23rd</a> to learn more.</p>


New in Apollo Router v1.12: Improved router security, performance, and extensibility


<p><br>Are you looking to learn how to build a GraphQL API using Typescript with Apollo Server? Then join the Apollo Developer Advocates for a live stream event on 3/22 at 9:00 AM PST! The event will be hosted in the <a rel="noreferrer noopener" href="https://discord.com/invite/graphos" target="_blank">Apollo Discord</a> with a live Q&amp;A session at the end. We&#8217;ll also be trying this live stream directly from our <a href="https://www.youtube.com/@ApolloGraphQL">YouTube</a> so you can subscribe to get a notification of the event.</p>



<p>During this live stream, we will provide a step-by-step guide to help you build your subgraph starting with a template using Schema Definition Language (SDL). This will include everything you need to get started along with important toolings like codegen and <a href="https://www.apollographql.com/docs/graphos/">GraphOS</a>. Plus, they will answer any questions you have along the way. </p>



<p>If you want to learn more about Apollo Server + Typescript, this is the perfect opportunity for you. So don’t miss out and join the Apollo Developer Advocates to get your questions answered! We&#8217;ll be updating this post with the video recording once it is available.</p>


Building a GraphQL API in Typescript with Apollo Server


<p>Are you interested in building a successful GraphQL API? Then you won&#8217;t want to miss the upcoming Tech Talk + Workshop that dive deep into Schema Design Best Practices. The event is split into two sessions, the first being a Tech Talk on March 9th at 10am PT, and the second being a Workshop on March 16th at 9am PT.</p>



<p>During the Tech Talk, you&#8217;ll learn about the common GraphQL schema design best practices that apply to supergraphs, and gain valuable tips from Erik on how to create and iterate on the type definitions that they contribute to the overall schema efficiently, without unexpected breaking changes for clients. This session is perfect for those who are already familiar with GraphQL and are looking to deepen their understanding of schema design.</p>



<p>If you&#8217;re looking for a more hands-on experience, then the Workshop is for you. In this course, you&#8217;ll get hands-on training to build readable, scalable, well-documented schemas with GraphQL. You&#8217;ll learn how to build a strong GraphQL schema that serves as the foundation of any successful GraphQL project.</p>



<p>Both sessions are packed with valuable information and practical tips that you can immediately apply to your own GraphQL projects. Whether you&#8217;re a beginner or an experienced GraphQL developer, you&#8217;re sure to benefit from attending this event.</p>



<p>The workshop is led by Moon Highway, a company that specializes in providing expert training and consulting services for web developers. Don&#8217;t miss this opportunity to learn from their team of experienced GraphQL developers and take your GraphQL skills to the next level. <a href="https://www.apollographql.com/events/tech-talk-workshop/register/deep-dive-into-schema-design-best-practices/">Register now for free</a> and get ready to dive deep into schema design best practices!</p>


Virtual Events – Deep Dive into Schema Design Best Practices


<p>The Apollo CLI <code>service</code> commands are now officially deprecated and will reach their <strong>final end of life on April 28th, 2023.</strong></p>



<p><strong>Note: </strong>Apollo will continue to provide support for the Apollo CLI <code>client</code> commands.</p>



<p>Rover is the command line interface for managing and maintaining graphs through GraphOS with over 10 million all-time downloads and over 4 million command invocations per day. If you are still using Apollo CLI’s <code>service</code> commands and would like to migrate to the Rover CLI, please refer to this migration <a href="https://www.apollographql.com/docs/rover/migration/">guide</a>.</p>



<p>For more information regarding Apollo’s software lifecycle policies and an up-to-date list of actively maintained software versions, please visit the Apollo launch stages <a href="https://www.apollographql.com/docs/resources/product-launch-stages/">documentation</a>.</p>


Announcing the end-of-life schedule for Apollo CLI service commands


<p>Almost a year ago we introduced <a href="https://www.apollographql.com/blog/announcement/platform/save-and-share-your-graphql-operations-in-apollo-explorer/">operation collections</a> in GraphOS as a way to save your frequently used operations in Explorer and share them with your team. Today, we are making saved operations even more useful with operation scripts! Now, you can write scripts for your saved operations to build automated testing workflows that call other saved operations.</p>



<h2 class="wp-block-heading"><a href="#what-are-operation-scripts" aria-hidden="true" class="aal_anchor" id="what-are-operation-scripts"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What are operation scripts?</strong></h2>



<p>Operation scripts are a brand new, <strong>free 🎊</strong> feature in GraphOS Studio that let you write scripts that run before your operation to execute JavaScript code, make HTTP requests, and run other saved operations before your current operation. You may think this sounds a lot like what you can do with <a href="https://www.apollographql.com/blog/announcement/tooling/automatically-authenticate-with-preflight-scripts-in-apollo-studio-explorer/">preflight scripts</a>, and you would be correct! An operation script, at a high level, is a preflight script that is defined <em>per operation</em> instead of <em>per variant</em>.</p>



<p>With operation scripts you and your team can:</p>



<ul class="wp-block-list">
<li>Easily debug the behavior of individual operations when they’re provided various values</li>



<li>Design and write scripted workflows with your saved operations for testing</li>
</ul>



<h2 class="wp-block-heading"><a href="#adding-an-operation-script" aria-hidden="true" class="aal_anchor" id="adding-an-operation-script"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Adding an operation script</strong></h2>



<p>Adding operation scripts to your saved operations is easy. To get started, head to Explorer in GraphOS Studio, open up the Operation Collections tab on the left panel, and open the operation you would like to write a script for. In the bottom pane, you’ll see a new tab named Script.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="879" src="https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM-1024x879.png" alt="" class="wp-image-19904" srcset="https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM-1024x879.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM-300x257.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM-768x659.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM-1200x1030.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.03.15-PM.png 1436w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>Click on the “Add Script” button to open up the operation script editor panel. To help you start writing your script, there are code snippets to the left of the editor. Clicking on the plus icon next to a snippet will insert it in the editor.</p>



<p>To run your operation script with your current operation, just save your operation and turn on the operation script setting within Explorer Settings &gt; Personal Settings.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="704" src="https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM-1024x704.png" alt="" class="wp-image-19901" srcset="https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM-1024x704.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM-300x206.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM-768x528.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM-1200x824.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/03/Screenshot-2023-03-06-at-6.01.31-PM.png 1406w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>ℹ️ <strong>Note</strong>: Operation scripts are not only limited to GraphOS Explorer, they can also be created in Sandbox and within Explorer or Sandbox embeds!</p>



<h2 class="wp-block-heading"><a href="#calling-saved-operations-with-runoperation" aria-hidden="true" class="aal_anchor" id="calling-saved-operations-with-runoperation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Calling saved operations with runOperation</strong></h2>



<p>In your script, you can also run <em>other</em> saved operations from any variant of your graph against your current endpoint using the <code>runOperation</code> command. This allows you to use values from the output of those operations as GraphQL variables for your current operation.&nbsp;</p>



<p>Below is an example of using <code>runOperation</code> to get a list of ships from the SpaceX GraphQL API and then passing the ID of the <code>firstShip</code> to an environment variable.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-javascript">const response = await explorer.runOperation({
 scope: &#039;shared&#039;,
 graphRef: &#039;SpaceX-pxxbxen@current&#039;,
 collectionName: &#039;Mission Control&#039;,
 operationName: &#039;Ships&#039;,
})

const firstShipID = response.result.data.ships[0].id

explorer.environment.set(&#039;shipID&#039;, firstShipID)</code></pre>



<p>From here you can use any environment variables set in your script by passing them into the GraphQL variables panel. For instance, if I had this script set on a mutation that takes in a <code>shipID</code> and then sets the <code>status</code> of the ship to <code>Launched</code>, I would use the following GraphQL variables in my variables panel:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">{
  &quot;shipID&quot;: &quot;{{ shipID }}&quot;,
  &quot;status&quot;: &quot;Launched&quot;,
}</code></pre>



<p>When you run your operation, it will run your script, populate your variables, and then run the current operation. Amazing! Now you can build operation workflows without you having to go back and forth between tabs copying and pasting values! And, if you forget the names of your saved operations or collections, the script editor provides automatic IntelliSense to suggest names of collections and operation names. To trigger it you can start typing <code>&#039;&#039;</code> and it will provide a dropdown for you to choose from.</p>



<figure class="wp-block-image size-full is-style-default"><img loading="lazy" decoding="async" width="1000" height="636" src="https://wp.apollographql.com/wp-content/uploads/2023/03/7341589aaef2707bbb952f65cc2bdaa6.gif" alt="" class="wp-image-19907"/></figure>



<h3 class="wp-block-heading"><a href="#chaining-operation-scripts-with-runoperation" aria-hidden="true" class="aal_anchor" id="chaining-operation-scripts-with-runoperation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Chaining operation scripts with runOperation</strong></h3>



<p>In addition to running GraphQL operations, runOperation will also run any operation scripts that are saved to the operation if they exist. This allows you and your team to write chains of scripts to automate entire workflows!</p>



<p>ℹ️ <strong>Note:</strong> Be sure that you have the operation script flag turned on in your Explorer settings to test and chain operation scripts.</p>



<h2 class="wp-block-heading"><a href="#start-writing-your-operation-scripts-today" aria-hidden="true" class="aal_anchor" id="start-writing-your-operation-scripts-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Start writing your Operation Scripts today!</strong></h2>



<p>Head over to <a href="https://studio.apollographql.com">GraphOS Studio</a> to start writing scripts and automating testing workflows for your GraphQL operations! Learn more about this feature <a href="https://www.apollographql.com/docs/graphos/explorer/connecting-authenticating/#operation-scripts">here</a> and as always we love hearing from you, so if you have any feedback, feel free to leave a comment in our <a href="https://github.com/apollographql/apollo-studio-community">Studio Community GitHub repository.</a></p>


Automate GraphQL query testing in GraphOS Explorer!


<p>You’ve heard it a million times: <em>everything you need, and nothing more, all in a single query</em>. It’s the core promise of GraphQL, but it presents a challenge. To truly get everything in a single query, you need to put everything you have<em> </em>into a single graph.</p>



<p>At Apollo, we’ve spent the better part of three years designing a GraphQL architecture to address that challenge — we call it <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">supergraph architecture</a>. Its main component is a graph router, which sits in front of your GraphQL servers and has a query planner to execute queries across multiple connected graphs. Just over a year ago, we released Apollo Router, our graph router binary, which is now used by Fortune 500 companies to run billions of operations each month for mission-critical applications.</p>



<p>But Apollo Router enables much more than just scale. It enables faster, more reliable, and more intelligent query execution for any GraphQL API by layering in support for directives like <code>@defer</code> and entity types. We want to bring these benefits and more to every developer in the world that uses GraphQL, not just those in a massive company.</p>



<p>That’s why today, we’re excited to announce general availability of <strong>Apollo GraphOS Cloud</strong> — a cloud-hosted platform with instant-on access to blazing-fast graph routing for any GraphQL API and integrated tools for rapid query development, collaboration, and schema design. Anyone with a GraphQL API can <a href="https://studio.apollographql.com/signup">start using GraphOS Cloud</a> today with 10 million free queries per month our Serverless plan. Serverless is a great way for developers and teams to evaluate GraphOS or even GraphQL. From startups to proofs-of-concept for your enterprise, Serverless is an easy way to try all that Apollo GraphOS has to offer.</p>



<h2 class="wp-block-heading"><a href="#faster-apps-with-hosted-graph-routing" aria-hidden="true" class="aal_anchor" id="faster-apps-with-hosted-graph-routing"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Faster apps with hosted graph routing</h2>



<p>At the heart of GraphOS Cloud is an edge graph router (built on Apollo Router) that enhances your existing GraphQL API with the latest runtime features of GraphOS. The router in GraphOS Cloud is so much more than just a GraphQL API gateway. It’s a runtime that is fully aware of the structure of data available to your connected GraphQL server, and it can manipulate how queries are executed to improve performance.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="520" src="https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-1024x520.png" alt="" class="wp-image-19859" srcset="https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-1024x520.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-300x152.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-768x390.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-1536x780.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router-1200x610.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/03/graph-router.png 1626w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#defer-for-any-server" aria-hidden="true" class="aal_anchor" id="defer-for-any-server"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><code>@defer</code> for any server</h3>



<p>With GraphOS Cloud, you can use <code>@defer</code> with any existing GraphQL server to improve time-to-interactive. When writing a query, you can simply add the <code>@defer</code> directive to slower fields, and GraphOS will automatically return those fields incrementally.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1918" height="864" src="https://wp.apollographql.com/wp-content/uploads/2022/11/explorer-defer-1.gif" alt="" class="wp-image-17955"/></figure>



<h3 class="wp-block-heading"><a href="#subscriptions-caching-and-more-coming-soon" aria-hidden="true" class="aal_anchor" id="subscriptions-caching-and-more-coming-soon"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Subscriptions, caching, and more coming soon</h3>



<p><code>@defer</code> is just the first of many features coming to GraphOS Cloud that will enhance performance for your GraphQL API. Support for subscriptions, response caching, and more are coming up soon on the roadmap!</p>



<h2 class="wp-block-heading"><a href="#develop-save-and-test-queries" aria-hidden="true" class="aal_anchor" id="develop-save-and-test-queries"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Develop, save, and test queries</h2>



<p>GraphOS Cloud automatically registers the schema from your GraphQL API and integrates your hosted router with Explorer — our GraphQL IDE with IntelliSense. With Explorer, you can create queries for your graph with just a click, save queries to reuse later, and even write scripts that chain scripts together for automated testing workflows! Try it out on our <a href="https://studio.apollographql.com/public/apollo-retail-supergraph/explorer?explorerURLState=N4IgzghgbgpgJgYQPYBsUwMYBcCWSB2AknCAFwgCccEADAEYQAsdAtAIwBMcbLjMdrABwUBLOvEZM4jAOwA2AGYKQAGnDR4yNJlwEAoviwAnAJ7EyIAMwBWOh34YKLDBArXeM6wpaDGlmSwygnLcgmwYgnAcNCAAvkA&amp;referrer=operation_collections&amp;variant=prod">demo graph</a>.</p>



<h2 class="wp-block-heading"><a href="#scale-and-collaborate-with-ease" aria-hidden="true" class="aal_anchor" id="scale-and-collaborate-with-ease"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Scale and collaborate with ease</h2>



<p>Most graphs start out small, but they can be a headache to scale across teams when the time comes. GraphOS Cloud has built-in support for Apollo Federation, so you can easily add to your graph modularly with subgraphs whenever you need to. It also automatically keeps your hosted router up-to-date with the latest version of Apollo Router, so you never need to worry about new version rollout.</p>



<p>GraphOS Cloud also integrates your router with a delivery pipeline to prevent breaking changes when collaborating on a graph with multiple subgraphs and client apps. Whenever GraphOS detects a change to one of your schemas, it will automatically recompose a supergraph schema for your router, check it against historic operations from registered client apps, and update your router with the new supergraph schema.</p>



<h2 class="wp-block-heading"><a href="#get-started-with-graphos-cloud-for-free" aria-hidden="true" class="aal_anchor" id="get-started-with-graphos-cloud-for-free"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started with GraphOS Cloud for free</h2>



<p>Anyone with a GraphQL API can <a href="https://studio.apollographql.com/signup?referrer=blog">start using GraphOS Cloud for free</a> today on our Serverless plan. On the Serverless plan, you can run up to 10 million operations per month through GraphOS Cloud for free! If 10 million isn’t enough, you can pay as you go for additional operations.</p>



<h2 class="wp-block-heading"><a href="#help-us-build-the-roadmap-for-graphos-cloud" aria-hidden="true" class="aal_anchor" id="help-us-build-the-roadmap-for-graphos-cloud"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Help us build the roadmap for GraphOS Cloud</h2>



<p>We’re actively building the next generation of GraphOS Cloud to improve governance and throughput for production graphs. We would love to hear feedback, feature requests, and questions you have. Reach out at <a href="mailto:cloud@apollographql.com">cloud@apollographql.com</a>.</p>


Supercharge your GraphQL stack with GraphOS Cloud

Apollo Federation and GraphOS add support for entity interfaces to streamline collaboration


<p>Today, we’re launching our new <a href="https://apollographql.com/trust">Trust Center</a>, a single source of truth for Apollo’s security, compliance, reliability, and legal documentation.&nbsp;</p>



<p>Here’s what you need to know.&nbsp; </p>



<h2 class="wp-block-heading"><a href="#understanding-the-apollo-trust-center" aria-hidden="true" class="aal_anchor" id="understanding-the-apollo-trust-center"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Understanding the Apollo Trust Center</h2>



<p>The Apollo Trust Center is for anyone with questions or needs concerning Apollo’s compliance, security, reliability, or legal policies. From the Trust Center, you can learn about Apollo’s approach to earning customer trust, and, most importantly, you can request and download a wide variety of Apollo’s security, compliance, and legal documentation including:</p>



<ul class="wp-block-list">
<li>Apollo’s SOC 2 report</li>



<li>Summaries of third-party penetration tests for Apollo GraphOS and Apollo Router</li>



<li>Prefilled industry-standard security questionnaires</li>



<li>All of our published reliability metrics</li>



<li>Apollo’s legal documentation required for privacy alignment</li>
</ul>



<p>It’s everything that we expect from vendors, in a single portal, tied with a bow 🎀</p>



<h2 class="wp-block-heading"><a href="#compliance-and-security" aria-hidden="true" class="aal_anchor" id="compliance-and-security"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Compliance and security</h2>



<p>In the Trust Center, you’ll find a <a href="https://www.apollographql.com/trust/compliance-and-security">Compliance and Security page</a> with answers to questions about the security of the Apollo GraphOS platform and how we can strengthen your posture. We offer information on vulnerability patching, internal and third-party penetration testing, and testing practices for our Business Continuity Plan.&nbsp;</p>



<p>Bookmark the Trust Center for annual refreshers and ongoing compliance needs like SOC 2 reports. The Compliance and Security page has everything you need to evaluate before using us and each year going forward.</p>



<h3 class="wp-block-heading"><a href="#reliability" aria-hidden="true" class="aal_anchor" id="reliability"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Reliability</h3>



<p>GraphOS is a critical part of our customers’ stack, so reliability is a critical concern for us at Apollo. Our customers need confidence that features like Uplink, the schema registry, and Contracts will be available. For cloud customers who trust Apollo to manage routing infrastructure in the critical path, this is even more important. On the <a href="https://www.apollographql.com/trust/reliability">Reliability page</a>, you can read more about how we approach matters like failovers, backups, and redundancy.</p>



<h3 class="wp-block-heading"><a href="#legal-and-privacy" aria-hidden="true" class="aal_anchor" id="legal-and-privacy"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Legal and privacy</h3>



<p>Lastly, we’ve put all paperwork associated with legal and privacy compliance on the <a href="https://www.apollographql.com/trust/legal-and-privacy">Legal page</a>. There, you’ll find information about how Apollo’s legal team helps customers comply with the European Union’s GDPR, California’s Consumer Privacy Act, and more. Working with Apollo means one less scavenger hunt for privacy policies and data processing addendums.</p>



<h2 class="wp-block-heading"><a href="#finding-the-right-security-resources" aria-hidden="true" class="aal_anchor" id="finding-the-right-security-resources"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Finding the right security resources</h2>



<p>Apollo’s Trust Center is designed to help you quickly and securely onboard Apollo into your stack and maintain our security health together each year.</p>



<p>If you&#8217;re interested in Apollo GraphOS technical content about cross-origin request forgery protection, access control in the Apollo Router, and similar materials, check out the <a href="https://www.apollographql.com/resources">Resources portal</a>.</p>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next?</h2>



<p>One of the most exciting offshoots of the Trust Center that we’re most excited about is creating new GraphOS security content. Security is one of the most requested topics customers ask us about and we can’t wait to talk about it. So go check out the <a href="https://www.apollographql.com/trust/">Trust Center</a>. Click around, download a security report, and explore. If you’ve got feedback, questions, or suggestions, we’d love to hear from you on the Apollo Community forum.</p>


Introducing the Apollo Trust Center


<p>We’re building so much great stuff at Apollo that it can be tricky to keep track of it all! To help with that, we’re kicking off our Changelog series to cover exciting releases for GraphOS and our open-source projects. We’ll also let you know about upcoming live events and new educational content to help you expand and sharpen your graph expertise. So without further ado, let’s see what’s new!</p>



<h2 class="wp-block-heading"><a href="#boost-app-responsiveness-with-defer-in-graphos" aria-hidden="true" class="aal_anchor" id="boost-app-responsiveness-with-defer-in-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Boost app responsiveness with @defer in GraphOS</h2>



<p>If a query includes a field that takes a long time to resolve, it can delay your graph’s entire response, making your apps feel less responsive. With GraphOS support for the @defer directive (now generally available!), your graph can respond to the client with most of the response data almost immediately, then follow up with slower fields when they’re ready.</p>



<p>To learn more, check out <a rel="noreferrer noopener" href="https://www.apollographql.com/blog/announcement/platform/rethinking-react-components-with-defer/" target="_blank">the announcement blog post</a> and <a rel="noreferrer noopener" href="https://www.apollographql.com/docs/graphos/routing/defer" target="_blank">the docs</a>. Make sure to set your graph’s federation version to 2.1 or higher in Apollo Studio!</p>



<figure class="wp-block-image size-full is-resized"><img loading="lazy" decoding="async" src="https://wp.apollographql.com/wp-content/uploads/2023/01/in_AdobeExpress.gif" alt="An animation shows the process of switching the federation version to 2.1 in Apollo Studio. First, click settings, then &quot;Edit Configuration&quot;, then change the &quot;Supergraph Pipeline Track&quot; to &quot;Federation 2.1 (default)&quot;. Finally, click &quot;Save&quot;." class="wp-image-19379" width="598" height="370"/></figure>



<h2 class="wp-block-heading"><a href="#livestreams-with-library-maintainers" aria-hidden="true" class="aal_anchor" id="livestreams-with-library-maintainers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Livestreams with library maintainers</h2>



<p>This week we kicked off a new livestream series in the <a rel="noreferrer noopener" href="https://discord.gg/graphos" target="_blank">Apollo GraphQL Discord</a> where maintainers and community experts demonstrate building subgraphs with different libraries and languages. To start, we built a subgraph live using Python and <a rel="noreferrer noopener" href="https://strawberry.rocks/" target="_blank">Strawberry</a>. Next up, we’ll do the same with Rust and <a rel="noreferrer noopener" href="https://async-graphql.github.io/async-graphql/en/index.html" target="_blank">async-graphql</a> on February 22. All of our livestreams are in <a rel="noreferrer noopener" href="https://discord.gg/graphos" target="_blank">Discord</a>, so make sure to join so you don’t miss out!</p>



<h2 class="wp-block-heading"><a href="#graphos-introduction-video" aria-hidden="true" class="aal_anchor" id="graphos-introduction-video"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphOS introduction video</h2>



<p>Your graph’s README page in <a rel="noreferrer noopener" href="https://studio.apollographql.com/" target="_blank">GraphOS Studio</a> now features a friendly introductory video and some handy links to help you get the most out of GraphOS from day one! Look for this section to the right of your README:<br></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="797" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2023/01/Screenshot-2023-01-19-at-2.51.27-PM-797x1024.png" alt="A screen shot of a section of Apollo Studio titled &quot;New to GraphOS Studio?&quot;. It says &quot;Check out a few quick tips and links from the Apollo team, designed to get you up and running.&quot; There is then a still of a video showing Apollo studio, followed by three links: &quot;Get to know your supergraph&quot;, &quot;Automate tasks with Rover CLI&quot;, and &quot;Build custom tools with the GraphOS Platform API&quot;." class="wp-image-19381" srcset="https://wp.apollographql.com/wp-content/uploads/2023/01/Screenshot-2023-01-19-at-2.51.27-PM-797x1024.png 797w, https://wp.apollographql.com/wp-content/uploads/2023/01/Screenshot-2023-01-19-at-2.51.27-PM-233x300.png 233w, https://wp.apollographql.com/wp-content/uploads/2023/01/Screenshot-2023-01-19-at-2.51.27-PM-768x987.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/01/Screenshot-2023-01-19-at-2.51.27-PM.png 856w" sizes="auto, (max-width: 797px) 100vw, 797px" /></figure>



<h2 class="wp-block-heading"><a href="#keeping-you-in-suspense" aria-hidden="true" class="aal_anchor" id="keeping-you-in-suspense"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Keeping you in suspense</h2>



<p>Can’t wait to use React 18’s Suspense feature when fetching data with your GraphQL queries? Try our new <code>useSuspenseQuery</code> hook today with <a rel="noreferrer noopener" href="https://www.npmjs.com/package/@apollo/client/v/3.8.0-alpha.5" target="_blank">Apollo Client 3.8.0-alpha.5</a>. Install it with <code>npm i @apollo/client@alpha</code>, then check out <a rel="noreferrer noopener" href="https://github.com/apollographql/apollo-client/issues/10231" target="_blank">the RFC</a> for more details. We can’t wait to hear your feedback!</p>



<h2 class="wp-block-heading"><a href="#rapid-roundup" aria-hidden="true" class="aal_anchor" id="rapid-roundup"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Rapid roundup</h2>



<p>Here are a few more changes and version updates you might want to check out:</p>



<ul class="wp-block-list">
<li><a href="https://github.com/apollographql/apollo-server/releases/tag/%40apollo%2Fserver%404.3.1" target="_blank" rel="noreferrer noopener">Apollo Server 4.3.1 was released with a few bug fixes</a></li>



<li><a href="https://github.com/apollographql/apollo-kotlin/releases/tag/v3.7.4" target="_blank" rel="noreferrer noopener">Apollo Kotlin 3.7.4 shipped with some minor improvements</a></li>



<li><a href="https://github.com/apollographql/apollo-client/releases/tag/v3.7.4" target="_blank" rel="noreferrer noopener">Apollo Client 3.7.4 squashed some bugs</a></li>



<li><a href="https://github.com/apollographql/apollo-ios/releases/tag/1.0.6">Apollo iOS 1.0.6 addressed some community requests and bugs </a></li>



<li><a rel="noreferrer noopener" href="https://github.com/apollographql/apollo-rs/releases/tag/apollo-compiler%400.6.0" target="_blank">apollo-compiler 0.6.0 brings API enhancements to your Rust code</a></li>



<li>All GraphOS <a rel="noreferrer noopener" href="https://www.apollographql.com/docs/graphos/routing/cloud" target="_blank">cloud supergraphs</a> have been updated to use version <a rel="noreferrer noopener" href="https://github.com/apollographql/router/releases/tag/v1.6.0" target="_blank">1.6.0</a> of the Apollo Router</li>



<li><a rel="noreferrer noopener" href="https://www.apollographql.com/docs/technotes/TN0029-relay-style-connections/" target="_blank">We’ve added an FAQ about Relay Connections</a> to our tech notes</li>



<li>You can now <a rel="noreferrer noopener" href="https://github.com/apollographql/hack-the-supergraph#deploy-to-railway-and-graphos" target="_blank">deploy our “Hack the Supergraph” example</a> to Railway with just a couple of clicks using a template</li>
</ul>



<h2 class="wp-block-heading"><a href="#performance-corner" aria-hidden="true" class="aal_anchor" id="performance-corner"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Performance corner</h2>



<p>Are you using data loaders in all of your graph’s resolvers? If you aren’t yet, learn all about <a rel="noreferrer noopener" href="https://www.apollographql.com/docs/federation/entities-advanced/#handling-the-n1-problem" target="_blank">handling the N+1 problem</a>.</p>



<p>That’s all for now! We’ll be back soon with another update. In the meantime, <a href="https://discord.gg/graphos" target="_blank" rel="noreferrer noopener">join our Discord server</a> to stay up to date with future programs and announcements. That’s also where you can give us feedback on this new format and request changes or additions. Happy querying!</p>


Apollo Changelog: Jan 23, 2023


<p>Since the rise of the frontend framework and the framework wars of the 2010s, we’ve all gotten pretty used to the idea of building single-page apps that load a JavaScript bundle and then send queries to a server dynamically as a user clicks around. The move to single-page apps was driven by the need to create faster, more interactive user experiences.</p>



<p>As with every great innovation, solving one problem just opens your eyes to the next one. As we all settled into the new normal of building apps with UI frameworks, the next major challenge presented itself: data fetching. Over the last 6 years, GraphQL has once again innovated on the frontend developers&#8217; experience, bringing UI-driven API design, automatic state management, strong types, and much more to the world of building interfaces.</p>



<p>And as someone who’s been building apps with GraphQL for a while, there’s one major ergonomic thing that has bothered me all that time: the relationship between queries and component structure. It’s common to create symmetry between the shape of a GraphQL query and the data that’s rendered in a UI component, but up until now, there has been no way to decouple the query itself from the importance of each field it holds. If you want some fields to load faster than others, or you know there’s a slow field and you don’t want your whole query’s response to be held up, you have to split those into multiple queries. This creates a lot of spaghetti code in components; something simple from a UI and schema design perspective just got complicated due to server implementation.</p>



<p>This isn’t a GraphQL problem–we had it with REST too–but GraphQL is uniquely positioned to solve it because we can annotate each field with metadata!</p>



<p><strong>Introducing, <code>@defer</code></strong></p>



<p>&nbsp;<code>@defer</code> is a directive you can add to queries that will tell your server it can respond to this query in multiple parts. Do you know a particular field is slow? Defer it! This means your server can respond with an initial response to your end-user much faster and fill in the rest when it gets there.</p>



<p>For the last several months, we’ve been working to support <code>@defer</code> across the Apollo stack, and today we’re excited to announce full supergraph support for&nbsp;<code>@defer</code> in GraphOS.<em> </em>You don&#8217;t even need to make any changes to your existing GraphQL API to use it, <em>it just works</em>.</p>



<h2 class="wp-block-heading"><a href="#using-defer-with-your-existing-graphql-api" aria-hidden="true" class="aal_anchor" id="using-defer-with-your-existing-graphql-api"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Using <code>@defer</code> with your existing GraphQL API</strong></h2>



<p>To use <code>@defer</code>, you just need to have a supergraph router between your GraphQL server and your client (even if you only have one GraphQL server that isn’t using Apollo Federation). The easiest way to create a router is to set up a free serverless instance of Apollo Router with <a href="https://apollographql.com/graphos/">Apollo GraphOS</a>. You can also use <a href="https://www.apollographql.com/docs/rover">Rover</a>, the GraphOS CLI, to start up a local instance of the router. <code>@defer</code> can be used on the root <code>Query</code> field and the router will break the query into multiple GraphQL requests. We can test this out using <strong>any</strong> GraphQL endpoint and <code>rover dev</code>.</p>



<p>In this post, we will use the SpaceX API to see how this works. Remember, the SpaceX example <em>does not</em> use Apollo Federation. First, we use the <code>rover dev</code> command to start up a local instance of the router pointing at <a href="https://spacex-production.up.railway.app/">https://spacex-production.up.railway.app/</a>:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash">rover dev --name=spacex --url=https://spacex-production.up.railway.app/</code></pre>



<p>Now you can open up <a href="http://localhost:3000">http://localhost:3000</a> and try executing a query using <code>@defer</code> on the root <code>Query</code>:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">query Launches {
  launches {
    id
    details
    rocket {
      rocket_name
    }
  }
  ... @defer {
    deferredLaunchDetails: launches {
      id
      upcoming
    }
  }
}</code></pre>



<p>Notice we&#8217;re aliasing the root query field to isolate a single field. An upgraded query planner instructs the router to fetch the deferred portions of a query:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="726" height="512" src="https://wp.apollographql.com/wp-content/uploads/2023/01/spacex-defer-queryplan.png" alt="A Query Plan showing two fetch requests to the SpaceX API where one fetch is being deferred" class="wp-image-19235" srcset="https://wp.apollographql.com/wp-content/uploads/2023/01/spacex-defer-queryplan.png 726w, https://wp.apollographql.com/wp-content/uploads/2023/01/spacex-defer-queryplan-300x212.png 300w" sizes="auto, (max-width: 726px) 100vw, 726px" /></figure>



<p>We can see that the generated query plan shows the router breaking our query into two requests to the SpaceX GraphQL API. Now you can <code>@defer</code> any field in your current API without making any changes 🚀</p>



<h2 class="wp-block-heading"><a href="#using-defer-on-any-entity-in-the-supergraph" aria-hidden="true" class="aal_anchor" id="using-defer-on-any-entity-in-the-supergraph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Using <code>@defer</code> on any Entity in the supergraph</strong></h2>



<p>When <a href="https://www.apollographql.com/docs/federation/entities/">entities</a> are used in the supergraph, they define an additional execution boundary for the deferred portions of a query with additional benefits like being able to <code>@defer</code> on nested fragments within a single root query.</p>



<p>Entities in the supergraph are traditionally used to split the implementation of an entity into multiple subgraph modules for a better <a href="https://www.apollographql.com/docs/federation/#separation-of-concerns">separation of concerns</a>. The supergraph router can then perform API-side joins by fetching the entity data from individual subgraphs and flattening the results into the requested query shape.</p>



<p>Since the Router uses the existing <a href="https://www.apollographql.com/docs/federation/subgraph-spec/">subgraph specification</a> supported in <a href="https://www.apollographql.com/docs/federation/supported-subgraphs/">over 24 languages and frameworks</a>, app developers can start using <code>@defer</code> in their client queries without any backend changes to existing subgraphs.</p>



<p>In this post, we&#8217;re going to use the <a href="https://github.com/apollographql/hack-the-supergraph">Apollo Hack the Supergraph demo</a> for the hosted subgraphs. We&#8217;ll still use <code>rover dev</code> to try this out. In separate terminal windows, start a rover dev session for these subgraphs:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-bash">rover dev --name=products --url=https://hts-products-production.up.railway.app/

# In a new terminal window
rover dev --name=reviews --url=https://hts-reviews-production.up.railway.app/</code></pre>



<p>Now you can open up <a href="http://localhost:3000">http://localhost:3000</a> and try executing a query using <code>@defer</code> on the product reviews:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-">fragment ProductReviewsFragment on Product {
  reviews {
    content
  }
}

query ExampleQuery {
  products {
    id
    title
    description
    price {
      amount
    }
    ...ProductReviewsFragment @defer
  }
}</code></pre>



<p>You should see the <code>data.products.reviews</code> be deferred in the response and query plan:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1918" height="834" src="https://wp.apollographql.com/wp-content/uploads/2023/01/@defer-gif.gif" alt="" class="wp-image-19289"/></figure>



<h2 class="wp-block-heading"><a href="#start-using-defer-today" aria-hidden="true" class="aal_anchor" id="start-using-defer-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Start using <code>@defer</code> today</strong></h2>



<p>The easiest way to get started with the Apollo Router is to <a href="https://www.apollographql.com/docs/graphos/quickstart/cloud">create a serverless instance</a> with <a href="https://studio.apollographql.com/signup?referrer=blog">GraphOS</a>. Once you&#8217;ve added your existing GraphQL API in GraphOS, you&#8217;ll need to be on the latest version of Apollo Client (<a href="https://www.apollographql.com/docs/react/data/defer/">React</a>, <a href="https://www.apollographql.com/docs/kotlin/fetching/defer/">Kotlin</a>, <a href="https://github.com/apollographql/apollo-ios/issues/2395">iOS support coming soon</a>). That&#8217;s it, you can start using <code>@defer</code> in your apps 🎉.</p>



<p>Want to dig deeper into <code>@defer</code> and GraphOS? <a href="https://discord.gg/graphos">Join our Discord</a> to continue the discussion! We’ll be live streaming about this topic and more!</p>


Rethinking React components with @defer


<p><em>Apollo CEO Geoff Schmidt sent the following note to Apollo employees:</em></p>



<p>I have some difficult news to share. Today, we’re reducing the size of our team by approximately 15% and saying goodbye to some talented colleagues. Those who are leaving have already been notified as we wanted them to hear the news through a personal conversation wherever possible. We are providing them with a separation package that includes at least 15 weeks of base pay and other support I’ll detail below.</p>



<p>I am very sad to make this decision. It’s a consequence of the approach that Matt and I took in scaling the company over the last year, and we take full responsibility for the impact that will have on the lives of our departing team members. Please know that we carefully analyzed and considered many other options before making this painful decision.</p>



<h2 class="wp-block-heading"><a href="#why-we-made-this-decision" aria-hidden="true" class="aal_anchor" id="why-we-made-this-decision"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Why we made this decision</strong></h2>



<p>Our business has grown dramatically over the last year and the supergraph now powers many of the products and services we use every day. But we are not yet profitable: we’ve taken full advantage of outside capital to speed our growth. That was good stewardship in a time when interest rates were low and venture capital was widely available on good terms. But economic conditions have changed and we believe that it’s no longer prudent to rely on outside capital to support us (and the Apollo community) in the long term. While we are already well capitalized, this difficult decision today puts the company in a strong position to become profitable without any further outside investment.</p>



<p>I must also acknowledge, though, that macroeconomic changes aren’t the only reason for today’s changes. Seeking to bring supergraph technology to every app developer, Matt and I made the decision to grow the company very quickly. Thanks to an incredible performance by our Talent Acquisition team, one of the best in the industry, we grew headcount 2.5x in about a year. But the problem is that growing the company 2.5x didn’t make us 2.5x more productive. It got harder to get things done because we didn’t add the right mix of skills and seniority levels to our team. As CEO, this mistake is my responsibility, and the root cause was setting a growth rate that was just too fast for us to sustain efficiently.</p>



<p>Though these changes are painful, they leave our company on firm ground. They refocus us on what matters most: giving our users and customers what they want, as efficiently as possible. And they mean that we can protect our independence, and serve our open source community, no matter what economic storms may come in the next few years.</p>



<h2 class="wp-block-heading"><a href="#supporting-our-departing-colleagues" aria-hidden="true" class="aal_anchor" id="supporting-our-departing-colleagues"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Supporting our departing colleagues</strong></h2>



<p>While our obligation to be good stewards of the supergraph is always top of mind, we have an equally important obligation to take care of our departing team members. Here is what we are doing to support them in their transition to new roles:</p>



<ol class="wp-block-list">
<li><strong>Severance pay:</strong> All departing employees are eligible for 15 weeks of base pay (through March 31), plus an additional week of pay per year of service.</li>



<li><strong>Health benefits: </strong>We’ll pay six months of COBRA coverage reimbursement for US employees and $300 towards any mental healthcare.</li>



<li><strong>Equity: </strong>We’re dropping the one-year cliff on option grants and extending the ability to exercise options through Dec. 31, 2023.</li>



<li><strong>Immigration support:</strong> We know this situation is particularly tough for visa holders, so we have dedicated support for those employees.</li>



<li><strong>Career support:</strong> We’ll connect our affected colleagues with new opportunities through our alumni support program.</li>



<li><strong>Equipment:</strong> To help with job searches, we won’t ask for the return of laptops (and any other office gear Apollo provided).</li>
</ol>



<p>What makes this an especially sad day is how deeply committed these departing colleagues have been to Apollo and our community. We are very grateful for their service. I regret this ending to our journey together, and Matt and I take full responsibility for the decisions that led to it.</p>



<h2 class="wp-block-heading"><a href="#going-forward" aria-hidden="true" class="aal_anchor" id="going-forward"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Going forward</strong></h2>



<p>Today, we’ll have a company all-hands at 1:00 PT to discuss the changes together. Tomorrow, we’ll host our usual AMA session at 9:30 PT. I know you will have many good questions, and we’ll extend the AMA so that we can answer as many as possible. While this week won’t be business as usual, I’m confident in our team’s resilience as we adjust to these changes and gear up for 2023.&nbsp;</p>



<p>While the changes today are hard for everyone, I know we’re in a solid position thanks to our hard work over the past year. Downloads of our open-source frameworks crossed the half-billion mark. Federation, the industry’s standard open architecture for graph composition, is now supported by 27 languages and frameworks. From Black Friday through Cyber Monday, the supergraph served over 110 billion queries with no downtime. Thousands of the world’s largest enterprises have adopted Apollo, with our enterprise business growing over 100% year over year with best-in-class retention and expansion. Thank you to our team, community, and customers for getting us to this point. Helping you do great things will continue to be our focus.</p>



<p>Geoff and Matt</p>


CEO Geoff Schmidt’s message to Apollo employees


<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p>Update: The EOL timeline for Apollo Server 3 has been <a href="https://www.apollographql.com/blog/apollo-server-3-end-of-life-extension" data-type="link" data-id="https://www.apollographql.com/blog/apollo-server-3-end-of-life-extension">extended to October 2024</a></p>
</blockquote>



<p>Last week we officially launched Apollo Server 4! AS4 is lightweight and easier to use than any previous iteration of Apollo Server. We are sure that you’ll love it, and we are excited to help you <a href="https://www.apollographql.com/docs/apollo-server/v4/getting-started">get started with it from scratch</a> or <a href="https://www.apollographql.com/docs/apollo-server/migration/">migrate</a> from a previous version.</p>



<p>With Apollo Server 4 now generally available, <strong>Apollo Server versions 2 and 3 are now officially deprecated</strong> and will reach their <strong>final end of life on October 22, 2023</strong>. </p>



<p>Additionally, <strong>the subscriptions, uploads, and Playground features of Apollo Server 2 will have an earlier end-of-life on December 31, 2022</strong>.&nbsp;</p>



<p>Apollo will continue to provide security patches and fixes for major regressions until October 2023, after which Apollo Server 2 and 3 will no longer be maintained by Apollo. <strong>Note:</strong> After December 31, 2022, Apollo will only continue to evaluate security issues and major regressions in Apollo Server 2 that persist with `{ subscriptions: false, playground: false, uploads: false }`.</p>



<p>If you are currently using Apollo Server 2 or 3, you can find details about migrating to Apollo Server 4 in <a href="https://www.apollographql.com/docs/apollo-server/migration">this guide</a>.</p>



<p>For more information about Apollo’s software lifecycle policies and an up-to-date list of actively maintained software versions,&nbsp; please consult the <a href="https://www.apollographql.com/docs/resources/product-launch-stages/">documentation</a>.</p>


Announcing the end-of-life schedule for Apollo Server 2 & 3


<p>With <a href="https://www.apollographql.com/docs/router/">Apollo Router v1.x</a> being rapidly adopted as our next-generation <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">supergraph</a> runtime and Apollo Gateway v2.x and Federation 2 <a href="https://www.apollographql.com/blog/announcement/backend/apollo-federation-2-is-now-generally-available/">being GA for over 7 months</a>, Apollo Gateway v0.x is now officially <a href="https://www.apollographql.com/docs/resources/product-launch-stages/#deprecated">deprecated</a> and will reach its <a href="https://www.apollographql.com/docs/resources/product-launch-stages/#end-of-life">end-of-life</a> on <strong>September 22, 2023</strong>.<br><br>As of today, <strong>Apollo Gateway v0.x</strong> is no longer under active development. We will, however, continue to release security patches and fixes for major regressions until September 2023, after which Apollo Gateway v0.x will <strong>no longer be supported or maintained by Apollo</strong>.&nbsp;</p>



<p>We recommend <a href="https://www.apollographql.com/docs/router/migrating-from-gateway/">migrating to Apollo Router</a> today for its significant performance gains and capabilities. <a href="https://www.apollographql.com/blog/announcement/backend/announcing-apollo-router-v1-0/"><strong>Apollo Router 1.x</strong></a> is the re-platforming of the Gateway offering <a href="https://www.apollographql.com/blog/announcement/backend/apollo-router-our-graphql-federation-runtime-in-rust/">10x better performance</a>, enhanced security, and many built-in capabilities like cors, logging, telemetry, and traffic shaping that can be <a href="https://www.apollographql.com/docs/router/configuration/overview#yaml-config-file">configured declaratively with YAML</a> rather than with Javascript code. Optionally, the Router can be customized with Rhai scripts and native Rust plugins for advanced use cases. Our roadmap for the router includes new features like entity-based <code>@defer</code> support (now in preview), <a href="https://www.apollographql.com/events/virtual-event/graphql-summit-october-2022/the-future-of-real-time-data-in-graphql/">live queries</a>, authorization, caching, demand control, and much more.</p>



<p>If you are unable to migrate to the Router, <strong>Apollo Gateway 2.x </strong>is a drop-in upgrade from Gateway 0.x. Plugins and middleware written for 0.x will work unmodified in Gateway 2.x. Most future feature development will be focused on Apollo Router, so we would love to understand any obstacles you encounter migrating to it. Please <a href="https://github.com/apollographql/router/discussions">open a discussion on GitHub</a> if you need general help or <a href="https://github.com/apollographql/router/issues">open an issue</a> if you have any troubles!</p>


Announcing the end-of-life schedule for Apollo Gateway v0.x


<p>Apollo Server 4 is a lightweight, open-source, spec-compliant GraphQL server that’s compatible with any GraphQL client. It’s a great choice for building a production-ready, self-documenting GraphQL API that can use data from any source. You can use Apollo Server 4 as a subgraph in a federated Supergraph or as a stand-alone GraphQL server.</p>



<p>Apollo Server 4 introduces the <code>@apollo/server</code> package which decouples plugins and frameworks from the core of Apollo Server. It offers a stable API for HTTP and serverless frameworks, enabling users to build Apollo Server integrations for their framework of choice. Apollo Server 4 also introduces a TypeScript-first development and documentation experience to help you build typesafe servers using a schema-first development process.</p>



<p>Apollo Server 4 is generally available! You can <a href="https://www.apollographql.com/docs/apollo-server/v4/getting-started">get started from scratch</a> or <a href="https://www.apollographql.com/docs/apollo-server/v4/migration">migrate from an older version</a> today!</p>



<h2 class="wp-block-heading"><a href="#a-dedicated-api-for-http-and-serverless-framework-integrations" aria-hidden="true" class="aal_anchor" id="a-dedicated-api-for-http-and-serverless-framework-integrations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>A dedicated API for HTTP and Serverless framework integrations</h2>



<p>A strength and a challenge of the JavaScript/TypeScript ecosystem is how many different options there are available to solve any problem. For example, there are dozens of popular web frameworks to choose between when setting up an HTTP server. There are also many serverless environments like AWS Lambda and Google Cloud Functions that each have their own APIs for handling HTTP requests. We want Apollo Server to work with as many of them as possible.</p>



<p>In previous versions of Apollo Server, there wasn’t a well-defined API layer between the “core” of Apollo Server and the individual framework integrations. Many features of Apollo Server were implemented as logic which had to be repeated in each integration, but often in slightly different, framework-specific ways. Improving any of these features often meant changing framework-specific code in 9 different packages.</p>



<p>For Apollo Server 4, we defined simple portable data structures for HTTP requests and responses, and we rewrote Apollo Server to act on these representations. Apollo Server now has a stable API for building framework integrations, which now usually consist of a dozen or so lines of code that convert between the request and response objects of the framework and Apollo Server. AS4 also has native support for serverless framework lifecycles, and serverless integrations now use a dedicated API during the server startup sequence to execute operations.</p>



<h3 class="wp-block-heading"><a href="#using-and-contributing-to-integrations" aria-hidden="true" class="aal_anchor" id="using-and-contributing-to-integrations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Using and contributing to integrations</h3>



<p>The Apollo Server 4 core project ships with a core-maintained integration for the most popular Node web framework (Express) as well as a simple standalone web server for when you don’t need to configure much.&nbsp;</p>



<p>We’ve <a href="https://github.com/apollo-server-integrations">set up infrastructure</a> to help our community build and maintain integrations, such as with <a href="https://github.com/apollo-server-integrations/apollo-server-integration-aws-lambda">AWS Lambda</a>, <a href="https://github.com/apollo-server-integrations/apollo-server-integration-fastify">Fastify</a>, and <a href="https://github.com/apollo-server-integrations/apollo-server-integration-koa">Koa</a>. Community members have also already built integrations with new environments such as <a href="https://github.com/apollo-server-integrations/apollo-server-integration-h3">H3</a> and <a href="https://github.com/apuyou/apollo-server-nextjs">Next.JS</a> that were never before supported by Apollo Server. Because building integrations require less domain-specific implementation, framework experts and integration authors can build integrations for their framework of choice and add those integrations to our <a href="https://github.com/apollo-server-integrations">Apollo Server integrations GitHub organization</a>.</p>



<p>Additionally, because integrations are now maintained independently from Apollo Server, it will be much easier to update your framework to take advantage of new features in your web framework of choice. We are always looking to add new framework integrations, so if you don’t see <a href="https://github.com/apollo-server-integrations">an integration</a> you’d like to use, create an issue on <a href="https://github.com/apollographql/apollo-server/issues">GitHub</a>. If you specialize in any of <a href="https://github.com/apollographql/apollo-server/labels/integration-collaborators">these frameworks</a> and are interested in building or maintaining an AS4 integration, please reach out!</p>



<h2 class="wp-block-heading"><a href="#simpler-package-structure-and-reduced-bundle-size" aria-hidden="true" class="aal_anchor" id="simpler-package-structure-and-reduced-bundle-size"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Simpler package structure and reduced bundle size</h2>



<p>Apollo Server 3 was structured as a large number of distinct packages for each framework integration. For example, Express users used the <code>apollo-server-express</code> package while Fastify users used the <code>apollo-server-fastify</code> package. Other functionality involved depending on one of a wide array of smaller packages, and it was challenging to ensure you used a consistent version across these packages. Apollo Server 4 simplifies this situation by combining all of the core code into a single new <code>@apollo/server</code> package.</p>



<p>Unlike Apollo Server 3, the Apollo Server 4 package is also published in both CJS and ESM formats! The ECMAScript Module format improves upon the CommonJS (CJS) format pioneered by Node. Modern build tools can better optimize packages built as ESM, resulting in reduced bundle size. Smaller, optimized bundles allow serverless runtimes like AWS Lambda to start up faster.&nbsp;</p>



<p>Because AS4 is published in both formats, you get the improved efficiency of ESM if you use a newer build tool without losing compatibility with older build environments that only support CJS.To learn more about the difference between ESM and CJS and their interoperability, check out the <a href="https://nodejs.org/api/esm.html#differences-between-es-modules-and-commonjs">Node.js documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#avoid-resolver-type-and-schema-mismatches" aria-hidden="true" class="aal_anchor" id="avoid-resolver-type-and-schema-mismatches"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Avoid resolver type and schema mismatches</h2>



<p>With the release of Apollo Server 4, we’ve updated all of <a href="https://www.apollographql.com/docs/apollo-server/">our documentation</a> to show a TypeScript-first approach and recommend Typescript as the default way to build with Apollo Server.</p>



<p>When using Apollo Server 3, there was no way to specify the type of your context value when setting up your server. This led to typing inconsistencies because there was no compile-time check ensuring the type returned by your context function matched the value in your plugins and resolvers.</p>



<p>Apollo Server 4 enables you to write code that can statically check that your resolver types match their schema types, using a schema-first approach. To do this, Apollo Server documents the use of the <code>graphql-code-generator</code> package with typescript-resolvers to ensure server implementations are type-safe. To get started or learn more about generating types from your schema, check out <a href="https://www.apollographql.com/docs/apollo-server/workflow/generate-types">our documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#getting-started-with-apollo-server-4" aria-hidden="true" class="aal_anchor" id="getting-started-with-apollo-server-4"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Getting started with Apollo Server 4</strong></h2>



<p>We’re excited for you to start using Apollo Server 4 and all of its new features!</p>



<p>If you’re starting from scratch, our <a href="https://www.apollographql.com/docs/apollo-server/v4/getting-started">getting started docs</a> will walk you through setting up Apollo Server for the first time, or if you’re already using Apollo Server 3, our <a href="https://www.apollographql.com/docs/apollo-server/v4/migration">migration guide</a> will help you upgrade. We would love your feedback on Apollo Server 4 and its framework integrations! You can do so by reaching out on <a href="https://community.apollographql.com">our community forum</a> or <a href="https://github.com/apollographql/apollo-server">GitHub</a>.</p>


Apollo Server 4: a lightweight and easier-to-use Apollo Server


<p>The Apollo team is still feeling the energy from spending three days in San Diego with over 1000 developers and engineering leaders. And, to the thousands of remote attendees, thank you. We are glad you were able to join in the action via Livestream! Summit participants attended workshops, panels, and sessions on all things GraphQL with a focus on how to successfully build supergraphs.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="614" src="https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Backdrop-1024x614.jpg" alt="" class="wp-image-17098" srcset="https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Backdrop-1024x614.jpg 1024w, https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Backdrop-300x180.jpg 300w, https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Backdrop-768x460.jpg 768w, https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Backdrop-1536x921.jpg 1536w, https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Backdrop-1200x719.jpg 1200w, https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Backdrop.jpg 1920w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p></p>



<p>Monday was about helping teams level up their GraphQL skills with workshops focused on production best practices, schema design, Apollo Federation, and how to champion the supergraph. </p>



<figure class="wp-block-image size-large is-resized"><img loading="lazy" decoding="async" src="https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Conference-Hall-1024x645.jpg" alt="" class="wp-image-17090" width="610" height="384" srcset="https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Conference-Hall-1024x645.jpg 1024w, https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Conference-Hall-300x189.jpg 300w, https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Conference-Hall-768x484.jpg 768w, https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Conference-Hall-1536x967.jpg 1536w, https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Conference-Hall-1200x756.jpg 1200w, https://wp.apollographql.com/wp-content/uploads/2022/10/GraphQL-Summit-Conference-Hall.jpg 1920w" sizes="auto, (max-width: 610px) 100vw, 610px" /><figcaption>GraphQL Summit 2022: Right before Tuesday Keynote</figcaption></figure>



<p>On Tuesday, Matt DeBergalis, CTO at Apollo GraphQL, kicked us off with a keynote announcing Apollo GraphOS and the new features we are launching. (Read on to learn what we launched at GraphQL Summit.) Attendees then split up across the GraphQL Summit pavilion to join compelling sessions from companies like Netflix, Fidelity, Wayfair, and Pinterest.  Marc-André Giroux from Netflix’s talk on Building Great GraphQL Developer Experiences @ Scale was packed with insight on how Netflix helps build solutions to empower 100s of developers to collaborate on their supergraph.  Attendees also raved about the practical advice for protecting your GraphQL API in Nick Aleks and Dolev Farhi’s talk on Offensive GraphQL Security Testing. Sam Scott from Oso’s talk Authorization Patterns in GraphQL and Ash Narcisse from Apollo’s Root of Auth things talks came in with high remarks from attendees. Tuesday&#8217;s closing keynote, How a Supergraph Powers The Front Page of the Internet, was by Reddit’s Savannah Forood and Jameson Williams. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="533" src="https://wp.apollographql.com/wp-content/uploads/2022/10/Ananya-Roy-Netflix-Stranger-Graphs-1024x533.jpg" alt="" class="wp-image-17116" srcset="https://wp.apollographql.com/wp-content/uploads/2022/10/Ananya-Roy-Netflix-Stranger-Graphs-1024x533.jpg 1024w, https://wp.apollographql.com/wp-content/uploads/2022/10/Ananya-Roy-Netflix-Stranger-Graphs-300x156.jpg 300w, https://wp.apollographql.com/wp-content/uploads/2022/10/Ananya-Roy-Netflix-Stranger-Graphs-768x400.jpg 768w, https://wp.apollographql.com/wp-content/uploads/2022/10/Ananya-Roy-Netflix-Stranger-Graphs-1536x800.jpg 1536w, https://wp.apollographql.com/wp-content/uploads/2022/10/Ananya-Roy-Netflix-Stranger-Graphs-1200x625.jpg 1200w, https://wp.apollographql.com/wp-content/uploads/2022/10/Ananya-Roy-Netflix-Stranger-Graphs.jpg 1920w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>Ananya Roy from Netflix spoke about how Netflix Studios use the supergraph</figcaption></figure>



<p></p>



<p>After a great day of sessions, we all gathered at Stone Brewing for the ultimate Graph &amp; Brew networking event, complete with karaoke. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="562" src="https://wp.apollographql.com/wp-content/uploads/2022/10/Stone-Brewing-Graph-Brew-Party-1024x562.jpg" alt="" class="wp-image-17101" srcset="https://wp.apollographql.com/wp-content/uploads/2022/10/Stone-Brewing-Graph-Brew-Party-1024x562.jpg 1024w, https://wp.apollographql.com/wp-content/uploads/2022/10/Stone-Brewing-Graph-Brew-Party-300x165.jpg 300w, https://wp.apollographql.com/wp-content/uploads/2022/10/Stone-Brewing-Graph-Brew-Party-768x422.jpg 768w, https://wp.apollographql.com/wp-content/uploads/2022/10/Stone-Brewing-Graph-Brew-Party-1536x843.jpg 1536w, https://wp.apollographql.com/wp-content/uploads/2022/10/Stone-Brewing-Graph-Brew-Party-1200x659.jpg 1200w, https://wp.apollographql.com/wp-content/uploads/2022/10/Stone-Brewing-Graph-Brew-Party.jpg 1920w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>The scene from Graph &amp; Brew at Stone Brewing</figcaption></figure>



<p></p>



<p>Apollo’s Ben Newman gave Wednesday’s keynote on The Future of Real-time Data with GraphQL, followed by compelling sessions from companies including Stripe, Expedia, Block, and TV2 Denmark. Attendees also called out Max Goodings’ talk, 7 Tips For Writing Better Resolvers, as providing concrete best practices on writing hundreds or thousands of resolvers. Two members of Walmart’s Global Tech team, Aditya Bakle and Ben Wilson, closed GraphQL Summit with the story of how they completely redesigned all of their digital properties using the supergraph in less than a year. </p>



<p></p>



<h2 class="wp-block-heading"><a href="#product-announcements" aria-hidden="true" class="aal_anchor" id="product-announcements"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Product announcements</strong></h2>



<h2 class="wp-block-heading"><a href="#graphos" aria-hidden="true" class="aal_anchor" id="graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphOS</h2>



<p>Tuesday morning, we introduced Apollo GraphOS, a complete cloud platform that lets anyone build, connect, and scale any supergraph. There are three key components of GraphOS:&nbsp;</p>



<ol class="wp-block-list"><li><strong>A global supergraph run-time</strong> that is either hosted by Apollo or Enterprise users can self-host using Apollo Router</li><li><strong>A schema delivery pipeline</strong> that includes a schema registry, observability, and schema validation to prevent downtime</li><li><strong>A supergraph development kit </strong>a set of tools that give you a complete supergraph development environment on your laptop</li></ol>



<p>GraphOS delivers advanced capabilities like @defer out of the box. @defer lets you mark slow parts of your query and tell the graph it can deliver those parts asynchronously, allowing teams to build more responsive, faster experiences.</p>



<p>Summit attendees could test out GraphOS at the supergraph stations across the venue.</p>



<p>Learn more about GraphOS <a href="https://www.apollographql.com/graphos/">here</a>.</p>



<p><strong>Our supergraph development kit&nbsp;</strong></p>



<p>The supergraph development kit is a set of tools that lets you spin up a complete supergraph development environment on your laptop powered by Apollo Router. New Rover templates in popular programming languages allow new teams to onboard to the graph faster, by providing the skeleton for building out subgraphs.</p>



<p>Learn more about GraphOS and the supergraph development kit <a href="https://www.apollographql.com/blog/announcement/platform/introducing-apollo-graphos/">here</a>.</p>



<p><strong>A peek into supergraph linking</strong></p>



<p>In Tuesday&#8217;s keynote, Matt previewed supergraph linking. The supergraph is a powerful way to allow independent teams within an organization to collaborate on a shared API. However, when organizations need to build experiences that require capabilities from other companies, this often results in writing tedious wrapping code around 3rd party APIs. The current approach creates a risk of experiences breaking if any underlying APIs change.&nbsp;</p>



<p>Matt showcased our conceptual approach to linking multiple supergraphs that would allow organizations to share capabilities more efficiently. Martijn Walraven went into more depth during his session, The Future of the Supergraph. He discussed how namespacing, dynamic schema composition, and multi-level routing could be used to build supergraph linking.</p>



<p><strong>Real-time data proposal</strong></p>



<p>For monolithic graphs, subscriptions are the most common approach for providing real-time data to GraphQL clients. However, implementing real-time solutions in federated graphs is challenging. As part of Wednesday&#8217;s opening keynote, Ben Newman, Apollo Open-Source Architect, proposed a real-time data protocol for federated graphs using @live directive and cursor-based query revalidation and diffing.</p>



<p></p>



<p>Watch the recap on demand and check out the slides from the talk. (<em>Interested in helping shape our approach? We&#8217;re also looking for feedback. </em><a href="https://bit.ly/real-time-graphql"><em>Take the survey here</em></a><em>.)&nbsp;</em></p>



<p><strong>Thank you to our GraphQL Summit Sponsors</strong></p>



<p>Our sponsors helped make GraphQL Summit an even more engaging experience with compelling talks and workshops from MongoDB, Grid Dynamics, Xolvio, Oso, and Moon Highway, along with experiences curated by Bethink Labs and Metronome. Visit the link below to hear their talks.&nbsp;</p>



<p><strong>Puppies at GraphQL Summit</strong></p>



<p>One last thing, we would be remiss not to post that puppies were in attendance at GraphQL Summit. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="678" src="https://wp.apollographql.com/wp-content/uploads/2022/10/Puppies-at-GraphQL-Summit-1024x678.jpg" alt="" class="wp-image-17095" srcset="https://wp.apollographql.com/wp-content/uploads/2022/10/Puppies-at-GraphQL-Summit-1024x678.jpg 1024w, https://wp.apollographql.com/wp-content/uploads/2022/10/Puppies-at-GraphQL-Summit-300x199.jpg 300w, https://wp.apollographql.com/wp-content/uploads/2022/10/Puppies-at-GraphQL-Summit-768x509.jpg 768w, https://wp.apollographql.com/wp-content/uploads/2022/10/Puppies-at-GraphQL-Summit-1536x1018.jpg 1536w, https://wp.apollographql.com/wp-content/uploads/2022/10/Puppies-at-GraphQL-Summit-1200x795.jpg 1200w, https://wp.apollographql.com/wp-content/uploads/2022/10/Puppies-at-GraphQL-Summit.jpg 1920w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p></p>



<p><strong>Looking to relive key moments or attend sessions you missed? We&#8217;re gonna be posting these sessions over the upcoming weeks. Watch the keynote </strong><a href="https://www.apollographql.com/events/virtual-event/opening-keynote-with-matt-debergalis-cto-cofounder/" data-type="URL" data-id="https://www.apollographql.com/events/virtual-event/opening-keynote-with-matt-debergalis-cto-cofounder/"><strong>on-demand now.</strong></a></p>


GraphQL Summit 2022 Recap: Highlights, Product Announcements, and Puppies


<p>As of today, you can now use our new public API to integrate with the Apollo GraphOS platform.</p>



<p>We built this API to enable those using GraphOS to easily automate operations in their own systems and CI workflows. In fact, this is the same API that the <a href="https://www.apollographql.com/docs/rover/">Rover CLI</a> uses to run schema checks and publish schemas to Apollo Studio.</p>



<p>Under the hood, the GraphOS platform API uses schema <a href="https://www.apollographql.com/blog/announcement/platform/contracts-are-now-generally-available/">contracts</a> to make our private platform API publicly available. By creating a contract, we can filter out the necessary subset of our private platform API schema, all the while keeping the public schema in sync with the source.</p>



<p>See the <a href="https://studio.apollographql.com/public/apollo-platform/home?variant=main">API’s readme</a> to get started, and check out the operation collections in Explorer to see example GraphQL queries and mutations you can use for your own graphs.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#take-the-api-for-a-spin" aria-hidden="true" class="aal_anchor" id="take-the-api-for-a-spin"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Take the API for a spin</h2>



<p>So, let’s try it out! We’ve embedded the API’s Explorer from Studio below. (Yes, you can <a href="https://www.apollographql.com/docs/studio/explorer/embed-explorer/">embed the Explorer</a> for any of your graphs managed in Studio!)&nbsp;</p>



<p>Here are some examples of what you can do with the GraphOS platform API:</p>



<ul class="wp-block-list"><li>Retrieve a list of your GraphQL supergraphs</li><li>Fetch a graph for a specific environment (such as staging)</li><li>Publish your supergraph’s schema</li><li>Check your supergraph’s schema for errors</li></ul>



<p>Note: Some of these operations, like publishing a new graph, require that you set your own Studio API key. See the <a href="https://studio.apollographql.com/public/apollo-platform/home?variant=main">readme</a> for instructions.&nbsp;<br>Check out our operations collections and try running some queries, read the API’s inline documentation, or see the <a href="https://studio.apollographql.com/public/apollo-platform/schema/reference?variant=main">schema reference</a> to view all the API’s types and fields:</p>



<div style="width: 100%; height: 500px;" id="embedded-explorer"></div>
<script src="https://embeddable-explorer.cdn.apollographql.com/_latest/embeddable-explorer.umd.production.min.js"></script> 
<script>
  new window.EmbeddedExplorer({
    target: '#embedded-explorer',
    graphRef: 'apollo-platform@main',
    persistExplorerState: true,
    initialState: {
      document: ` # Fetches basic details about a single Studio graph
# by its ID.
#
# By default, this fetches details for the
# apollo-platform graph and its main variant, 
# which you're currently querying! You can provide a 
# different graph ID in the Variables panel.
#
# ⚠️ If you provide a non-public graph ID, you
#    need to provide a valid API key in the
#    X-API-KEY header!
query GetGraph($graphId: ID!, $name: String!) {
  graph(id: $graphId) {
    id
    title
    myRole # Null if querying a public graph anonymously
    variant(name: $name) {
      id
      url
    }
  }
}`,
      variables: {
  "graphId": "apollo-platform",
  "name": "main"
},
      headers: {"apollographql-client-name":"explorer","apollographql-client-version":"1.0"},
      displayOptions: {
        showHeadersAndEnvVars: true, 
        docsPanelState: 'closed', 
        theme: 'dark',
      },
    },
  });
</script>



<h2 class="wp-block-heading"><a href="#when-to-use-the-api-and-when-to-use-rover" aria-hidden="true" class="aal_anchor" id="when-to-use-the-api-and-when-to-use-rover"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>When to use the API and when to use Rover</h2>



<p>In most cases, you’ll want to use the Apollo Rover CLI to manage and publish your GraphQL supergraph schema. As developers iterate on their subgraphs, we recommend regularly running schema checks to ensure that their updated graphs properly compose into a supergraph. If you use continuous integration (CI), we recommend integrating Rover into your pipeline. <a href="https://www.apollographql.com/docs/rover/ci-cd">Here’s how to get started</a>.</p>



<p>If you need to do more complex operations, then you might want to use the GraphOS platform API. For instance, you might want your CI pipeline to create a new Studio variant for each test run, then delete that variant when the run finishes. To accomplish this, you can do the following using the Platform API:</p>



<ul class="wp-block-list"><li>Create a test variant by <a href="https://studio.apollographql.com/public/apollo-platform/home?variant=main#publishing-schemas">Publishing your schema(s) to it</a>.</li><li>Perform any desired tests (such as <a href="https://studio.apollographql.com/public/apollo-platform/home?variant=main#running-schema-checks">schema checks</a>) on the test variant.</li><li>Delete the variant with the corresponding <a href="https://studio.apollographql.com/public/apollo-platform/home?variant=main#destructive-actions">destructive action</a>.</li></ul>



<p>In the near future, we will post about other ways to integrate with the GraphOS platform, such as using the platform API with your governance workflows for your supergraphs. We also look forward to learning how you will use the API!</p>



<h2 class="wp-block-heading"><a href="#looking-ahead" aria-hidden="true" class="aal_anchor" id="looking-ahead"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Looking ahead</h2>



<p>This is just the start for the GraphOS platform API! We are continuing to add new features to both GraphOS and the platform API to make it easier for you to get your schema changes safely to production, to keep your teams up-to-date, and to ensure that clients consuming your graph never experience breaking changes.</p>



<p>To stay up-to-date on what’s coming next with the GraphOS platform API, <a href="https://github.com/apollographql/apollo-studio-community">star and watch the Apollo Studio Community GitHub project</a>. We will be sharing more about the GraphOS platform API roadmap there and here in the Apollo blog.</p>



<p>You can help us by letting us know what you’d like added to the API by creating a GitHub issue or by giving us feedback in the <a href="https://community.apollographql.com/">Apollo Community</a>.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#get-started-with-graphos" aria-hidden="true" class="aal_anchor" id="get-started-with-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started with GraphOS</h2>



<p>Still getting started with a single GraphQL server or new to GraphQL? No problem. We&#8217;ve made it easier than ever to leverage all of the analytics and automation of supergraphs in Studio. <a href="https://apollographql.com/tutorials?ref=www">Create your first graph</a> and make your first graph query in under an hour.</p>


Integrate with GraphOS using the new Platform API


<p>When we built Apollo in 2016, we had a vision. We set out to build one distributed and scalable data layer that could connect to anything we need, no matter the client, the architecture, the source, the language. It was a lofty goal, but work worth doing, because solving this gets to the heart of how to make app development more approachable and productive.</p>



<p>We realized this vision with <a href="https://www.apollographql.com/blog/announcement/backend/the-supergraph-a-new-way-to-think-about-graphql/">the supergraph</a>, a new layer of the stack that unifies an organization’s data, services, and capabilities, built around three underlying principles: 1) One unified composition layer; 2) Built in modules; 3) That evolves over time.</p>



<p>Today, we’re announcing Apollo GraphOS, a complete cloud platform that lets anyone build, connect, and scale any supergraph. GraphOS is the execution fabric for the supergraph – a powerful runtime that connects backend and frontend systems in a modular way. It also has an integrated control plane to help developers manage, evolve, and collaborate on the supergraph.&nbsp;</p>



<p>GraphOS lets you connect all your data and services seamlessly with federation. It gives you advanced capabilities like <code>@defer</code> without having to write any code or sign up for any ops burden. And it’s secure – we’ve achieved SOC 2 Type 2 compliance, and passed a full audit by Doyensec with flying colors.</p>



<h2 class="wp-block-heading"><a href="#why-graphos" aria-hidden="true" class="aal_anchor" id="why-graphos"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Why GraphOS?</strong></h2>



<p>We hear a lot from developers that they want to do more with the graph. They want to scale, but they really don’t want to have to think about it. They just want to build products.</p>



<p>We wanted to solve this. Not everyone has a big ops team or the GraphQL expertise or the desire to run infrastructure for the supergraph themselves. They need something that’s easy to start with and that can grow along with them – a supergraph operating system that can scale to any number of subgraphs, across every continent, at lightning speed.</p>



<p>So we built one.</p>



<h2 class="wp-block-heading"><a href="#whats-in-it" aria-hidden="true" class="aal_anchor" id="whats-in-it"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What’s in it?</strong></h2>



<p>Apollo Router is the heart of GraphOS – built in Rust, designed for performance. We partnered with Fly.io to build our own cloud-based supergraph runtime on top of Apollo Router, designed for exactly what the supergraph needs. It gives us the global reach of an edge network with the core computing capability and performance to support new and upcoming features like query planning, @defer, live queries, and so much more to come.</p>



<p>We paired this global supergraph runtime with our complete set of schema delivery, collaboration, and observability tools so developers can publish changes to the supergraph and seamlessly deliver them across all their apps. And, last but not least, we included a supergraph development kit that can connect any existing graph to the supergraph.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#our-supergraph-development-kit" aria-hidden="true" class="aal_anchor" id="our-supergraph-development-kit"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Our supergraph development kit&nbsp;</strong></h2>



<p>We hear from thousands of GraphQL developers that there is a disconnect between how they start building graphs, and how they scale them. That disconnect leads to breaking changes, bloated schemas, and uncertainty about the path forward.</p>



<p>If we have learned one thing about graphs, it is that they MUST mature, change, and adapt. The supergraph doesn’t work if it requires a rewrite of the entire existing system. It’s not the v2 of a schema. It’s about modularizing what already exists –&nbsp; transforming an existing graph into a module and elevating it into a full-fledged supergraph.</p>



<p>What if you could take what you’ve already built, and say: ok this isn’t the end. This is just my first module. Where can I go from here? What else can I build from here?&nbsp;</p>



<p>Let’s add a new service; a new function.&nbsp;</p>



<p>And another.&nbsp;</p>



<p>And another.&nbsp;</p>



<p>All individual and unique, each written in whatever language I choose, each independent and flexible. But all connected.&nbsp;</p>



<p>The supergraph development kit is here to make this all possible with three components that create a seamless developer experience:</p>



<ul class="wp-block-list">
<li><strong><code>rover dev</code>:</strong> Spins up a supergraph and runtime locally, making the graph you have your first module.</li>



<li><strong><code>rover template use</code>:</strong> Gives anyone access to a cookbook of templates for adding new modules in all the most popular languages and frameworks.&nbsp;</li>



<li><strong>Sandbox:</strong> A GraphQL IDE designed for local supergraph development and testing.</li>
</ul>



<h2 class="wp-block-heading"><a href="#priced-to-use" aria-hidden="true" class="aal_anchor" id="priced-to-use"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Priced to use</strong></h2>



<p>Alongside GraphOS we are launching a new <a href="https://apollographql.com/pricing">usage-based pricing</a> model that matches how developers build and scale the graph.</p>



<p>It starts free with a generous free quota to get you on the supergraph – 10M queries every month.</p>



<p>Beyond that, it’s priced as it should be – by the query on a pay-as-you-go basis.</p>



<p>GraphOS is an essential part of the toolkit for any GraphQL developer who is looking to build better apps fast while avoiding technical debt, mitigating risks, and staying competitive in a demand-driven world.&nbsp;</p>



<p>It’s free and takes just a few minutes to get started. We can&#8217;t wait for you to <a href="https://studio.apollographql.com/signup?referrer=blog" data-type="URL" data-id="https://studio.apollographql.com/signup">get on the supergraph</a>.</p>


Introducing Apollo GraphOS

Announcing Apollo Router v1.0


<p>Calling all graph architects! If you are looking for inspiration, best practices, and help building or scaling your organization&#8217;s supergraph architecture, then this blog is for you. Read on for your graph architect’s guide to GraphQL Summit 2022.&nbsp;</p>



<p>#ICYMI: GraphQL Summit 2022 is back in person October 3-5 in San Diego for 3 days of surf, sun, and all things GraphQL. <a href="https://summit.graphql.com/event/9cabb0aa-eb3c-4bfd-bf74-3dcc4c82c066/regProcessStep1?utm_campaign=graphql-summit-22-grapharch-blog&amp;utm_medium=blog&amp;utm_source=apollo&amp;utm_content=content" target="_blank" rel="noreferrer noopener">Register today to avoid all the FOMO</a>. </p>



<p><strong>Why you should attend GraphQL Summit 2022&nbsp;</strong></p>



<p>Come to GraphQL Summit to hear how graph architects at leading global enterprises are migrating to a federated supergraph, scaling large graphs with many resolvers, and more.&nbsp;&nbsp;</p>



<p>Connect with fellow graph architects to share advice, best practices, and lessons learned from scaling a supergraph enterprise-wide while overlooking the San Diego marina or indulging in brews at the ultimate Graph &amp; Brew at Stone Brewery.&nbsp;</p>



<p><strong>Can’t miss sessions</strong></p>



<p><span style="text-decoration: underline;">Determining the Right Architecture to Design When Adopting Apollo Federation</span> with Maria Lucena, Director of Architecture, Fidelity Investments</p>



<ul class="wp-block-list"><li>As teams think about creating or migrating their APIs to Apollo Federation, it can be perplexing, if not paralyzing, to decide where functionality should go in a distributed system. In this session, Fidelity Investments share the techniques that have helped us identify and separate functionality, using time-tested engineering techniques, including domain-driven design, that teams can embrace to become productive faster.</li></ul>



<p><span style="text-decoration: underline;">State of the Federation Subgraph Ecosystem</span> with Derek Kuc, Principle Engineer, Apollo GraphQL </p>



<ul class="wp-block-list"><li>Apollo Federation is a powerful, open architecture that helps you create a unified supergraph that combines multiple GraphQL APIs. From dynamically typed languages like JavaScript to statically typed Java. From functional programming style of Elixir to Object Oriented one in C#. SDL first or code first. Developers have a number of options to choose from when developing their GraphQL subgraphs. In this talk we’ll explore the ever growing federation subgraph ecosystem and highlight some of the available libraries.</li></ul>



<p><span style="text-decoration: underline;">Sit Back and Let the Graph Grow</span> with Joey Nenni, Enterprise Architect, PayPal</p>



<ul class="wp-block-list"><li>Remove the stress and guess work from designing your company&#8217;s large GraphQL schema. Having an intensive schema design process ensures your graph remains consistent and coherent but often blocks product teams from meeting deadlines due to complex ownership issues and required time for a quality design review. Instead, learn how to unblock your product teams and let them express what they want from the graph by allowing them to create whatever schema they want exactly how they want it in their own protected bubble on the supergraph. Learn from the schemas your client applications are creating and design a quality shared schema at the pace required to do the job properly.</li></ul>



<p><span style="text-decoration: underline;">How We Unified One Graph at Block</span> with Alex Hancock, Software Engineer, Block </p>



<ul class="wp-block-list"><li>Architecture overview of our system at Block, how we fostered adoption, and how we unified two separate GraphQL implementations at the company to use one graph.</li></ul>



<p><span style="text-decoration: underline;">7 Tips for Writing Better Resolvers</span> with Max Gooding, Software Architect, Neo Financial&nbsp;</p>



<ul class="wp-block-list"><li>If you are a large organization and have many developers you probably have hundreds or maybe even thousands of resolvers. Here are 7 tips that will help you maintain and scale your large graph and its many resolvers!</li></ul>



<p><strong>Don’t delay, register today</strong></p>



<p>Read the full details about this year’s conference and <a href="https://summit.graphql.com/event/9cabb0aa-eb3c-4bfd-bf74-3dcc4c82c066/regProcessStep1?utm_campaign=graphql-summit-22-grapharch-blog&amp;utm_medium=blog&amp;utm_source=apollo&amp;utm_content=content" target="_blank" rel="noreferrer noopener">register to attend here</a>. </p>



<p>Already tasting the salty air but need more details to convince your boss? Use this <a href="https://docs.google.com/document/d/1NHVkn2_kV67YeVI1wkpGMfXPHoINsFIZdXitRIcuGcg/edit" target="_blank" rel="noreferrer noopener">Justification Letter</a> to help persuade them of the benefits of attending GraphQL Summit 2022. </p>



<p>P.S. Sending a group of 5 or more? Reach out to summit@apollographql.com for an additional $200 off each pass.</p>


The Graph Architect’s Guide to GraphQL Summit 2022


<p>For federated graph variants, Apollo offers schema checks to ensure that proposed changes to subgraphs won’t break supergraph composition (build checks) or your active clients (operation checks).&nbsp;</p>



<p>Today, we’re excited to extend this capability to <a href="https://www.apollographql.com/blog/announcement/platform/contracts-are-now-generally-available/">contracts</a>!</p>



<h2 class="wp-block-heading"><a href="#what-are-contract-checks" aria-hidden="true" class="aal_anchor" id="what-are-contract-checks"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What are contract checks?</h2>



<p>Contract checks ensure that changes made to a source variant’s subgraphs or to the contract filtering configuration won’t cause breaking changes to any downstream contract variant’s schema or active clients. Each contract check runs two types of tasks to do this:</p>



<ol class="wp-block-list"><li><strong>Build tasks</strong>: Build tasks verify that downstream contract variants build successfully and that filtering rules continue to work as expected.</li><li><strong>Operation tasks:</strong> Operation tasks check proposed schema changes against historical operations to the contract variant (and any other selected variant) to verify whether the changes will break any of the contract variant’s active clients.</li></ol>



<h2 class="wp-block-heading"><a href="#how-are-contract-checks-triggered" aria-hidden="true" class="aal_anchor" id="how-are-contract-checks-triggered"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How are contract checks triggered?</h2>



<p>Contract checks are triggered in two scenarios:&nbsp;</p>



<p><strong>1. Changes are made to the source variant’s subgraphs and source variants checks are run</strong></p>



<p>When a source variant has downstream contracts associated with it, Apollo will run an additional task in the checks workflow called a <strong>downstream task</strong>.&nbsp;</p>



<p>When a change is made to any of the source variant’s subgraphs, the checks workflow begins, and the downstream task runs contract checks for all of the downstream contract variants.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1433" height="791" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image2.gif" alt="" class="wp-image-16051"/></figure>



<p><strong>2. Contract filter configuration is edited in Studio</strong></p>



<p>When you edit the filtering configuration for a contract in Studio, contract checks will run to make sure that the new filter rules can apply without build errors and without causing breaking changes that affect operations from the contract variant’s active clients.&nbsp;</p>



<p>If any checks fail, you’ll see a warning when reviewing the new contract schema, but you can still choose to update the contract even if there are warning or if checks haven’t finished running.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1435" height="786" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image3.gif" alt="" class="wp-image-16053"/></figure>



<h2 class="wp-block-heading"><a href="#blocking-downstream-contract-variants" aria-hidden="true" class="aal_anchor" id="blocking-downstream-contract-variants"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Blocking downstream contract variants</h2>



<p>When checks for a source variant are triggered, checks for all associated contract variants will also run. You can decide which of those contract variants you’d like to mark as <code>BLOCKING</code>.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="558" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-1024x558.png" alt="" class="wp-image-16057" srcset="https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-1024x558.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-300x163.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-768x418.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-1536x837.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-1200x654.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2-1980x1079.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/09/image1-2.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>If a contract variant is marked as <code>BLOCKING</code> and a check for that contract <em>fails</em>, then the source variant’s check status would also be evaluated as <em>failed</em>.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="437" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image4-1024x437.png" alt="" class="wp-image-16059" srcset="https://wp.apollographql.com/wp-content/uploads/2022/09/image4-1024x437.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4-300x128.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4-768x328.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4-1536x655.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4-1200x512.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4-1980x845.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/09/image4.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started!</h2>



<p>Contracts checks are available today on Apollo’s Enterprise plan! Head over to checks configuration in Studio to select which contract variants should be blocking your source variant checks to fail. If you aren’t on Apollo Enterprise and would like to try it out, <a href="https://www.apollographql.com/contact-sales/">talk to us</a> about an Enterprise trial.</p>



<p>ℹ️ If you are using the Rover CLI to run checks in your CI/CD pipelines, you must upgrade to at least Rover v0.8.2 to get the best and full functionality of contract checks. If you are using Rover v0.8.0 or v0.8.1, your source variants that have associated contract variants <em>will</em> start triggering contract checks as described above, however, if a contract check fails, it won’t cause <code>rover subgraph check</code> to fail, affecting the accuracy of your CI/CD pipeline.</p>



<p>⚠️ <strong>Note: </strong>Please make sure you are on the latest version of the Studio UI. Click on the bell icon at the top right corner of Studio and if you see <em>“Update available, click to relaunch”</em> at the bottom left of the modal then click that to get the latest version.</p>


Prevent breaking changes in downstream variants with contract checks


<p>A healthy graph is never still — new features appear, old ones are pruned, and regretful decisions are repaired (“at last, my schema is perfect” &#8211; said no one ever).</p>



<p>But planning for change requires graph maintainers to tread carefully &#8211; the more you know about how your schema is being used, the more confidently and quickly you can move. With the new Field Insights page in Apollo Studio, safe and rapid innovation of your graph just got a whole lot easier.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="600" height="450" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image-3.png" alt="My schema is perfect - said no one ever." class="wp-image-15888" srcset="https://wp.apollographql.com/wp-content/uploads/2022/09/image-3.png 600w, https://wp.apollographql.com/wp-content/uploads/2022/09/image-3-300x225.png 300w" sizes="auto, (max-width: 600px) 100vw, 600px" /></figure>



<h2 class="wp-block-heading"><a href="#why-measure-fields" aria-hidden="true" class="aal_anchor" id="why-measure-fields"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Why measure fields?</h2>



<h3 class="wp-block-heading"><a href="#fields-as-features" aria-hidden="true" class="aal_anchor" id="fields-as-features"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Fields as <em>features</em></h3>



<p>Fields are the last stop for querying data from the graph. They represent the atoms of information that are exposed to the outside world. They are also functions &#8211; when used in a mutation, they are the entry points that trigger actions in the graph. Every field is literally a “feature” of the graph, and if we want to measure the usage or health of our graph’s features, the field is a great place to start. Maintaining a graph comes with a mindset of continuous curation, and knowing where to focus our improvements is key.</p>



<h3 class="wp-block-heading"><a href="#fields-as-relationships" aria-hidden="true" class="aal_anchor" id="fields-as-relationships"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Fields as <em>relationships</em></h3>



<p>Crucially, fields also model the relationships that bind objects together. This is what makes GraphQL uniquely powerful — queries can move freely about the graph, jumping from one entity to the next and fetching as much or as little data as they need along the way. But if one of these links breaks down, entire subtrees can go dark. This is of special concern in a federated context where fields provide the bridge between the business domains in your API.</p>



<h2 class="wp-block-heading"><a href="#stewardship-through-understanding" aria-hidden="true" class="aal_anchor" id="stewardship-through-understanding"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Stewardship through understanding</h2>



<p>Viewing usage data through the lens of your fields unlocks some essential graph health workflows. With field insights, we are bringing these capabilities into focus for your graph:</p>



<ol class="wp-block-list"><li><strong>Understand usage and adoption patterns.</strong> Client usage breakdowns make it easy to see how client applications and operations are using the field, and field usage over time tells you whether field usage is ramping up or down.</li><li><strong>Identify impact on user-facing apps.</strong> Understand earlier in the schema lifecycle the changes that are likely to impact end-users and other team members based on observed usage.</li><li><strong>Guide change workflows</strong>. Confidently deprecate and remove outdated or unused fields. See the first and last time a field was used, then verify changes with <a href="https://www.apollographql.com/docs/studio/schema-checks">schema checks</a> at release time.</li><li><strong>Assess field-level health.</strong> Per-field error rates and latency histograms help you pinpoint health issues in your graph to target optimization work and validate improvements.</li><li><strong>Understand federation dependencies.</strong> Discover which subgraphs participate in resolving a field as teams work together to build the graph. (Hint: use the <code>@contact</code> directive in your subgraphs to let teams know how to get in touch with one another!)</li></ol>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="584" src="https://wp.apollographql.com/wp-content/uploads/2022/09/image-4-1024x584.png" alt="" class="wp-image-15890" srcset="https://wp.apollographql.com/wp-content/uploads/2022/09/image-4-1024x584.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/09/image-4-300x171.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/09/image-4-768x438.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/09/image-4-1200x684.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/09/image-4.png 1371w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>New field-level insights for your graph.</figcaption></figure>



<p>The amazing flexibility of GraphQL has been game-changing for app developers, but it does present an observability challenge. With operations of all shapes and sizes, how can we best understand which parts of the graph are being used, how much, and by whom? What parts of the schema are unhealthy or causing performance bottlenecks for the graph? With the new Field Insights page, you’ll have a powerful new tool to answer these kinds of questions.</p>



<p>Field Insights are available to all organizations, with longer data retention offered on paid Apollo plans. As always, we’d <a href="https://docs.google.com/forms/d/1lC-7aWNe4pnxcAPTB-W4-N8jZoyD_xQXzVByD6HOZpc/edit">love your feedback</a> on how we could further improve your graph workflows.</p>



<p>⚠️ <em>Note that field latency and execution stats require the use of field-level instrumentation in your server or subgraph &#8211; for details on how to configure your server, see </em><a href="https://www.apollographql.com/docs/studio/metrics/field-usage"><em>our documentation.</em></a></p>


Continuously improve your graph with field-level usage and health metrics from Apollo Studio.


<p>Calling all backend developers! If you are looking to learn more about building, managing, and securing your supergraph at scale, then this blog is for you. Read on for your backend developer’s guide to GraphQL Summit 2022.&nbsp;</p>



<p>#ICYMI: GraphQL Summit 2022 is back in person October 3-5 in San Diego for 3 days of surf, sun, and all things GraphQL. <a href="https://summit.graphql.com/event/9cabb0aa-eb3c-4bfd-bf74-3dcc4c82c066/regProcessStep1?utm_campaign=graphql-summit-22-backenddev-blog&amp;utm_medium=blog&amp;utm_source=apollo&amp;utm_content=content">Register today to avoid all the FOMO.</a>&nbsp;</p>



<p><strong>Why you should attend GraphQL Summit 2022&nbsp;</strong></p>



<p>Come to GraphQL Summit to hear best practices from backend developers at leading global enterprise organizations who are minimizing API maintenance work by contributing to the supergraph.&nbsp;&nbsp;</p>



<p>Connect with fellow backend developers to share advice for building subgraphs, ensuring security, and modernizing your stack with a supergraph while overlooking the San Diego marina or indulging in brews at the ultimate Graph &amp; Brew at Stone Brewery.&nbsp;</p>



<p><strong>Can’t miss sessions</strong></p>



<p>Offensive GraphQL Security Testing with Nick Aleks, Sr. Director of Security, Wealthsimple and Dolev Farhi, Head of Security &amp; Research, Inigo&nbsp;</p>



<ul class="wp-block-list"><li>Understand how to hack GraphQL through the lens of a hacker. By using the same tools and resources adversaries use to break GraphQL applications, developers can pragmatically test the security posture of their applications before it&#8217;s too late.</li></ul>



<p>Server Driven UI and Batching from Gateway to Subgraphs with Samuel Vazquez, Sr. Software Development Engineer, Expedia Group&nbsp;</p>



<ul class="wp-block-list"><li>Learn how to make sure you’re taking full advantage of Apollo Federation to batch operations to subgraphs and subgraphs to downstream through resolvers with a custom DataLoader dispatching mechanism.&nbsp;</li></ul>



<p>How We Do Localization at Babylon with Dominic Chambers, Staff Engineer, Babylon&nbsp;</p>



<ul class="wp-block-list"><li>Discover how utility objects can be used when creating subgraphs that expose functionality that can not be surfaced using entity objects. Plus, Dominic will share concrete examples of how they’ve done this at Babylon, and why they think it&#8217;s a great pattern.</li></ul>



<p><strong>Don’t delay, register today</strong></p>



<p>Read the full details about this year’s conference and <a href="https://summit.graphql.com/event/9cabb0aa-eb3c-4bfd-bf74-3dcc4c82c066/regProcessStep1?utm_campaign=graphql-summit-22-backenddev-blog&amp;utm_medium=blog&amp;utm_source=apollo&amp;utm_content=content">register to attend here</a>. Don’t miss out! </p>



<p>Already tasting the salty air but need more details to convince your boss? Use this <a href="https://docs.google.com/document/d/1NHVkn2_kV67YeVI1wkpGMfXPHoINsFIZdXitRIcuGcg/edit">Justification Letter</a> to help persuade them of the benefits of attending GraphQL Summit 2022.&nbsp;</p>



<p>P.S. Sending a group? Reach out to summit@apollographql.com for an additional $200 off each pass. </p>


The Backend Developer’s Guide to GraphQL Summit 2022


<p>Calling all app developers! If you are looking for help navigating how to effectively, and efficiently, build applications on top of the supergraph, then this blog is for you. Read on for your app developer’s guide to GraphQL Summit 2022.&nbsp;</p>



<p>#ICYMI: GraphQL Summit 2022 is back in person October 3-5 in San Diego for 3 days of surf, sun, and all things GraphQL. <a href="https://summit.graphql.com/event/9cabb0aa-eb3c-4bfd-bf74-3dcc4c82c066/regProcessStep1?utm_campaign=graphql-summit-22-appdev-blog&amp;utm_medium=blog&amp;utm_source=apollo&amp;utm_content=content">Register today to avoid all the FOMO</a>.&nbsp;</p>



<p><strong>Why you should attend GraphQL Summit 2022&nbsp;</strong></p>



<p>Come to GraphQL Summit to hear how graph champions at leading global organizations are reducing friction in the app development process, optimizing their schemas, solving caching challenges, and more.&nbsp;</p>



<p>Connect with fellow app developers to share advice on schema best practices and how you are using the supergraph to deliver innovative customer experiences while overlooking the San Diego marina or indulging in brews at the ultimate Graph &amp; Brew at Stone Brewery.&nbsp;</p>



<p><strong>Can’t miss sessions</strong></p>



<p>Challenges of Modularizing a GraphQL iOS Application Calvin Cestari, iOS Engineer, Apollo GraphQL</p>



<ul class="wp-block-list"><li>There is no one-size-fits-all approach to building a modularized iOS app. How would you approach sharing generated GraphQL schema objects throughout your modularized app? Do you want to co-locate the generated model objects with the rest of your view code? How could you share GraphQL fragment generated code with multiple objects and/or operations? This talk explores a few of the challenges you might face, and some techniques for resolving them.</li></ul>



<p>Navigating the Normalized Cache Ali Asghari, Staff Engineer, Wayfair</p>



<ul class="wp-block-list"><li>Mobile app experiences focus as much on the space between screens as they do the screens themselves. Transitioning between screens however is data bounded, often requiring a latent network round trips to fully render. While pre-fetching is a solution, for apps with federated ownership, coordinating what data to pre-fetch becomes challenging. By examining what motivates our users’ navigational patterns, we can design schemas which allow for uncoordinated data sharing and smoother transitions by leveraging the normalized cache.</li></ul>



<p>Schema Updates on Mobile GraphQL Clients Anthony Miller, Lead Developer, Apollo iOS, Apollo GraphQL&nbsp;</p>



<ul class="wp-block-list"><li>Most GraphQL clients use schema knowledge to execute GraphQL operations, configure caching, generate model objects, and more. This talk explores the problems that schema updates pose to mobile applications using Apollo iOS and Apollo Kotlin; some methods for dealing with those problems; and how possible future additions to the GraphQL specification could help mitigate them.</li></ul>



<p>Isolated Client Development with Kaitlyn Taboada, Lead Software Engineer, Odeko</p>



<ul class="wp-block-list"><li>We will cover using the power of the schema to create meaningful/reliable stub data quickly. This allows frontend developer work without relying on backends to be complete or operational. This is vital for a microservice ecosystem to prevent users from needing to spin up microservices to develop locally.</li></ul>



<p><strong>Don’t delay, register today</strong></p>



<p>Read the full details about this year’s conference and <a rel="noreferrer noopener" href="https://summit.graphql.com/event/9cabb0aa-eb3c-4bfd-bf74-3dcc4c82c066/regProcessStep1?utm_campaign=graphql-summit-22-appdev-blog&amp;utm_medium=blog&amp;utm_source=apollo&amp;utm_content=content" target="_blank">register to attend here</a>. Don’t miss out! </p>



<p>Already tasting the salty air but need more details to convince your boss? Use this <a href="https://docs.google.com/document/d/1NHVkn2_kV67YeVI1wkpGMfXPHoINsFIZdXitRIcuGcg/edit" target="_blank" rel="noreferrer noopener">Justification Letter</a> to help persuade them of the benefits of attending GraphQL Summit 2022.&nbsp;</p>



<p>P.S. Sending a group? Reach out to summit@apollographql.com for an additional $200 off each pass.</p>



<p></p>


The App Developer’s Guide to GraphQL Summit 2022 


<p>We recently added filters to the Schema Reference page in Studio to make the schema browsing experience easier and more intuitive, especially as your supergraph schemas grow!&nbsp;</p>



<p>Head over to the Schema Reference page in Apollo Studio and try it out.</p>



<h2 class="wp-block-heading"><a href="#filter-schema-by-subgraphs-tags-directives-arguments-and-return-types" aria-hidden="true" class="aal_anchor" id="filter-schema-by-subgraphs-tags-directives-arguments-and-return-types"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Filter schema by subgraphs, tags, directives, arguments and return types</h2>



<p>Filter elements of your schema that match to multiple types of filters. You can AND across filters and OR within a single filter.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="349" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image1-1024x349.png" alt="" class="wp-image-15618" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image1-1024x349.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1-300x102.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1-768x262.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1-1536x524.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1-1200x409.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1-1980x676.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image1.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#text-highlighting" aria-hidden="true" class="aal_anchor" id="text-highlighting"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Text highlighting</h2>



<p>Any filter results are highlighted for easy visibility. In the left menu, you can see how many elements matched for each type in the parenthesis.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="421" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image6-1024x421.png" alt="" class="wp-image-15622" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image6-1024x421.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6-300x123.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6-768x316.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6-1536x632.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6-1200x493.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6-1980x814.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image6.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>You can also type a word and see matching elements. If you prefix the word with a <code>.</code> then filters are only applied to fields, and if you suffix the word with a <code>.</code> then the filter is only applied to the types.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="389" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image4-1024x389.png" alt="" class="wp-image-15624" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image4-1024x389.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4-300x114.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4-768x292.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4-1536x584.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4-1200x456.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4-1980x753.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image4.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#hints-hints-hints" aria-hidden="true" class="aal_anchor" id="hints-hints-hints"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Hints hints hints</h2>



<p>When you type a word, Studio might suggest some hints associated with supported filter types for better results.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="525" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image3-1024x525.png" alt="" class="wp-image-15626" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image3-1024x525.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3-300x154.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3-768x394.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3-1536x787.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3-1200x615.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3-1980x1015.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image3.png 1982w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#view-and-filter-by-tag" aria-hidden="true" class="aal_anchor" id="view-and-filter-by-tag"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>View and filter by <code>@tag</code></h2>



<p>With the right permissions, you can view and filter by different tag names in the schema reference page.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="523" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-1024x523.png" alt="" class="wp-image-15628" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-1024x523.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-300x153.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-768x392.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-1536x784.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-1200x612.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1-1980x1010.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image5-1.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#and-finally-share-your-filter-query-with-your-teammates" aria-hidden="true" class="aal_anchor" id="and-finally-share-your-filter-query-with-your-teammates"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>And finally, share your filter query with your teammates</h2>



<p>You can share your filter query so that your teammates can look at the same resulting schema elements. Either copy the URL directly, or click on the share icon. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="240" src="https://wp.apollographql.com/wp-content/uploads/2022/08/image2-1024x240.png" alt="" class="wp-image-15630" srcset="https://wp.apollographql.com/wp-content/uploads/2022/08/image2-1024x240.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2-300x70.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2-768x180.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2-1536x360.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2-1200x281.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2-1980x464.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/08/image2.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#check-it-out-today-and-let-us-know-what-you-think" aria-hidden="true" class="aal_anchor" id="check-it-out-today-and-let-us-know-what-you-think"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Check it out today and let us know what you think!</h3>



<p>Head over to the Schema Reference page for your graphs in Apollo Studio and try out these filters! This is our first iteration and we hope to continue to provide you with the best schema browsing experience, so if you have any feedback, please fill out this <a href="https://forms.gle/z1pofnxnxwe2YxpG6">feedback</a> form or drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>



<p>⚠️ <strong>Note:</strong> If you do not see this capability on Apollo Studio, make sure you are on the latest version of the UI. Click on the bell icon at the top right corner of Studio and if you see <em>“Update available, click to relaunch”</em> at the bottom left of the modal then click that to get the latest version.</p>


Quickly find what you need in your GraphQL schema with filters


<p>Our main objective at Apollo is to ensure every company can build a successful supergraph. As part of the effort, we’re committed to ensuring a thriving supergraph ecosystem of solutions and technology partners that make it possible for companies to scale their supergraphs. I’m excited to announce that we are partnering with <a href="https://www.xolv.io/">Xolvio</a> to provide professional services for customers needing additional help scaling their supergraphs.</p>



<p><strong>About Xolvio</strong></p>



<p>Xolvio is a boutique consulting &amp; development company made up of digital architects and expert builders with a proven track record in helping organizations scale their supergraphs. They have enterprise-grade experience working with high-complexity systems with a specialty in refactoring and modernizing legacy code through domain-driven design principles and CI/CD pipeline automation.</p>



<p>Apollo and Xolvio have partnered on several key projects and are excited to make this an official partnership. One of those projects was the launch of <a href="https://www.xolv.io/case-studies/audi-case-study/">Audi’s e-tron reservation platform</a> for their electric car. The Xolvio team worked closely with Apollo and Audi to build a supergraph to power their e-tron reservation system, which they were able to launch in just four months. As Jeff Titus at Audi puts it, “Xolvio offers a level of experience and cross-functional value that we have never encountered anywhere else, nor have we been able to find from any single organization.”</p>



<p><strong>How Xolvio helps teams scale their supergraphs</strong> <strong>faster</strong></p>



<p>Xolvio partners with engineering organizations to assess their GraphQL capabilities, create a supergraph roadmap, and provide dedicated engineers to help implement the supergraph. Xolvio founder, Sam Hatoum, says, “We have been part of Apollo’s amazing journey since the very beginning, which allowed us to create a unique methodology for deliberate and predictable supergraph design and implementation. Our holistic approach to software architecture and development ensures that we provide targeted support tailored to the organization’s current GraphQL adoption stage and aimed at fast-tracking an enterprise-wide supergraph.”</p>



<p>Xolvio provides dedicated engagements from 2 to 12 weeks and more ongoing support if needed. Some of the deliverables that Xolvio provides are:</p>



<ul class="wp-block-list"><li>Creating readiness assessment and Supergraph project roadmap</li><li>Conducting schema design sessions</li><li>Breaking monoliths into microservices</li><li>Joining existing REST services to the supergraph</li><li>Implementation of a federated supergraph&nbsp;</li><li>Integrating CI/CD pipelines with schema registry integration</li><li>Creating standard reference repositories with best practice patterns</li><li>Defining maintenance strategies</li></ul>



<p>Learn more about Xolvio’s Apollo GraphQL professional services <a href="https://www.xolv.io/services/apollo-graphql-professional-services/">here</a>.</p>



<p><strong>Reach out to get started:</strong></p>



<p>If you are interested in exploring a relationship with Xolvio, reach your account executive or message us at partners@apollographql.com. Stay tuned for additional announcements around our partner program.</p>


Apollo introduces  supergraph professional services by Xolvio


<p>We’re excited to announce that Apollo is now SOC 2 Type II certified, an incredibly important milestone for us that demonstrates the investment we’ve put into building a safe and secure product and organization over the years.&nbsp;</p>



<p>SOC 2 Type II certification is a third-party audit that’s part of the American Institute of CPA’s (AICPA) <a href="https://us.aicpa.org/interestareas/frc/assuranceadvisoryservices/aicpasoc2report">Service Organization Control reporting platform</a>. It’s a necessity for any cloud SaaS business today. In order to achieve SOC 2 compliance, companies like Apollo must undergo a rigorous audit of the security policies and controls it has in place to protect its customers’ data. This certification means that Apollo has written – and operates our business – based on a set of comprehensive information security policies and procedures.</p>



<p>You can request a copy of our Type II audit through your customer success team.</p>



<h2 class="wp-block-heading"><a href="#apollo-values-your-security" aria-hidden="true" class="aal_anchor" id="apollo-values-your-security"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Apollo values your security</strong></h2>



<p>One of our core company values is empowering others –&nbsp;setting people up, both inside and outside the company, to do their best work. This certification demonstrates that value by letting our customers know that every bit of information they put into their supergraph is being handled safely and securely. We will continue to focus on, and extend our commitment to security so that,&nbsp;as more and more companies use the supergraph to power the world&#8217;s most important apps, they will know Apollo takes their data security seriously.</p>


Apollo earns SOC 2 Type II compliance


<p>Two years ago we set out to build Apollo Explorer &#8211; the GraphQL IDE we felt was missing from the GraphQL community. And last summer, we made Explorer available for local development by releasing it in <a href="https://www.apollographql.com/blog/announcement/platform/apollo-sandbox-an-open-graphql-ide-for-local-development/">Apollo Sandbox</a>. But Sandbox still ran on the Apollo Studio domain, and our #1 challenge has been distributing Explorer in a way that gives you enough control over the network properties of your queries. Authentication, CORS, firewalls, you name it – a GraphQL IDE exists to let people write queries, and graph admins need to be able to control the network properties of those HTTP requests, full stop.</p>



<p>We added a lot of controls to Explorer to help. We made a way for graph admins to set default headers on their graphs. We built a mechanism for you to define preflight scripts which can do things like automatically refresh tokens in the headers on your graph. But in the end, we have found that there’s no setting we can add to Studio that can replace what <strong>you</strong> can do with full control over the network requests from our IDE.</p>



<p><strong>That’s why today we are giving Sandbox to <em>you</em>.&nbsp;</strong></p>



<p>We are over the moon to share with you that we have made Apollo Sandbox available for you to <strong>embed on any website</strong>, not just on Apollo Studio. ✨🌙 ✨</p>



<h2 class="wp-block-heading"><a href="#how-to-embed-apollo-sandbox" aria-hidden="true" class="aal_anchor" id="how-to-embed-apollo-sandbox"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How to embed Apollo Sandbox</h2>



<h3 class="wp-block-heading"><a href="#embedding-apollo-sandbox-with-html" aria-hidden="true" class="aal_anchor" id="embedding-apollo-sandbox-with-html"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Embedding Apollo Sandbox with HTML</h3>



<p>We are now distributing the full-featured code of Apollo Sandbox over a CDN, so you can embed it on any website you’d like. All you need is a little HTML:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-markup">&lt;div id=&quot;sandbox&quot; style=&quot;position:absolute;top:0;right:0;bottom:0;left:0&quot;&gt;&lt;/div&gt;
&lt;script src=&quot;https://embeddable-sandbox.cdn.apollographql.com/_latest/embeddable-sandbox.umd.production.min.js&quot;&gt;&lt;/script&gt;
&lt;script&gt;
 new window.EmbeddedSandbox({
   target: &quot;#sandbox&quot;,
   // Pass through your server href if you are embedding on an endpoint.
   // Otherwise, you can pass whatever endpoint you want Sandbox to start up with here.
   initialEndpoint: window.location.href,
 });
 // advanced options: https://www.apollographql.com/docs/studio/explorer/sandbox#embedding-sandbox
&lt;/script&gt;</code></pre>



<h3 class="wp-block-heading"><a href="#embed-sandbox-by-default-for-apollo-server" aria-hidden="true" class="aal_anchor" id="embed-sandbox-by-default-for-apollo-server"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Embed Sandbox by default for Apollo Server</h3>



<p>If you’re using Apollo Server, you can easily turn on embedding for Sandbox with<a href="https://github.com/apollographql/apollo-server/blob/main/CHANGELOG.md#v380"> a new embed parameter</a> that we released in v3.8.0. This will be the default experience in Apollo Server 4.</p>



<pre class="wp-block-prismatic-blocks"><code class="language-javascript">const {
 ApolloServerPluginLandingPageProductionDefault,
 ApolloServerPluginLandingPageLocalDefault
} = require(&#039;apollo-server-core&#039;);

const server = new ApolloServer({
 ...
 plugins: [
    process.env.NODE_ENV === &quot;production&quot;
      ? ApolloServerPluginLandingPageProductionDefault({
          embed: true,
          graphRef: &quot;plaid-gufzoj@current&quot;
        })
      : ApolloServerPluginLandingPageLocalDefault({ embed: true })
 ]
});</code></pre>



<h3 class="wp-block-heading"><a href="#embed-using-react-soon" aria-hidden="true" class="aal_anchor" id="embed-using-react-soon"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Embed using React (soon!)</h3>



<p>We will be releasing a React component for embedded Sandbox that you will be able to import from our <code>@apollo/sandbox</code> package in the near future. We will update this blog post with some example code when it’s available.</p>



<h2 class="wp-block-heading"><a href="#more-than-just-an-ide" aria-hidden="true" class="aal_anchor" id="more-than-just-an-ide"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>More than just an IDE</h2>



<p>We know there are a number of GraphQL IDEs to pick from these days&#8230; and we know we’re biased, but we’re particularly excited to bring Sandbox to you because it’s so much more than just an IDE.</p>



<h3 class="wp-block-heading"><a href="#saved-operations-in-the-cloud-%e2%98%81%ef%b8%8f" aria-hidden="true" class="aal_anchor" id="saved-operations-in-the-cloud-%e2%98%81%ef%b8%8f"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Saved operations (in the cloud) ☁️</h3>



<p>Over the years, we’ve met many developers who have told us they were scared to restart their computer or clear their browser cookies because they didn’t want to lose their queries in GraphiQL/Playground.</p>



<p>It’s 2022, and we figured that it’s about time for that to be a problem of the past. 🕰️</p>



<p>Connect your local Sandbox to your Studio account to <strong>save operations in the cloud</strong> and never worry about losing your work again.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="609" src="https://wp.apollographql.com/wp-content/uploads/2022/06/image4-opt-1024x609.png" alt="" class="wp-image-14169" srcset="https://wp.apollographql.com/wp-content/uploads/2022/06/image4-opt-1024x609.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/06/image4-opt-300x179.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/06/image4-opt-768x457.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/06/image4-opt-1536x914.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/06/image4-opt-1200x714.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/06/image4-opt.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#schema-diffs-checks" aria-hidden="true" class="aal_anchor" id="schema-diffs-checks"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Schema diffs &amp; checks</h3>



<p>Have you ever worked with a schema so large it was distributed across multiple files or maybe even multiple repos? What about a GraphQL server that generates its schema from code and doesn’t even have an SDL file?</p>



<p>When developing graphs, sometimes all you want is a simple schema diff. But due to the implementation details of our graphs, that’s not always easy to accomplish. So we built it right into Sandbox.</p>



<p>You can diff your local schema against any graph in Apollo Studio, and if the changes look good, you can even run <a href="https://www.apollographql.com/docs/studio/schema-checks">schema checks</a> from Sandbox to make sure they pass CI before checking them into code.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="609" src="https://wp.apollographql.com/wp-content/uploads/2022/06/image2-opt-1024x609.png" alt="" class="wp-image-14161" srcset="https://wp.apollographql.com/wp-content/uploads/2022/06/image2-opt-1024x609.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/06/image2-opt-300x179.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/06/image2-opt-768x457.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/06/image2-opt-1536x914.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/06/image2-opt-1200x714.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/06/image2-opt.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#automatic-schema-reference" aria-hidden="true" class="aal_anchor" id="automatic-schema-reference"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Automatic schema reference</h3>



<p>One of the best properties of GraphQL is that it’s self-documenting. We’ve always felt like squashing graph docs alongside a query IDE just didn’t do enough justice to the act of exploring the graph or referencing something in particular. That’s why we built a full-fledged automatic schema reference tool in Studio.</p>



<p>Sandbox also comes with Studio’s schema reference tool:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="609" src="https://wp.apollographql.com/wp-content/uploads/2022/06/image1-optimized-1024x609.png" alt="" class="wp-image-14163" srcset="https://wp.apollographql.com/wp-content/uploads/2022/06/image1-optimized-1024x609.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-optimized-300x179.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-optimized-768x457.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-optimized-1536x914.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-optimized-1200x714.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-optimized.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#apollo-explorer" aria-hidden="true" class="aal_anchor" id="apollo-explorer"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Apollo Explorer</h3>



<p>And of course, Sandbox has the Apollo Explorer and every feature we’ve built into it over the last several years.<a href="https://www.apollographql.com/docs/studio/explorer/explorer"> Explorer</a> is by far the most sophisticated GraphQL IDE in the ecosystem.</p>



<p>We love Explorer so much because it’s not just a playground for you to query graphs, it’s a playground for us as developers to build the things we always felt were missing from GraphQL tooling. As developers, there’s so much power we’ve gotten used to having in our IDEs and the GraphQL DX is still catching up in a lot of ways. We get new ideas every week about how to improve the Explorer just from using it ourselves.</p>



<p>Explorer has become a passion project of ours, and it is our expression of love for the GraphQL DX itself.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="609" src="https://wp.apollographql.com/wp-content/uploads/2022/06/image3-opt-1024x609.png" alt="" class="wp-image-14165" srcset="https://wp.apollographql.com/wp-content/uploads/2022/06/image3-opt-1024x609.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/06/image3-opt-300x179.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/06/image3-opt-768x457.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/06/image3-opt-1536x914.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/06/image3-opt-1200x714.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/06/image3-opt.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p><strong>That’s all for now folks!</strong></p>



<p>We’re very happy to be bringing this to you today. It’s the culmination of a couple of years of dreaming within the Apollo zoom tunnels, now turned into reality. We’d love to see what you do with Sandbox and where you take your graphs. ❤️</p>



<p>Tweet at us and share what you build! 🐦</p>



<p>As always, happy querying 👋 </p>


How to use Apollo Sandbox on your localhost


<p><strong>Embed private graphs, use embeds to invite new users, and use improved Apollo Client Dev Tools.</strong></p>



<p>Explorer is an incredible GraphQL IDE that makes it quick and easy to browse schemas and run operations against them. It’s so awesome, that our community asked us to make it embeddable so that it could be used anywhere – and last year, <a href="https://www.apollographql.com/blog/announcement/platform/embed-apollo-explorer-anywhere/">we did just that</a>! But at the time, you could only embed public graph variants. Now, we are happy to announce that you can embed Explorer on <strong>any website</strong> with <strong>any graph variant</strong> – even private variants!&nbsp;</p>



<p>You can provide the experience of Explorer on any of your internal or external documentation, dev portals, and websites to onboard new consumers to your graphs.</p>



<h2 class="wp-block-heading"><a href="#embedding-the-explorer-graphql-ide" aria-hidden="true" class="aal_anchor" id="embedding-the-explorer-graphql-ide"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Embedding the Explorer GraphQL IDE</strong></h2>



<p>To embed Explorer for a specific graph, first open Explorer for that graph in Apollo Studio. Click on the chevron next to the share icon in the editor pane and select “Share as embed”. This will open a modal that gives you a few different options for embedding.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="235" src="https://wp.apollographql.com/wp-content/uploads/2022/06/image1-1024x235.png" alt="" class="wp-image-14019" srcset="https://wp.apollographql.com/wp-content/uploads/2022/06/image1-1024x235.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-300x69.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-768x176.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-1536x352.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-1200x275.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1-1980x454.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/06/image1.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>💡Embedded Explorer uses the graph ref from Apollo Studio. Since your graph is registered in Studio, embedded Explorer is always kept up to date with the schema changes in Studio. You can take your schema anywhere by embedding Explorer while Studio’s registry acts as its single source of truth behind the scenes. How neat is that?!</p>



<h3 class="wp-block-heading"><a href="#how-does-embedded-explorer-work-for-private-graph-variants" aria-hidden="true" class="aal_anchor" id="how-does-embedded-explorer-work-for-private-graph-variants"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How does embedded Explorer work for private graph variants?</h3>



<p>If the graph variant you want to embed isn’t public (meaning it’s gated behind Studio authentication), then the embedded Explorer will request the visitor to authorize access before proceeding.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1425" height="861" src="https://wp.apollographql.com/wp-content/uploads/2022/06/image2.gif" alt="" class="wp-image-14021"/></figure>



<p>If the visitor has never interacted with Apollo Studio before &#8211; no problem! They can sign up and be invited from the embed itself.</p>



<p>If your Studio org is using SSO, users are invited with the role that is default selected for your org.&nbsp;</p>



<p>Otherwise, while copying the embed code from the modal in Apollo Studio, admins can configure whether they would like to invite visitors to the organization and select the role to invite with.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1431" height="791" src="https://wp.apollographql.com/wp-content/uploads/2022/06/image3.gif" alt="" class="wp-image-14023"/></figure>



<h3 class="wp-block-heading"><a href="#share-operation-collections-with-embedded-explorer" aria-hidden="true" class="aal_anchor" id="share-operation-collections-with-embedded-explorer"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Share operation collections with embedded Explorer</h3>



<p>As the person embedding Explorer, graph producers can <a href="https://www.apollographql.com/blog/announcement/platform/save-and-share-your-graphql-operations-in-apollo-explorer/">share collections of example operations</a> to get their consumers started. Any collection in the “Shared” workspace will be available as default once the embedded Explorer is made available. Visitors can also create their personal collections by signing in.</p>



<h2 class="wp-block-heading"><a href="#improved-explorer-in-apollo-client-dev-tools" aria-hidden="true" class="aal_anchor" id="improved-explorer-in-apollo-client-dev-tools"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Improved Explorer in Apollo Client Dev Tools</strong></h2>



<p>With this release, we have also improved the Apollo Client Dev Tools by enabling it to securely pull in a graph ref from Apollo Studio if it is unable to introspect the graph from the browser.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="800" height="500" src="https://wp.apollographql.com/wp-content/uploads/2022/06/dev-tools-embed.gif" alt="" class="wp-image-14025"/></figure>



<h2 class="wp-block-heading"><a href="#start-embedding-your-graphs-with-explorer-today" aria-hidden="true" class="aal_anchor" id="start-embedding-your-graphs-with-explorer-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Start embedding your graphs with Explorer today!</strong></h2>



<p>Sharing graphs with a broader audience using Apollo Explorer’s amazing experience could not get any easier. <a href="https://studio.apollographql.com/sandbox/explorer?endpoint=https%3A%2F%2Fapi.spacex.land%2Fgraphql%2F&amp;explorerURLState=N4IgJg9gxgrgtgUwHYBcQC4QEcYIE4CeABADICGMSUAFggM5HAA6SRRANhVbQ862xy40A%2BgQRk8LAUTgBLOnVkQkwpGURSiAXxZaQAGhAA3CbLIAjdvQwgQWoA">Head over to Apollo Studio</a> and get started! For detailed instructions on embedding Explorer, check out the <a href="https://www.apollographql.com/docs/studio/explorer/embed-explorer/">docs</a>. As always, we love hearing from you, so if you have any feedback, please drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>



<p><strong>⚠️  Note</strong>: Make sure you are on the latest version of the UI. Click on the bell icon at the top right corner of Studio and if you see “Update available, click to relaunch” at the bottom left of the modal then click that to get the latest version.</p>


Improved embedding for Apollo Explorer!


<p>We’ve had a busy month at Apollo. Over the last several weeks we’ve released some significant updates to the Apollo stack. Last month we shipped <a href="https://www.apollographql.com/blog/announcement/backend/apollo-federation-2-is-now-generally-available/">Federation 2</a>, a sophisticated and more flexible approach to GraphQL composition. And last week we made <a href="https://www.apollographql.com/blog/announcement/platform/contracts-are-now-generally-available/">Contracts</a> generally available, a way to tailor your graph to specific use cases like mobile development or creating public GraphQL APIs.</p>



<p>Today we’re launching updates to two more components of our stack: the <a href="https://apollographql.com/blog/apollo-router-is-now-generally-available">GA release of Apollo Router</a> – our new high-performance runtime for federated GraphQL APIs – and a <a href="https://apollographql.com/blog/schema-checks-and-launches-are-now-available-for-free-in-apollo-studio/">new cloud-hosted build pipeline</a> for delivering changes to a graph.</p>



<p>We’ve been building these tools together to help teams implement a more advanced GraphQL architecture – one that delivers essential capabilities for operating mission-critical graphs in organizations with many teams, programming languages, and technologies. That architecture is now at the heart of API strategy at companies like Netflix, Walmart, Expedia, Zillow, RetailMeNot, Paypal, Major League Baseball, and many more.&nbsp;</p>



<p>We think it’s time to give this architecture a name, and after talking about it with the developers that have pioneered this approach in their companies, we’re calling it <strong>the supergraph</strong>.</p>



<h2 class="wp-block-heading"><a href="#the-principles-of-supergraph-architecture" aria-hidden="true" class="aal_anchor" id="the-principles-of-supergraph-architecture"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>The principles of supergraph architecture</h2>



<p>The essential ideas of the supergraph are going to be <a href="https://principledgraphql.com/">pretty familiar to those who’ve been following Apollo for a while</a>. It comes down to three core principles.</p>



<h3 class="wp-block-heading"><a href="#1-a-unified-composition-layer" aria-hidden="true" class="aal_anchor" id="1-a-unified-composition-layer"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>1: a unified composition layer</h3>



<p>The supergraph is a new way to think about implementing GraphQL that goes far beyond the technical benefits of replacing data fetching and BFF code with schema and queries. It’s a unified network of a company’s data, microservices, and digital capabilities that serves as the “composition layer” for the whole organization.&nbsp;</p>



<p>The supergraph empowers everyone to create richer, more engaging experiences for their users and customers by bringing everything into a single point of collaboration.</p>



<h3 class="wp-block-heading"><a href="#2-a-modular-architecture" aria-hidden="true" class="aal_anchor" id="2-a-modular-architecture"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2: a modular architecture</h3>



<p>Supergraph architecture is declarative and modular. Just as React and Kubernetes leverage modularity to scale UI development and service deployment, the supergraph leverages modularity to scale the API layer as it grows beyond a single team.&nbsp;</p>



<p>Apollo Federation has always been about bringing modularity to the API layer – letting you scale a graph without bottlenecking developers on a single monolith or creating a single point of failure.&nbsp;</p>



<p>Of course, Apollo Federation offers a lot of additional advantages along the way: programmable configuration, standardized tooling, analyzable query plans, strict validation at build-time instead of run-time, great support for heterogeneous environments, a structured on-ramp for new developers, and many more.</p>



<h3 class="wp-block-heading"><a href="#3-an-agile-approach" aria-hidden="true" class="aal_anchor" id="3-an-agile-approach"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>3: an agile approach</h3>



<p>The supergraph enables an agile bottom-up approach. Traditionally, APIs tend to be fairly static. Because it’s so hard to change an API, the tendency is to waterfall a design that anticipates future requirements. But products change constantly, driven by evolving user requirements and feedback.&nbsp;</p>



<p>The supergraph works harmoniously with rapidly changing products because it empowers developers to ship schema changes swiftly and safely to support their own initiatives, causing the schema to naturally evolve based on actual usage and the needs of the business.</p>



<h2 class="wp-block-heading"><a href="#on-to-the-supergraph" aria-hidden="true" class="aal_anchor" id="on-to-the-supergraph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>On to the supergraph</h2>



<p>We’ve seen case after case of the supergraph architecture – a unified layer, made from modules, continuously evolving – emerging organically at companies we respect and admire. So we’re focused on this idea of the supergraph and our ambition is to help every team have one. Here’s how all that we’ve been building helps with that goal.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1600" height="800" src="https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane.png" alt="" class="wp-image-20799" srcset="https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane.png 1600w, https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2023/05/supergraph-runtime-plane-1200x600.png 1200w" sizes="auto, (max-width: 1600px) 100vw, 1600px" /></figure>



<h3 class="wp-block-heading"><a href="#apollo-federation-the-spec" aria-hidden="true" class="aal_anchor" id="apollo-federation-the-spec"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Apollo Federation: the spec</h3>



<p>Apollo Federation is our open specification for composing subgraphs – modular GraphQL services – together into a single supergraph. Each subgraph is a self-contained component with its own schema and server, so it can be developed, tested, and deployed independently.&nbsp;</p>



<p>Rather than relying on custom code to combine subgraphs, subgraphs reference and extend each other through a principled set of primitives. Thanks to our incredible developer community, Federation supports subgraphs written in over <a href="https://www.apollographql.com/docs/federation/other-servers">20 programming languages</a> and a growing number of GraphQL-native services and products.</p>



<p><a href="https://www.apollographql.com/blog/announcement/backend/apollo-federation-2-is-now-generally-available/">Federation 2</a> builds on what we’ve learned from our community. It adds more complete support for the GraphQL spec including interfaces and new directives which can eliminate much of the boilerplate code that came with Federation 1.&nbsp;</p>



<p>Federation 2 also streamlines cross-team collaboration with a flexible shared ownership model that allows multiple subgraphs to implement overlapping, complementary parts of types and schemas. New governance directives like <code>@inaccessible</code>, <code>@shareable</code>, and <code>@override</code> give teams fine-grained control over the composition process and resulting supergraph schema.</p>



<p>TLDR; Apollo Federation is now more approachable and incrementally adoptable for anyone interested in building a supergraph, and it scales seamlessly all the way into enterprises with thousands of developers collaborating on the largest rapidly-evolving supergraphs. Check out <a href="https://www.apollographql.com/docs/federation/quickstart/setup/">the Federation quickstart</a> to learn more.</p>



<h3 class="wp-block-heading"><a href="#apollo-router-the-runtime" aria-hidden="true" class="aal_anchor" id="apollo-router-the-runtime"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Apollo Router: the runtime</h3>



<p>So you’ve created a federated schema, but how do you run it? At a minimum, the runtime for a supergraph has to receive client requests, build an execution plan, route requests to the proper subgraphs, assemble the results back together, and return it back to the client. We launched Apollo Gateway — an add-on to Apollo Server — alongside Apollo Federation to serve this purpose, but we quickly realized that we needed to build a more elegant solution that was purpose-built for the task. We decided to call it a <strong>graph router</strong>.</p>



<p>A graph router does far more than a traditional API gateway. Like a relational database, it requires a sophisticated implementation that shields users from unwanted details of execution while still providing a principled way to analyze and control the system when necessary. Critical infrastructure like this is better written in a lower-level systems language that offers a smaller operational footprint, so we opted for Rust instead of Node.js.</p>



<p>At the end of 2021, we released the world’s first and only graph router: Apollo Router. The performance advantages are significant: Apollo Router processes requests with <strong>10x lower latency</strong>, <strong>10x higher throughput</strong>, and <strong>12x lower variance</strong> compared to Apollo Gateway, its JavaScript predecessor. Take a look at the benchmark below to get a sense of how much better it is.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="512" src="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-1024x512.png" alt="" class="wp-image-13769" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1-1200x600.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Response latency vs request throughput for Gateway, Router, and direct-to-subgraph</figcaption></figure>



<p>There are other benefits too, like an <a href="https://www.apollographql.com/docs/router/customizations/rhai">extension facility</a> that lets you replace custom gateway code with configuration (this should sound familiar!) and comprehensive support for <a href="https://www.apollographql.com/docs/router/configuration/tracing">OpenTelemetry</a>.</p>



<p>As of today, <a href="https://apollographql.com/blog/apollo-router-is-now-generally-available">Apollo Router is generally available</a>, free for anyone to use. Check out the <a href="https://www.apollographql.com/docs/router/">Router docs</a> to learn more.</p>



<h3 class="wp-block-heading"><a href="#graphos-studio-the-control-plane" aria-hidden="true" class="aal_anchor" id="graphos-studio-the-control-plane"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>GraphOS Studio: the control plane</h3>



<p>GraphOS Studio is the final piece of the puzzle for building and operating a supergraph. Its delivery pipeline provides the validation, automation, and observability you need to deliver changes rapidly and safely, making it possible to constantly evolve the supergraph schema, particularly when teams leverage and extend each other’s contributions.</p>



<p><a href="https://www.apollographql.com/docs/studio/schema-checks">Schema Checks</a> and <a href="https://www.apollographql.com/docs/studio/launches">Launches</a> prevent breaking changes before they happen by automatically validating your supergraph schema in development and giving visibility into past and in-progress changes to the supergraph.</p>



<p>Previously only available on our Enterprise plan, <a href="https://apollographql.com/blog/schema-checks-and-launches-are-now-available-for-free-in-apollo-studio/">today we are making Studio’s delivery pipeline available to everyone</a>.</p>



<h2 class="wp-block-heading"><a href="#whats-next-for-the-supergraph" aria-hidden="true" class="aal_anchor" id="whats-next-for-the-supergraph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next for the supergraph</h2>



<p>We’re excited to get the core components of the supergraph architecture in your hands. We can’t wait to build with you and we are eager to work together on what’s next.</p>


The supergraph: a new way to think about GraphQL


<p>Apollo Router, the next-generation runtime for our <a href="https://apollographql.com/blog/the-supergraph-a-new-way-to-think-about-graphql">supergraph stack</a>, is here, and it’s fully production-ready.&nbsp;</p>



<p>It’s been about six months since we first unveiled Apollo Router at GraphQL Summit. Since then, we’ve been improving it and testing it to ensure that it’s even more efficient, secure, reliable, and customizable. And today, we’re excited to make Apollo Router generally available.</p>



<h2 class="wp-block-heading"><a href="#what-is-apollo-router" aria-hidden="true" class="aal_anchor" id="what-is-apollo-router"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What is Apollo Router?</h2>



<p>Apollo Router is a supergraph runtime written in Rust that supports <a href="https://apollographql.com/docs/federation/v2">Apollo Federation</a> (v1 or v2) &#8211; a declarative GraphQL architecture that lets you build and collaborate on a unified GraphQL API (a supergraph) in a modular and declarative way. The router is what processes all of the incoming API requests from clients and <em>routes</em> them to the subgraphs that make up the overall supergraph.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="564" src="https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-17-at-10.30.53-AM-1024x564.png" alt="" class="wp-image-13736" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-17-at-10.30.53-AM-1024x564.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-17-at-10.30.53-AM-300x165.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-17-at-10.30.53-AM-768x423.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-17-at-10.30.53-AM-1536x846.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-17-at-10.30.53-AM-1200x661.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-17-at-10.30.53-AM.png 1764w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>You may be thinking, “doesn’t Apollo Gateway already do that?” It does! Apollo Gateway is our Node.js supergraph runtime, and we will continue to support it well into 2023 and likely beyond. But when it comes to routing API requests, speed is the name of the game, and Apollo Router is FAST ⚡️.</p>



<p>In our benchmarks Apollo Router processed requests <strong>10x faster</strong> than Apollo Gateway with<strong> 10x higher throughput</strong> and <strong>90% less variance in latency</strong>. And that’s just the start. We have more improvements coming up on the roadmap that will make it even more efficient.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="512" src="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1024x512.png" alt="" class="wp-image-13733" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3-1200x600.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-3.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#the-apollo-router-operational-experience" aria-hidden="true" class="aal_anchor" id="the-apollo-router-operational-experience"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>The Apollo Router operational experience</h2>



<p>While speed was one of our main goals for Apollo Router, it wasn’t our only goal.</p>



<h3 class="wp-block-heading"><a href="#easier-to-run" aria-hidden="true" class="aal_anchor" id="easier-to-run"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Easier to run</h3>



<p>Apollo Router is easier to manage. Unlike Apollo Gateway, Apollo Router ships as a standalone binary. To use it, you simply download and run it with any valid supergraph schema. This makes containerization and scaling a breeze! We even supply <a href="https://www.apollographql.com/docs/router/containerization/overview">Docker images</a> for every release.</p>



<h3 class="wp-block-heading"><a href="#more-native-functionality" aria-hidden="true" class="aal_anchor" id="more-native-functionality"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>More native functionality</h3>



<p>Apollo Router has a ton of built-in options like CORS controls, header propagation, telemetry, <a href="https://www.apollographql.com/docs/router/configuration/overview">and more</a> that can all be configured with a declarative YAML file! What’s possible with Router today is just the beginning. In future releases, we will be adding even more native functionality like:</p>



<ul class="wp-block-list"><li><code>@defer</code> support</li><li>real-time data</li><li>Studio operation trace reporting</li><li>1st-class caching</li><li>Authentication and authorization</li><li>Multi-language extensibility (write your own plugins in languages other than Rust)</li></ul>



<h3 class="wp-block-heading"><a href="#tracing-and-monitoring" aria-hidden="true" class="aal_anchor" id="tracing-and-monitoring"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Tracing and monitoring</h3>



<p>Apollo Router comes with Studio Reporting, Open Telemetry and Prometheus metrics out of the box.</p>



<p>Alerting on errors or high latencies is now possible via:</p>



<ul class="wp-block-list"><li>Prometheus</li><li>OpenTelemetry Collector (metrics)</li></ul>



<p>In addition, you can diagnose where there are latency issues in your request pipeline by connecting to existing tracing solutions such as:</p>



<ul class="wp-block-list"><li>DataDog</li><li>Jaeger</li><li>OpenTelemetry Collector (tracing)</li><li>Zipkin</li></ul>



<h2 class="wp-block-heading"><a href="#the-apollo-router-developer-experience" aria-hidden="true" class="aal_anchor" id="the-apollo-router-developer-experience"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>The Apollo Router developer experience</h2>



<p>Apollo Router has a rich extensibility model that enables you to add custom functionality when you need to.&nbsp;</p>



<h3 class="wp-block-heading"><a href="#rust-plugins" aria-hidden="true" class="aal_anchor" id="rust-plugins"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Rust plugins</h3>



<p>All of our configurable functionality in Apollo Router is written as plugins, and the very same plugin API is available to you.&nbsp;</p>



<p>Plugins that you write yourself are automatically integrated with the main YAML config giving you a seamless configuration experience.</p>



<p>With the plugin API you could add things like:</p>



<ul class="wp-block-list"><li>Custom authentication</li><li>Custom logging</li><li>Anything you want, as long as you can write the code!</li></ul>



<p>Take a look at our <a href="https://github.com/apollographql/router/tree/main/examples">examples directory</a> to see how it’s done.</p>



<h3 class="wp-block-heading"><a href="#rhai-scripting" aria-hidden="true" class="aal_anchor" id="rhai-scripting"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Rhai scripting</h3>



<p><a href="https://www.apollographql.com/blog/announcement/backend/apollo-router-our-graphql-federation-runtime-in-rust#why-rust">We chose Rust</a> to build Apollo Router because of its memory-safety and performance potential, but we want everyone to be able to write custom plugins, not just Rust enthusiasts like us.&nbsp;</p>



<p>If you need to make small changes to your request pipeline then the experimental Rhai script plugin may save you from needing to compile your own binary.</p>



<p>What you can do:</p>



<ul class="wp-block-list"><li>Manipulate request/response HTTP headers</li><li>Manipulate request/response context</li><li>Perform checkpoint-style short-circuiting of requests</li><li>Modify the status codes of requests/responses</li><li>Modify the body of requests (excluding variables)</li><li>Modify the body of responses</li></ul>



<h2 class="wp-block-heading"><a href="#getting-started-with-apollo-router" aria-hidden="true" class="aal_anchor" id="getting-started-with-apollo-router"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started with Apollo Router</h2>



<p>We can’t wait for you to start using Apollo Router! Depending on where you are in your supergraph journey, here are some next steps you can take to get started:</p>



<ul class="wp-block-list"><li><strong>If you’re already using Apollo Gateway</strong>, check out the <a href="https://www.apollographql.com/docs/router/migrating-from-gateway">migration guide</a>. The migration guide will walk you through how to check if your use case is currently fully supported by Apollo Router.<ul><li>If you find yourself unable to migrate from the Gateway for some reason, we&#8217;d love to understand the obstacles you&#8217;re encountering.&nbsp; Please <a href="https://github.com/apollographql/router/discussions">open a discussion on GitHub</a> if you need general help or <a href="https://github.com/apollographql/router/issues">open an issue</a> if you have any troubles with our instructions.</li><li>In future Router releases, we’ll be enhancing Router’s built-in Gateway migration support. Keep an eye on future <a href="https://github.com/apollographql/router/releases">releases</a>.</li></ul></li><li><strong>If you’re starting fresh with the Router</strong>, see our <a href="https://www.apollographql.com/docs/router/quickstart">Quickstart docs</a>.&nbsp;</li><li><strong>If you don’t have a supergraph schema yet and want to learn more about Apollo Federation</strong>, head over to the <a href="https://apollographql.com/docs/federation/v2">Federation docs</a>.</li></ul>


Apollo Router is now generally available


<p>Today, we’re updating Apollo Studio to make its <a href="https://apollographql.com/blog/the-supergraph-a-new-way-to-think-about-graphql">supergraph</a> delivery pipeline, including <a href="https://www.apollographql.com/docs/studio/schema-checks">Schema Checks</a> and <a href="https://www.apollographql.com/docs/studio/launches">Launches</a>, available for anyone to use for free.</p>



<p>We’ve made a lot of exciting announcements about supergraphs recently. In April, we announced the <a href="https://apollographql.com/blog/apollo-federation-2-is-now-generally-available/">general availability of Federation 2</a>, an improved version of Federation that makes it easier for anyone to build a supergraph. And just today, we announced <a href="https://apollographql.com/blog/apollo-router-is-now-generally-available">general availability of Apollo Router</a>, our next generation supergraph runtime written in Rust. </p>



<p>With Federation and Router, anyone can build and run a supergraph. But the needs of your users evolve rapidly, and like any other layer of your stack, your supergraph needs to evolve with them. That’s where Apollo Studio comes in.</p>



<h2 class="wp-block-heading"><a href="#optimized-for-iteration-the-supergraph-delivery-pipeline" aria-hidden="true" class="aal_anchor" id="optimized-for-iteration-the-supergraph-delivery-pipeline"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Optimized for iteration: the supergraph delivery pipeline</h2>



<p>The days of lockstep deployments are over. Teams need the ability to deploy changes many times a day without worrying about breaking production.&nbsp;</p>



<p>We built Apollo Studio’s delivery pipeline to help you evolve and iterate on your supergraph schema with speed and confidence. It’s a single source of truth that provides the automation, validation, and observability you need to deliver changes rapidly and safely. After building a supergraph and adopting a Studio’s delivery pipeline, <a href="http://apollographql.com/customers/retailmenot">RetailMeNot</a> saw a 7X reduction in time spent deploying schema changes and eliminated production outages. Schema Checks and Launches are two core delivery features that make this possible.</p>



<h3 class="wp-block-heading"><a href="#schema-checks" aria-hidden="true" class="aal_anchor" id="schema-checks"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Schema checks</h3>



<p>Schema checks validate changes to your supergraph schema so that you can be confident that it&#8217;s ready for production. There are two types of schema checks that Apollo Studio runs for supergraphs: composition checks and operation checks.</p>



<p>Composition checks validate that subgraphs compose successfully into the overall Supergraph schema. If composition succeeds, operation checks then validate that your composed supergraph schema will serve all of your client applications by checking it against historical operations on your supergraph.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="512" src="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-1024x512.png" alt="" class="wp-image-13725" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-1024x512.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-300x150.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-768x384.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-1536x768.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4-1200x600.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-4.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>The best part: schema checks can be run within existing CI/CD tools using Apollo’s Rover CLI to create a seamless integration with your existing software delivery pipelines.</p>



<h3 class="wp-block-heading"><a href="#launches" aria-hidden="true" class="aal_anchor" id="launches"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Launches</h3>



<p>One of the fantastic benefits of GraphQL that a supergraph inherits is that it’s versionless. But even without a version, it’s still extremely important to understand how your supergraph has evolved over time and if new changes are live. Launches in Apollo Studio are how you do that.</p>



<p>Launches give you a way to reason about the lifecycle of your supergraph. In Apollo Studio, a launch represents the complete process of an update to your deployed supergraph running through Studio’s delivery pipeline. An update to your supergraph could include:</p>



<ul class="wp-block-list"><li>Adding, removing, or modifying types and fields in a subgraph schema</li><li>Adding or removing entire subgraphs</li><li>Migrating types or fields between subgraphs</li></ul>



<p>The Launches page in Apollo Studio gives you visibility into in-progress and past launches for your supergraph. It’s a dashboard that summarizes how launches over time have evolved your supergraph, helping you track when new changes are reflected in production and debug when something goes wrong.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="616" src="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-1024x616.png" alt="" class="wp-image-13727" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-1024x616.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-300x180.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-768x462.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-1536x924.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5-1200x722.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/Frame-5.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#the-supergraph-pipeline-for-everyone" aria-hidden="true" class="aal_anchor" id="the-supergraph-pipeline-for-everyone"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>The supergraph pipeline for everyone</h2>



<p>Supergraphs are transformational for developers, and we believe that everyone should be able to start building one. To make that a reality, as of today Apollo Studio’s end-to-end delivery pipeline is now available to everyone.</p>



<p>You can start using Schema Checks and Launches for free in Apollo Studio today. For instructions on how to get started, head over to the <a href="https://www.apollographql.com/docs/studio/schema-checks">Schema Checks</a> and <a href="https://www.apollographql.com/docs/studio/launches">Launches</a> docs.</p>



<p>If you don’t have a supergraph yet, check out <a href="https://apollographql.com/blog/the-supergraph-a-new-way-to-think-about-graphql">this post</a> to learn about Apollo’s supergraph stack and how to get started!</p>


Schema Checks and Launches are now available for free in Apollo Studio


<p>At GraphQL Summit last year, we announced the <a href="https://www.apollographql.com/blog/announcement/platform/introducing-contracts-serve-many-audiences-with-a-unified-graph/">preview release of Contracts</a> on Apollo’s Enterprise plan. Contracts allow you to create tailored graphs for different audiences by applying filters to a single unified graph. Today, we are excited to announce that Contracts are generally available!</p>



<h2 class="wp-block-heading"><a href="#one-graph-many-representations" aria-hidden="true" class="aal_anchor" id="one-graph-many-representations"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>One graph &#8211; many representations</strong></h2>



<p>Building a unified graph is incredibly beneficial. It gives you a single source of truth for all your organization’s data, services, and business capabilities and allows developers to deliver better, faster apps with less overhead. However, unification can introduce new challenges at scale:</p>



<ul class="wp-block-list"><li>How do you create varying levels of access for different personas or types of users like customers, employees, suppliers, or partners?</li><li>How do you provide partners and public API users with a schema scoped for their integration and app development needs?</li><li>How do you maintain client-specific BFFs and experience-driven schemas alongside a canonical domain-driven schema?</li><li>How do you restrict access to experimental or non-stable parts of the graph, but still allow access for testing and early adopters?</li></ul>



<p>In summary, <strong>“how do I serve multiple different audiences with a single graph?”</strong> The answer: <strong>Contracts</strong>!</p>



<p>Using Contracts, you can take your unified graph and create filtered variants of that graph that contain only a subset of its types and fields. Contracts can power separate graphs for partner developers, specific client applications, public APIs, experimental features, and more without losing any of the benefits of the unified graph.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="2118" height="972" src="https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM.png" alt="" class="wp-image-13587" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM.png 2118w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-300x138.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-1024x470.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-768x352.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-1536x705.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-2048x940.png 2048w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-1200x551.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/Screen-Shot-2022-05-10-at-6.54.35-PM-1980x909.png 1980w" sizes="auto, (max-width: 2118px) 100vw, 2118px" /></figure>



<h2 class="wp-block-heading"><a href="#whats-new-in-contracts" aria-hidden="true" class="aal_anchor" id="whats-new-in-contracts"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>What’s new in Contracts?</strong></h2>



<p>Since announcing the preview, we’ve been hard at work making sure that Contracts integrates seamlessly with all of the other great features of Apollo Studio. We’ve even added in some net new functionality based on customer feedback! Here are some of the improvements we’ve made:</p>



<h3 class="wp-block-heading"><a href="#contract-launches" aria-hidden="true" class="aal_anchor" id="contract-launches"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Contract Launches</h3>



<p>Earlier this year we added <a href="https://www.apollographql.com/blog/announcement/platform/introducing-contract-launches-see-the-lifecycle-of-contract-schemas-in-apollo-studio/">Contract Launches</a> to the Launches dashboard in Apollo Studio. This gives you full visibility into the lifecycle of your contract schemas and helps you understand which contracts launched from a given source variant.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="572" src="https://wp.apollographql.com/wp-content/uploads/2022/05/image5-1024x572.png" alt="" class="wp-image-13589" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/image5-1024x572.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5-300x167.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5-768x429.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5-1536x858.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5-1200x670.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5-1980x1105.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/05/image5.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#support-for-federation-2-and-tagging-additional-schema-elements" aria-hidden="true" class="aal_anchor" id="support-for-federation-2-and-tagging-additional-schema-elements"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Support for Federation 2 and tagging additional schema elements</h3>



<p>In case you missed it, <a href="https://www.apollographql.com/blog/announcement/backend/apollo-federation-2-is-now-generally-available/">Federation 2</a> &#8211; with a much improved shared ownership model, enhanced type merging, and cleaner syntax for a smoother developer experience &#8211; was made generally available recently. If you have migrated your graph variants to Federation 2, you can now create contracts from them.&nbsp;</p>



<p>Additionally, if your graph variants are on Federation 2, you can hide additional schema elements like input arguments, input types and fields and enums, which is currently not possible with Federation 1. </p>



<h3 class="wp-block-heading"><a href="#filter-previews" aria-hidden="true" class="aal_anchor" id="filter-previews"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Filter previews</h3>



<p>We have also added the ability to see a <em>before</em> and <em>after</em> view of your contract schema once you have applied your filter configurations. This will allow you to quickly verify the changes you are making against the source variant schema or latest successful contract schema.&nbsp;</p>



<p>When creating or updating a contract schema, you can click on Generate Preview to see the number of types and fields the proposed contract schema will have. You can also see any errors that occur when generating the contract schema with the selected filter configuration.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="762" src="https://wp.apollographql.com/wp-content/uploads/2022/05/image1-1024x762.png" alt="" class="wp-image-13591" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/image1-1024x762.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/image1-300x223.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/image1-768x572.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/image1-1536x1143.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/image1-1200x893.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/image1.png 1620w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>On proceeding to Review, you can now see the changes that are being made based on the selected filter configuration. You can compare your proposed changes to the contract schema against the last successful contract schema build or to the source variant schema. </p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="820" src="https://wp.apollographql.com/wp-content/uploads/2022/05/image3-1024x820.png" alt="" class="wp-image-13593" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/image3-1024x820.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/image3-300x240.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/image3-768x615.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/image3-1536x1230.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/image3-1200x961.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/image3.png 1618w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>You can also select whether you want to compare API Schema or Supergraph Schema.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="774" src="https://wp.apollographql.com/wp-content/uploads/2022/05/image2-1024x774.png" alt="" class="wp-image-13595" srcset="https://wp.apollographql.com/wp-content/uploads/2022/05/image2-1024x774.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/05/image2-300x227.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/05/image2-768x581.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/05/image2-1536x1161.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/05/image2-1200x907.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/05/image2.png 1706w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Getting Started</strong></h2>



<p>Contracts are generally available today on Apollo’s Enterprise plan! To learn how to create your first contract, check out our documentation.</p>



<p>To get the most out of Contracts, we recommend migrating your source variants (from which contracts schemas are created) to Federation 2. Federation 1 supports Contracts as well, but it does not support tagging of input and enum types and fields.</p>



<p>If you aren’t on Apollo Enterprise and would like to try it out, <a href="https://www.apollographql.com/contact-sales/">talk to us</a> about an Enterprise trial.</p>



<p><strong>⚠️ Note:</strong> Make sure you are on the latest version of the UI. Click on the bell icon at the top right corner of Studio and if you see “Update available, click to relaunch” at the bottom left of the modal then click that to get the latest version.</p>



<p><em>(Contracts are patent pending)</em></p>


Contracts are now generally available


<p>The momentum continues to build around Apollo Federation with over 1M weekly downloads and 18K+ projects now using Apollo Federation, up 50% in the last 5 months since <a href="https://www.apollographql.com/blog/announcement/backend/announcing-federation-2/">Federation 2 was first announced</a>.&nbsp;</p>



<p>We’d like to extend a big thank you to our community! Because of your contributions, Federation developers can compose subgraphs written in <a href="https://www.apollographql.com/docs/federation/v2/other-servers">over 18 languages and frameworks</a>!</p>



<p><strong>Today, we’re excited to announce the general availability of Apollo Federation 2, with improvements across the entire Apollo platform including Gateway 2.0, the Rover CLI, and Apollo Studio.</strong>&nbsp;</p>



<p>Keep reading to learn more about Federation and what you can expect from the new improvements in Federation 2 or head to our docs to <a href="https://www.apollographql.com/docs/federation/v2/">get started today</a>! 🚀</p>



<h2 class="wp-block-heading"><a href="#whats-new-in-apollo-federation-2" aria-hidden="true" class="aal_anchor" id="whats-new-in-apollo-federation-2"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What&#8217;s new in Apollo Federation 2</h2>



<p>Apollo Federation is a <a href="https://www.apollographql.com/docs/federation/v2">modular GraphQL architecture</a> that powers the world’s most important graphs, including <a href="https://netflixtechblog.com/how-netflix-scales-its-api-with-graphql-federation-part-2-bbe71aaec44a">Netflix</a>, <a href="https://medium.com/walmartglobaltech/federated-graphql-walmart-bfc85c2553de">Walmart</a>, <a href="https://medium.com/adobetech/graphql-making-sense-of-enterprise-microservices-for-the-ui-46fc8f5a5301">Adobe</a>, and <a href="https://www.apollographql.com/docs/federation/enterprise-guide/federation-case-studies/">more</a>.&nbsp;</p>



<p>Designed in collaboration with the GraphQL community, Federation 2 is a clean-sheet implementation of the core composition and query-planning engine at the heart of Apollo Federation.&nbsp;</p>



<p>The new version builds on the success of the original with an improved shared ownership model, enhanced type merging, and cleaner syntax for a smoother developer experience. It’s backward compatible and designed for incremental adoption one subgraph at a time.</p>



<h3 class="wp-block-heading"><a href="#build-with-a-smoother-developer-experience" aria-hidden="true" class="aal_anchor" id="build-with-a-smoother-developer-experience"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Build with a smoother developer experience</h3>



<p>Federation 2 adds first-class support for shared interfaces, enums, and other value types. Common tasks like extending a federated type are now possible without special directives and keywords, resulting in cleaner syntax.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1999" height="798" src="https://wp.apollographql.com/wp-content/uploads/2022/04/image2.png" alt="" class="wp-image-13169" srcset="https://wp.apollographql.com/wp-content/uploads/2022/04/image2.png 1999w, https://wp.apollographql.com/wp-content/uploads/2022/04/image2-300x120.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/04/image2-1024x409.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/04/image2-768x307.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/04/image2-1536x613.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/04/image2-1200x479.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/04/image2-1980x790.png 1980w" sizes="auto, (max-width: 1999px) 100vw, 1999px" /></figure>



<h3 class="wp-block-heading"><a href="#deliver-smaller-increments-with-better-shared-types" aria-hidden="true" class="aal_anchor" id="deliver-smaller-increments-with-better-shared-types"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Deliver smaller increments with better shared types</h3>



<p>Apollo Federation’s shared ownership model lets you spread a federated type across subgraphs so that you can reuse common value types like interfaces and enums. Federation 2 improves upon the shared ownership model and makes shared types more flexible:</p>



<p><strong>Value type definitions are now merged into a single unified type</strong>. Value types don’t need to be identical across subgraphs, so smaller incremental changes, like adding a field, can often be rolled out one subgraph at a time by using the <code>@inaccessible</code> directive to hide it from the client-facing schema.</p>



<p><strong>All types are shared equally across subgraphs</strong>. This means you don’t have to use the <code>extend</code> keyword.</p>



<p><strong>All fields have a single source of truth by default. </strong>You can optionally mark a field or object with the <code>@shareable</code> directive&nbsp; so other subgraphs can resolve them, which may increase performance.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1999" height="874" src="https://wp.apollographql.com/wp-content/uploads/2022/04/image3.png" alt="" class="wp-image-13171" srcset="https://wp.apollographql.com/wp-content/uploads/2022/04/image3.png 1999w, https://wp.apollographql.com/wp-content/uploads/2022/04/image3-300x131.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/04/image3-1024x448.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/04/image3-768x336.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/04/image3-1536x672.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/04/image3-1200x525.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/04/image3-1980x866.png 1980w" sizes="auto, (max-width: 1999px) 100vw, 1999px" /></figure>



<h3 class="wp-block-heading"><a href="#migrate-fields-across-subgraphs-without-downtime-or-coordinated-delivery" aria-hidden="true" class="aal_anchor" id="migrate-fields-across-subgraphs-without-downtime-or-coordinated-delivery"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Migrate fields across subgraphs without downtime or coordinated delivery</h3>



<p>As the shape of your subgraphs change, sometimes fields need to be migrated from one subgraph to another. This previously required a coordinated release across subgraphs to avoid downtime. </p>



<p>With Federation 2, field migration is painless. Simply add the field to the destination subgraph, mark it with <code>@override</code> to accept production traffic without downtime, and remove the migrated field from the old subgraph.</p>



<h3 class="wp-block-heading"><a href="#catch-errors-sooner-with-improved-static-analysis" aria-hidden="true" class="aal_anchor" id="catch-errors-sooner-with-improved-static-analysis"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Catch errors sooner with improved static analysis</h3>



<p>Federation 2 has deeper static analysis, better error messages, and a new generalized composition model that helps you catch more errors at build-time instead of at runtime. The rewritten composition engine now validates all theoretically possible queries and provides more descriptive error messages when a query can’t be satisfied. New composition hints help you understand how schema definitions influence query planning and performance.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1999" height="945" src="https://wp.apollographql.com/wp-content/uploads/2022/04/image1.png" alt="" class="wp-image-13173" srcset="https://wp.apollographql.com/wp-content/uploads/2022/04/image1.png 1999w, https://wp.apollographql.com/wp-content/uploads/2022/04/image1-300x142.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/04/image1-1024x484.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/04/image1-768x363.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/04/image1-1536x726.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/04/image1-1200x567.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/04/image1-1980x936.png 1980w" sizes="auto, (max-width: 1999px) 100vw, 1999px" /></figure>



<p>While Federation 2 is backwards compatible, its enhanced validation might <a href="https://www.apollographql.com/docs/federation/v2/federation-2/backward-compatibility#breaking-changes">catch a few things</a> that the original Federation didn’t. Things you’ll be happy to know about!</p>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started</h2>



<p>⚠️ <strong>Note: The Apollo Contracts preview does not yet support Federation 2. If you are using Contracts in production you should not upgrade to Federation 2 yet. The generally available release of Contracts will include support for Federation 2.</strong></p>



<p>Moving to Federation 2 is a simple and incremental process:</p>



<ol class="wp-block-list"><li><strong>Upgrade your Gateways to version 2.0.0 or later.</strong> Gateway 2 is backward compatible with Federation 1 and any existing customizations you have, so this won’t break anything.</li><li><strong>Turn on Federation 2 composition</strong> for the Rover CLI and Apollo Studio. Federation 2 composition will automatically convert Federation 1 subgraphs, so you can get some great benefits (like improved error messages) without upgrading any subgraphs! 🎉</li><li><strong>Upgrade individual subgraphs to Federation 2 syntax at your own pace</strong>. Because Federation 2 composition is backward compatible with Federation 1 subgraphs, you can add Federation 2 syntax to your subgraphs at your own pace.</li></ol>



<p>💡 You can find detailed instructions for the steps above in our <a href="https://www.apollographql.com/docs/federation/v2/federation-2/moving-to-federation-2"><strong>migration guide</strong></a>.</p>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next</h2>



<p>If you&#8217;re already using Apollo Federation 1.x, check out <a href="https://www.apollographql.com/docs/federation/v2/federation-2/moving-to-federation-2">our migration guide docs</a> to start taking advantage of the benefits from Federation 2. If you&#8217;re interested in trying things out, check out our <a href="https://www.apollographql.com/docs/federation/v2/quickstart/setup">quickstart docs</a> or our full <a href="https://github.com/apollographql/supergraph-demo-fed2">supergraph demo for Federation 2</a> that includes a complete enterprise-grade example.</p>



<p>Check out our public <a href="https://github.com/apollographql/federation/blob/main/ROADMAP.md">Federation Roadmap</a> to learn about&nbsp; upcoming releases. We’d love to hear your thoughts! <a href="https://github.com/apollographql/federation/issues">Open a GitHub issue</a> to share your feedback.</p>



<h2 class="wp-block-heading"><a href="#get-involved" aria-hidden="true" class="aal_anchor" id="get-involved"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get involved!</h2>



<p>If you’re interested in getting involved or becoming a contributor,&nbsp; checkout our GitHub repos and community forums:</p>



<ul class="wp-block-list"><li><a href="https://github.com/apollographql/federation">GitHub</a></li><li><a href="https://community.apollographql.com/">Apollo Community Forum</a></li><li><a href="https://community.apollographql.com/t/apollo-federation-2-compatibility-showcasing-community-libraries/3272">Subgraph Library Maintainer Support</a></li></ul>



<p></p>


Apollo Federation 2 is now generally available


<p>At last year’s GraphQL Summit we announced the alpha release of <a href="https://www.apollographql.com/blog/announcement/backend/apollo-router-our-graphql-federation-runtime-in-rust/">Apollo Router</a> for the first time &#8211; our new, high-performance Federation runtime written in Rust. Today, we’re excited to bring Apollo Router out of Alpha and into an open preview!</p>



<h2 class="wp-block-heading"><a href="#what-does-the-apollo-router-preview-mean-for-you" aria-hidden="true" class="aal_anchor" id="what-does-the-apollo-router-preview-mean-for-you"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What does the Apollo Router preview mean for you?</h2>



<p>If you’re currently running a federated supergraph with Apollo Gateway, Apollo Router gives you a leaner, high-performance runtime option for Federation (both Federation 1 and <a href="https://www.apollographql.com/blog/apollo-federation-2-and-gateway-2-0-are-now-available-in-preview">Federation 2</a>!). Here are a few things to know about the preview release:</p>



<ul class="wp-block-list"><li>Benchmarks show that Apollo Router is <strong>10x faster</strong>, has<strong> 10x higher throughput</strong>, and has <strong>12x less variance</strong> compared to the latest release of Apollo Gateway.</li><li>Apollo Router is ready for use with limited production workloads and proof-of-concepts.</li><li>You can deploy Apollo Router as a standalone binary, making it easier to manage and scale.</li><li>The preview release adds support for more advanced configuration and customization.<ul><li>Simple <a href="https://www.apollographql.com/docs/router/customizations/overview">YAML configuration</a> for CORS, logging, header propagation, routing URLs, OpenTelemetry, and operation usage reporting to Apollo Studio</li><li><a href="https://www.apollographql.com/docs/router/customizations/native">Native Rust plugins for the Apollo Router</a> for maximum flexibility &amp; control.</li><li><a href="https://www.apollographql.com/docs/router/customizations/rhai">Lightweight Rhai scripting</a> for string manipulation, custom header forwarding, and more to come as we fully develop this capability.</li></ul></li><li>Apollo Router offers key integrations with Apollo Studio:<ul><li>Automated supergraph rollout via <a href="https://www.apollographql.com/docs/router/managed-federation/overview">Managed Federation</a> and Apollo Uplink</li><li>Operation-usage &amp; client-awareness reporting via <a href="https://www.apollographql.com/docs/router/configuration/spaceport">a new reporting agent called spaceport</a></li></ul></li><li>Automatic Persisted Queries (APQ) is enabled by default with zero config required and a local, in-memory cache.<ul><li>Existing clients that use APQ will work with Apollo Router which stores persisted queries in an in-memory cache.</li><li>For an overview of the APQ protocol and Client configuration see: <a href="https://www.apollographql.com/docs/apollo-server/performance/apq/">https://www.apollographql.com/docs/apollo-server/performance/apq/</a>&nbsp;</li></ul></li></ul>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="634" src="https://wp.apollographql.com/wp-content/uploads/2022/03/85CCA2D7-DD89-4486-ACDB-CC551769671D-1024x634.png" alt="" class="wp-image-12779" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/85CCA2D7-DD89-4486-ACDB-CC551769671D-1024x634.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/85CCA2D7-DD89-4486-ACDB-CC551769671D-300x186.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/85CCA2D7-DD89-4486-ACDB-CC551769671D-768x475.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/85CCA2D7-DD89-4486-ACDB-CC551769671D-1536x950.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/85CCA2D7-DD89-4486-ACDB-CC551769671D-1200x743.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/85CCA2D7-DD89-4486-ACDB-CC551769671D.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>Apollo Router and Gateway response time</figcaption></figure>



<h2 class="wp-block-heading"><a href="#deploying-apollo-router" aria-hidden="true" class="aal_anchor" id="deploying-apollo-router"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Deploying Apollo Router</h2>



<p>You may be wondering, “how do I get started with Apollo Router?” Good news! Unlike Apollo Gateway, Apollo Router is a standalone binary that’s purpose-built for running federated schemas, so it’s easy to deploy and scale. There are just three steps to get started:</p>



<ol class="wp-block-list"><li>Download Apollo Router</li><li>Make sure your project has a supergraph schema</li><li>Run Apollo Router 🚀</li></ol>



<p>It’s that easy! For the full quickstart guide including downloads and detailed instructions, check out <a href="https://www.apollographql.com/docs/router/">our docs</a>.</p>



<h2 class="wp-block-heading"><a href="#apollo-router-extensibility" aria-hidden="true" class="aal_anchor" id="apollo-router-extensibility"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Apollo Router extensibility</h2>



<p>Using our example is a great way to get started, but if you’ve ever run a supergraph in production with Apollo Gateway, you may have encountered a&nbsp; common challenge: how do you extend your gateway to meet your specific needs. The Gateway has a well-documented extensibility model, but you need to know node.js to take full advantage of it.</p>



<p>With Apollo Router, we want to make extensibility more approachable, which is why plugins can be configured with just a `router.yaml` file. Apollo Router is written in Rust, but things like propagating headers to subgraphs and OpenTelemetry can be configured with the `router.yaml` file without writing any Rust code, with more plugins coming soon.</p>



<p>However, we know that not every use case can be covered with pre-built customizations, so Router also supports lightweight <a href="https://www.apollographql.com/docs/router/customizations/rhai">Rhai scripting</a>. When YAML configuration is insufficient, Rhai scripting allows you to make programmatic customizations without requiring you to recompile the router with a custom Rust plugin.</p>



<h2 class="wp-block-heading"><a href="#where-to-next" aria-hidden="true" class="aal_anchor" id="where-to-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Where to next?</h2>



<p>We’re so excited to have the GraphQL community get their hands on the Apollo Router preview release! It’s going to be a game-changer for building high-performance supergraphs that power the world’s most cutting-edge and creative applications.&nbsp;</p>



<p>When you’re using the preview, please don’t hesitate to drop us your questions and feedback in the Apollo Router <a href="https://github.com/apollographql/router/discussions">GitHub discussion</a> &#8211; it will help us put the final touches on Apollo Router before our GA release 🚀</p>


Apollo Router: our new high-performance Federation runtime is now available in open preview


<p>Last year on popular request, we brought <a rel="noreferrer noopener" href="https://www.apollographql.com/blog/tooling/graphql-ide/were-shipping-3-of-our-most-requested-features/#1-tabs-in-explorer" data-type="URL" data-id="https://www.apollographql.com/blog/tooling/graphql-ide/were-shipping-3-of-our-most-requested-features/#1-tabs-in-explorer" target="_blank">tabs</a> to Explorer. And today, we are taking it up another notch! You can now save your operations in Explorer and share them with your team using Operation Collections!</p>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="Operation Collections: Save and share GraphQL queries" width="580" height="326" src="https://www.youtube.com/embed/o0C5FkT7gk4?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<h2 class="wp-block-heading"><a href="#what-is-an-operation-collection" aria-hidden="true" class="aal_anchor" id="what-is-an-operation-collection"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What is an Operation Collection?</h2>



<p>Operation Collections are a new, <strong>free</strong> feature in Apollo Studio that help you save and organize operations in folders that align to different use cases, client apps, personas and more.&nbsp;</p>



<p>Saving your operations into a collection in Explorer means that you and your team can:</p>



<ul class="wp-block-list"><li>Stop writing the same operation over and over</li><li>Organize common operations by how they&#8217;re used and who uses them</li><li>Design, execute, and share operations all in a single interface</li><li>More easily onboard new team members</li></ul>



<p><img loading="lazy" decoding="async" width="295" height="466" src="https://lh3.googleusercontent.com/L0uf1ugErGINiTA4ZJL-5aUZWg1wkDaRvo7mjx0D7yLhxSmdGdIPmaiFxr-tPo6FR_n8qaaBj3Ht2-mpJj_3nN0BjMSp0V6PPlwFUULCaGnuRfpzFYDqxFpve5pL1l03MWtvlBbY"></p>



<p>Let’s see how!</p>



<h2 class="wp-block-heading"><a href="#creating-a-collection" aria-hidden="true" class="aal_anchor" id="creating-a-collection"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Creating a collection</h2>



<p>To get started, head over to the Explorer in Apollo Studio and select any graph/variant combination that you want to create a collection for. Now let’s create a new collection:</p>



<ol class="wp-block-list"><li>In Explorer on the left panel, click on the bookmark icon and click on <code>+Create collection</code>.&nbsp;</li><li>A collection can be created as Personal or Shared. Personal collections are only visible to you while shared collections are visible to all Studio org members who have access to that variant. Configure collection details in the modal and hit Add.&nbsp;</li><li>That is it! You should see your newly created collection in the Operation Collection index 🥳</li></ol>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1424" height="782" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image1.gif" alt="" class="wp-image-12669"/></figure>



<h2 class="wp-block-heading"><a href="#saving-an-operation" aria-hidden="true" class="aal_anchor" id="saving-an-operation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Saving an operation</h2>



<p>Now let’s save an operation to the newly created collection:</p>



<ol class="wp-block-list"><li>Navigate to any tab in the Explorer with an operation, or build a query using the Explorer’s query builder.&nbsp;</li><li>Click on the save icon in the editor pane, left of the run button. You can also use the keyboard shortcut of <code>Cmd/Ctrl+S</code>.&nbsp;</li><li>Give the operation a name, select the collection to save in, and hit Save!&nbsp;</li><li>Your operation is now saved and available for access within that collection 🎊</li></ol>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1426" height="783" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image2.gif" alt="" class="wp-image-12672"/></figure>



<h2 class="wp-block-heading"><a href="#sharing-a-collection" aria-hidden="true" class="aal_anchor" id="sharing-a-collection"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Sharing a collection</h2>



<p>A collection created as Shared for a graph/variant is automatically visible to every member of the Studio organization who has access to that graph/variant. Shared collections are editable by any graph or org admin. Optionally, editing settings can also be given to other roles in the org.&nbsp;</p>



<p>⚠️ <strong>Note:</strong> If you are an enterprise user, you can configure granular <a href="https://www.apollographql.com/docs/studio/org/members/">role</a> level permissions, otherwise you can choose whether you want to grant edit permissions to all org users.</p>



<figure class="wp-block-image size-large is-resized"><img loading="lazy" decoding="async" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image4-962x1024.png" alt="" class="wp-image-12699" width="481" height="512" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/image4-962x1024.png 962w, https://wp.apollographql.com/wp-content/uploads/2022/03/image4-282x300.png 282w, https://wp.apollographql.com/wp-content/uploads/2022/03/image4-768x818.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/image4.png 1170w" sizes="auto, (max-width: 481px) 100vw, 481px" /></figure>



<p>But that’s not it! Here are a few ways to make it even easier for your team to find shared operations:</p>



<h3 class="wp-block-heading"><a href="#1-share-a-link" aria-hidden="true" class="aal_anchor" id="1-share-a-link"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>1. Share a link</strong></h3>



<p>You can also give team members a link directly to a particular shared collection or operation. To do so, click the <code>•••</code> button next to any shared collection or operation in the list and select the Copy Link option.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="653" src="https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-1024x653.png" alt="" class="wp-image-12713" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-1024x653.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-300x191.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-768x490.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-1536x979.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1-1200x765.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/Frame-273-1.png 1600w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#2-embed-in-your-graphs-readme" aria-hidden="true" class="aal_anchor" id="2-embed-in-your-graphs-readme"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>2. Embed in your graph’s README</strong></h3>



<p>Have you added a README for your graph yet? If not, no better time like the present! We added the <a href="https://www.apollographql.com/blog/announcement/platform/create-a-readme-to-onboard-developers-to-the-graph/">README page</a> last year to make it easy for graph producers to onboard new developers on their graphs.&nbsp;</p>



<p>Now you can embed saved operations and collections directly into your README:</p>



<ol class="wp-block-list"><li>Click on the edit icon on the README.&nbsp;</li><li>Using the graph shortcodes, select a saved operation or a collection to embed.&nbsp;</li><li>Check out the preview to make sure everything looks good, and then click Update.</li><li>Tada! 🎉 With a few clicks you’ve added an example set of operations to the README.&nbsp;</li></ol>



<p>Now any developer looking to explore the graph can get started right away!</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1432" height="790" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image9.gif" alt="" class="wp-image-12684"/></figure>



<h3 class="wp-block-heading"><a href="#3-create-a-collection-for-a-public-graph" aria-hidden="true" class="aal_anchor" id="3-create-a-collection-for-a-public-graph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>3. Create a collection for a public graph</strong></h3>



<p>If you have a <a href="https://www.apollographql.com/blog/announcement/tooling/make-your-graphql-schema-publicly-visible-without-introspection/">public graph</a>, you can publish a collection of example operations to help developers accessing the public graph onboard quickly. Any developer accessing the public graph can view and execute operations in a public collection, without having to login!&nbsp;</p>



<p>⚠️ <strong>Note:</strong> Unauthenticated users do not have edit access for collections</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="326" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image6-1024x326.png" alt="" class="wp-image-12701" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/image6-1024x326.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6-300x96.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6-768x245.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6-1536x489.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6-1200x382.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6-1980x631.png 1980w, https://wp.apollographql.com/wp-content/uploads/2022/03/image6.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#collections-in-sandbox" aria-hidden="true" class="aal_anchor" id="collections-in-sandbox"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Collections in Sandbox</h3>



<p>Now you might be thinking, “this is great! But I use Sandbox for my local development. Can I save my operations in collections in Sandbox too?” <strong>Yes you can!</strong></p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1999" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image7.png" alt="" class="wp-image-12704" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/image7.png 1999w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-300x154.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-1024x525.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-768x393.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-1536x787.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-1200x615.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/image7-1980x1014.png 1980w" sizes="auto, (max-width: 1999px) 100vw, 1999px" /></figure>



<p>In fact, not only can you save operations in collections across all of your Sandbox endpoints, you can also access collections for any registered graph that you have access to! That means that when you’re using Sandbox to build or make changes to a registered graph in Apollo Studio, you can test out operations in collections for the registered graph and edit them directly as you are making your schema changes!</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="816" src="https://wp.apollographql.com/wp-content/uploads/2022/03/image10-1024x816.png" alt="" class="wp-image-12708" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/image10-1024x816.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/image10-300x239.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/image10-768x612.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/image10-1200x956.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/image10.png 1230w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#and-a-few-more-things" aria-hidden="true" class="aal_anchor" id="and-a-few-more-things"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>And a few more things…</h2>



<p>You thought that was it? Not quite.&nbsp;</p>



<p><strong>After you have created a collection you can:</strong></p>



<ul class="wp-block-list"><li>Edit its configuration.&nbsp;</li><li>Duplicate the collection between graphs, including between sandbox and registered graphs.<ul><li>You can also choose to make the copy public or shared.</li><li>Duplicating a collection does not keep the copy in-sync with the original.</li></ul></li><li>Mark it as favorite, to keep it at the top of the list. ⭐</li></ul>



<p><strong>After you have created an operation you can:</strong></p>



<ul class="wp-block-list"><li>Rename the operation.</li><li>Save a copy of the operation.</li><li>Drag and drop the operation between collections!</li></ul>



<h2 class="wp-block-heading"><a href="#so-what-are-you-waiting-for-save-and-share-your-operations-today" aria-hidden="true" class="aal_anchor" id="so-what-are-you-waiting-for-save-and-share-your-operations-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>So what are you waiting for? Save and share your operations today!</h2>



<p>Head over to Apollo Studio or Apollo Sandbox, and save, organize and share your frequently used operations today! And as always, we love hearing from you, so if you have any feedback, please fill out this <a href="https://forms.gle/CbY8mEp5vK7hgYgA9">feedback</a> form or drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>



<p>⚠️ <strong>Note:</strong> If you do not see Operation Collections in your Explorer, make sure you are on the latest version of the UI. Click on the bell icon at the top right corner of Studio or Sandbox and if you see <em>“Update available, click to relaunch”</em> at the bottom left of the modal then click that to get the latest version.</p>


Save and share your GraphQL operations in Apollo Explorer!


<p><em>🚀 🎉  Heads up &#8211; Federation 2 and Gateway 2.x are now GA! Check out the <a href="https://www.apollographql.com/blog/apollo-federation-2-is-now-generally-available/" data-type="URL" data-id="https://www.apollographql.com/blog/apollo-federation-2-is-now-generally-available/">GA announcement blog</a> or head over to the <a href="https://www.apollographql.com/docs/federation/" data-type="URL" data-id="https://www.apollographql.com/docs/federation/">Federation docs</a> to get started.</em></p>



<hr class="wp-block-separator"/>



<p>Four months ago we announced Apollo Federation 2 &#8211; the next generation of Federation with <a href="https://www.apollographql.com/blog/announcement/backend/announcing-federation-2/">new features</a> designed to improve the graph developer experience and make it easy for anyone to build, manage, and scale a unified graph. </p>



<p>Since then, we’ve been collecting feedback from members of the community and our customers that have tried out the alpha release and have been iterating on the Federation 2 spec to make it viable for the larger GraphQL ecosystem.&nbsp;</p>



<p>With the improvements we’ve made in recent months, we’re excited to move <a href="https://www.apollographql.com/docs/federation/v2/">Federation 2</a> along with <a href="https://www.apollographql.com/docs/federation/v2/gateway/">Apollo Gateway 2.0</a> out of alpha into public preview!</p>



<h2 class="wp-block-heading"><a href="#what-you-need-to-know-about-the-preview" aria-hidden="true" class="aal_anchor" id="what-you-need-to-know-about-the-preview"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What you need to know about the preview</h2>



<p>With Federation 2 and Gateway 2.0 now in preview, here are some highlights and improvements to be aware of:</p>



<ul class="wp-block-list"><li>There are <strong>no breaking changes</strong> between Federation 2 alpha and preview.</li><li>Apollo Gateway 0.X does not support Federation 2. If you would like to use Apollo Gateway with Federation 2, you must use Gateway 2.0 or higher.</li><li>Graphs in Apollo Studio with Federation 2 composition enabled will automatically be updated from <code>alpha</code> to <code>preview</code>.</li><li>If you have Federation 2 composition enabled, Federation 1 subgraphs will automatically be converted to Federation 2 during composition. You can continue to use your Federation 1 subgraphs as long as you like.</li><li><code>@link</code> and <code>@shareable</code> are now supported in the Fed 2 subgraph syntax.</li><li><code>subgraph-js</code> subgraph library now supports Fed 2 subgraph syntax.</li></ul>



<h2 class="wp-block-heading"><a href="#getting-started-with-federation-2-gateway-2-0" aria-hidden="true" class="aal_anchor" id="getting-started-with-federation-2-gateway-2-0"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started with Federation 2 &amp; Gateway 2.0</h2>



<p>Ready to start using Federation 2? <strong>Check out our </strong><a href="https://www.apollographql.com/docs/federation/v2/federation-2/moving-to-federation-2"><strong>docs on moving to Federation 2</strong></a><strong>.</strong> Here’s a quick overview of the steps you’ll need to take:</p>



<h3 class="wp-block-heading"><a href="#1-upgrade-apollo-gateway" aria-hidden="true" class="aal_anchor" id="1-upgrade-apollo-gateway"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>1. Upgrade <code>@apollo/gateway</code></h3>



<p>To use Federation 2, you must be using Gateway 2.0 or higher (or <a href="https://www.apollographql.com/blog/announcement/backend/apollo-router-our-graphql-federation-runtime-in-rust/">Apollo Router</a>). Upgrading from Gateway 0.X to Gateway 2.0 is as easy as bumping the version in your <code>package.json</code>.</p>



<p>Gateway 2.0 is still compatible with Federation 1, so you can upgrade without breaking your existing graph.</p>



<h3 class="wp-block-heading"><a href="#2-turn-on-federation-2-composition" aria-hidden="true" class="aal_anchor" id="2-turn-on-federation-2-composition"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2. Turn on Federation 2 composition</h3>



<p>Once your runtime is compatible with Federation 2, you’ll need to take a moment to turn on Fed 2 composition for Managed Federation or for the Rover CLI, depending on how you compose your federated graph.</p>



<p>Federation 2 composition is backward compatible with Federation 1 subgraphs (🎉), so turning it on won’t break your existing graph.</p>



<p><strong>Managed Federation</strong></p>



<p>If you use managed Federation, you can turn on Fed 2 composition for specific variants. Navigate to the “Manage Variants” section of your graph’s settings page and click the meatball menu next to a variant.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh5.googleusercontent.com/qfapzHPkVsn7KDhBrs-x-CRWPT1yLOiu5BzS3krUHAXpC489sApWL5jqf4F64vbc79HMR1AQPnrpECb3-63vTRgt_baqGdHr-1yy6zRbl6majExI73FaiiBif4o63_wZWOwj4vsZ" alt=""/></figure>



<p>Click “Edit Build Configuration” and select Federation 2 under the “Federation Version” dropdown.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh4.googleusercontent.com/cTbU2CnbeZa_gWjO7QkZ4Phh3o97axRZCBAcazYIaidBBkExnwACRqTGtSgXiWYwg829jE4UM-lQiVk0NOnnk_QYwswQJq_Wh5b5QUEXycbCE9ISYs8Scfp4pAdHd4cPbMe7NZ-Z" alt=""/></figure>



<p><strong>Rover CLI</strong></p>



<p>If you use the Rover CLI for Federation composition, you’ll need to install the latest version of Rover and install the Federation 2 plugin. You can find detailed instructions on how to do so <a href="https://www.apollographql.com/docs/federation/v2/federation-2/moving-to-federation-2/#using-the-rover-cli">here</a>.</p>



<h3 class="wp-block-heading"><a href="#3-modify-your-subgraphs-at-your-own-pace" aria-hidden="true" class="aal_anchor" id="3-modify-your-subgraphs-at-your-own-pace"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>3. Modify your subgraphs at your own pace</h3>



<p>At this point, your graph is already running on Federation 2 &#8211; congrats! Now, to make the most out of Fed 2, you’ll want to modify your subgraphs to take advantage of its more flexible composition model.&nbsp;</p>



<p>Since Fed 2 composition is backwards compatible with Fed 1 subgraphs, service teams can modify their subgraphs at their own pace without breaking composition! You can learn about all of the improvements available in the Fed 2 subgraph syntax in the <a href="https://www.apollographql.com/docs/federation/v2/federation-2/new-in-federation-2/#more-flexible-composition">documentation</a>.</p>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next?</h2>



<p>We can’t wait for you to experience the next generation of Apollo Federation and Gateway 2.0! 🚀&nbsp;If you’re currently using Federation 1, check our guide on <a href="https://www.apollographql.com/docs/federation/v2/federation-2/moving-to-federation-2/">moving to Federation 2</a>, or if you’re new to Federation, our <a href="https://www.apollographql.com/docs/federation/v2/quickstart/setup/">quickstart guide</a> is a great place to get started. And don’t forget, we would love to know about your experience with Federation 2, so be sure to leave us your thoughts on <a href="https://community.apollographql.com">community.apollographql.com</a>.</p>


Apollo Federation 2 and Gateway 2.0 are now available in preview


<p>Today we’re excited to show off some recent upgrades to Operation Insights in Apollo Studio. This update features three significant enhancements which make it easier to understand the usage and data flow of operations in your graph.</p>



<h2 class="wp-block-heading"><a href="#1-what-does-an-operation-look-like" aria-hidden="true" class="aal_anchor" id="1-what-does-an-operation-look-like"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>1. What does an operation look like?</h2>



<p>First, we brought the operation signature front and center so that you can quickly understand the shape of fields being requested by the operation.  The signature now appears as a side-panel that you can resize instead of hidden behind another tab.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="621" src="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-1024x621.png" alt="" class="wp-image-12391" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-1024x621.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-300x182.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-768x465.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-1536x931.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1-1200x727.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-1.png 1650w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>Easier to find operation signatures.</figcaption></figure>



<h2 class="wp-block-heading"><a href="#2-which-subgraphs-are-used-by-an-operation" aria-hidden="true" class="aal_anchor" id="2-which-subgraphs-are-used-by-an-operation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>2. Which subgraphs are used by an operation?</h2>



<p>In the same panel, we added the ability to view the federation query plan for an operation.  The query plan lets you see how Apollo Gateway or Router is working under the hood, describing how data from your subgraphs is woven together to build a full query response.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1024" height="768" src="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-2.png" alt="" class="wp-image-12397" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-2.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-2-300x225.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-2-768x576.png 768w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>See query plans and subgraph dependencies for federated operations.</figcaption></figure>



<p>Similar to features found in Apollo Explorer, you can view the query plan as either a text document or visualized as a tree of subgraphs. (<span class="has-inline-color has-accent-color">Only available to federated graphs. Learn more about <a href="https://www.apollographql.com/docs/federation/query-plans/">Apollo Federation Query Plans</a></span>).</p>



<h2 class="wp-block-heading"><a href="#3-which-clients-are-using-this-operation" aria-hidden="true" class="aal_anchor" id="3-which-clients-are-using-this-operation"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>3. Which clients are using this operation?</h2>



<p>Last but not least, we introduced a way to understand which clients are using an operation in a new Client Usage display. The most active clients are sorted to the top of the list based on the number of requests reported to Apollo Studio via <a href="https://www.apollographql.com/docs/studio/metrics/usage-reporting/">usage reporting</a>.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="621" src="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-1024x621.png" alt="" class="wp-image-12400" srcset="https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-1024x621.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-300x182.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-768x465.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-1536x931.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3-1200x727.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/03/operation-blog-3.png 1650w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>See client usage breakdowns for operations.</figcaption></figure>



<h3 class="wp-block-heading"><a href="#now-available-in-apollo-studio" aria-hidden="true" class="aal_anchor" id="now-available-in-apollo-studio"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Now Available in Apollo Studio!</h3>



<p><span class="has-inline-color has-primary-color">As a reminder, you can find all of these features by visiting the Operations tab in Apollo Studio and then choosing a single operation from the operations drop-down. Note that you can also get to insights for individual operations from field usage details, failed operation checks, client breakdowns, and Slack daily reports.</span></p>



<h2 class="wp-block-heading"><a href="#explore-operation-insights-today" aria-hidden="true" class="aal_anchor" id="explore-operation-insights-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Explore Operation Insights today</h2>



<p>When utilizing <a href="https://www.apollographql.com/docs/studio/metrics/usage-reporting/">Apollo usage reporting</a> for your graph, you’ll have access to these insights and more.</p>



<p><a href="https://studio.apollographql.com/">Visit Apollo Studio</a> to start using these tools and more today.  And as always, we love hearing from you, so if you have any feedback, please fill out this <a href="https://forms.gle/Ep9cRWq9j3hwdmTL6">feedback form </a>or drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


New Operation Insights with Client Usage and Federation Query Plans


<p>When you’re a developer working on a federated graph, you likely work on a single subgraph locally before publishing it to Apollo Studio as part of the supergraph. We created <a href="https://www.apollographql.com/blog/announcement/platform/apollo-sandbox-an-open-graphql-ide-for-local-development/">Apollo Sandbox</a> to give developers a great tool for working on locally-running graphs, but wouldn’t it be great if could get the same functionality when working with subgraphs? And even better &#8211; what if you could use Sandbox to run checks to check that your local changes won’t break composition or operations against the federated graph? Well, now you can!</p>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="Introducing Apollo Sandbox" width="580" height="326" src="https://www.youtube.com/embed/0jzqqHZU00Q?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<h2 class="wp-block-heading"><a href="#load-a-subgraph-in-apollo-sandbox" aria-hidden="true" class="aal_anchor" id="load-a-subgraph-in-apollo-sandbox"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Load a subgraph in Apollo Sandbox</h2>



<p>When working off a subgraph, head over to <a href="http://studio.apollographql.com/sandbox/">Apollo Sandbox</a> and connect to your subgraph localhost via the Sandbox endpoint field (or you can connect to a remote endpoint if you like). You will notice that a <code>SUBGRAPH</code> badge appears next to the endpoint. Your subgraph schema is loaded and ready to be queried!&nbsp;</p>



<p>Explore your subgraph schema on the Schema page and run operations in Explorer. As you make changes to your subgraph schema, changes are automatically updated in Sandbox without any manual refresh.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1434" height="793" src="https://wp.apollographql.com/wp-content/uploads/2022/02/subgraph-sandbox-1.gif" alt="" class="wp-image-12331"/></figure>



<h2 class="wp-block-heading"><a href="#compare-your-subgraph-schema-to-a-registered-subgraph-in-studio" aria-hidden="true" class="aal_anchor" id="compare-your-subgraph-schema-to-a-registered-subgraph-in-studio"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Compare your subgraph schema to a registered subgraph in Studio</h2>



<p>Navigate to the Diffs tab and sign into Studio to select a registered subgraph to diff your local schema against. Without going anywhere, you can see how your changes compare to the existing subgraph. You can also see a summary of how many types and fields have been added or removed.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1433" height="788" src="https://wp.apollographql.com/wp-content/uploads/2022/02/subgraph-sandbox-2.gif" alt="" class="wp-image-12333"/></figure>



<h2 class="wp-block-heading"><a href="#check-supergraph-composition-and-prevent-breaking-changes" aria-hidden="true" class="aal_anchor" id="check-supergraph-composition-and-prevent-breaking-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Check supergraph composition and prevent breaking changes</h2>



<p>You can ensure that your changes won’t break the supergraph schema composition and or affect any operations to the federated graph by clicking on the “Run a check” button in the loaded diff view or by heading over to the checks tab. If all of your checks pass, you can publish your changes to the registered schema in Apollo Studio with complete confidence!</p>



<p>If you want to see even more details about checks, you can navigate to the main checks page on Studio. You can always move back and forth between Sandbox and full Studio experience using the box icon on the top right corner in the navigation bar.</p>



<p><strong>⚠️</strong> <strong>Note:</strong> For checks to work, you’ll need to have a Studio account with access to Checks, which is available on Team and Enterprise plans only.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1433" height="789" src="https://wp.apollographql.com/wp-content/uploads/2022/02/subgraph-sandbox-3.gif" alt="" class="wp-image-12335"/></figure>



<h2 class="wp-block-heading"><a href="#start-working-on-your-subgraphs-in-sandbox-today" aria-hidden="true" class="aal_anchor" id="start-working-on-your-subgraphs-in-sandbox-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Start working on your subgraphs in Sandbox today!</h2>



<p><a href="https://studio.apollographql.com/sandbox/">Head over to Apollo Sandbox</a>, point it to a subgraph and try out these new features! And as always, we love hearing from you, so if you have any feedback, please fill out this <a href="https://forms.gle/4G2cEumrh85jgDF1A">feedback form</a> or drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


Introducing subgraph support in Apollo Sandbox


<p>Since releasing <a href="https://www.apollographql.com/blog/announcement/platform/introducing-contracts-serve-many-audiences-with-a-unified-graph/">contracts</a> as a way to serve many audiences with a unified graph, we’ve received great feedback from developers adopting contracts and championing the graph. However, one question we frequently hear is: “how can I reason about contracts with respect to my publishing pipeline?”</p>



<p>As of today, we are thrilled to introduce Contract Launches in Apollo Studio to answer this very question. With Contract Launches, you can use the Launches page in Studio that provides better visibility into the lifecycle of your contract schemas and helps you understand which contracts launched from a given source variant.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="4857" height="2710" src="https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall.png" alt="" class="wp-image-12141" srcset="https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall.png 4857w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-300x167.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-1024x571.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-768x429.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-1536x857.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-2048x1143.png 2048w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-1200x670.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Overall-1980x1105.png 1980w" sizes="auto, (max-width: 4857px) 100vw, 4857px" /></figure>



<h2 class="wp-block-heading"><a href="#lifecycle-of-a-contract-launch" aria-hidden="true" class="aal_anchor" id="lifecycle-of-a-contract-launch"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Lifecycle of a Contract Launch</h2>



<p>Every contract is built from an existing source variant. Publishing updates to your source variant triggers downstream launches for any contract built from that source.</p>



<p>Let&#8217;s look in more detail what this looks like:</p>



<ol class="wp-block-list"><li>You publish an update to your source variant</li><li>A launch initiates for the source variant</li><li>If the launch was successful a core schema is the output artifact</li><li>The core schema is then approved and made available to gateways</li><li>A launch for each contract is initiated<ol><li>The core schema is used as the build input to contract launches</li></ol></li><li>The schema is then filtered into a contract schema</li><li>If the launch was successful a contract schema is the output artifact</li><li>The contract schema is then approved and made available to gateways</li></ol>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1020" height="892" src="https://wp.apollographql.com/wp-content/uploads/2022/02/contract-launches.gif" alt="" class="wp-image-12143"/><figcaption>The lifecycle of a contract launch</figcaption></figure>



<h2 class="wp-block-heading"><a href="#launch-status" aria-hidden="true" class="aal_anchor" id="launch-status"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Launch status</h2>



<p>For any launch that triggers a contract launch, you can see a summary of how many downstream launches succeeded or failed:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="229" src="https://wp.apollographql.com/wp-content/uploads/2022/02/image-5-1024x229.png" alt="" class="wp-image-12145" srcset="https://wp.apollographql.com/wp-content/uploads/2022/02/image-5-1024x229.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-5-300x67.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-5-768x172.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-5.png 1179w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>You can also take a look at the Launch Sequence to see the status of each contract launch individually. To debug a failed launch, you can navigate to the Launches page for a contract by clicking the desired contract launch item.</p>



<p>A contract launch that completes successfully is made available to running gateways via Uplink.</p>



<p>⚠️ <strong>Note:</strong> Checks for contracts are not currently supported but are in active research and development.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="872" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2022/02/image-6-872x1024.png" alt="" class="wp-image-12147" srcset="https://wp.apollographql.com/wp-content/uploads/2022/02/image-6-872x1024.png 872w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-6-256x300.png 256w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-6-768x901.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/02/image-6.png 978w" sizes="auto, (max-width: 872px) 100vw, 872px" /></figure>



<h2 class="wp-block-heading"><a href="#reviewing-changes" aria-hidden="true" class="aal_anchor" id="reviewing-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Reviewing changes</h2>



<p>Any update to your graph will also update your contracts. To help you keep track of these changes, there’s a convenient link to the contracts changelog. The changelog page shows you any types or fields from your contract schema that have been added, removed, or modified.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="518" src="https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-1024x518.png" alt="" class="wp-image-12149" srcset="https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-1024x518.png 1024w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-300x152.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-768x389.png 768w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-1536x777.png 1536w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-2048x1036.png 2048w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-1200x607.png 1200w, https://wp.apollographql.com/wp-content/uploads/2022/02/Contract-Launches-Changelog-Entries-1980x1002.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next</h2>



<p>Apollo Contracts is currently in public preview on Apollo’s Enterprise plan. Feedback from our community and customers is crucial to the success of Apollo, and the feedback we’ve received from pilot users so far has been instrumental in ensuring that contracts can serve many use cases while still giving teams full visibility and control over changes.</p>



<p>If you’re interested in learning more about Contracts, visit the <a href="https://www.apollographql.com/docs/studio/contracts/">documentation</a>. We’re excited to see what you’ll build!</p>


Introducing Contract Launches: see the lifecycle of contract schemas in Apollo Studio


<p>We recently introduced Preflight Scripts to Explorer! With preflight scripts you can automatically run any custom authentication before your GraphQL operation is executed. Preflight scripts are especially useful for managing authentication flows like OAuth by refreshing an access token, for example. Let’s take a look.</p>



<h2 class="wp-block-heading"><a href="#setting-up-your-preflight-script" aria-hidden="true" class="aal_anchor" id="setting-up-your-preflight-script"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Setting up your preflight script</h2>



<p>For a graph and variant you want to create a script for, scroll down to find the “Preflight script” section in Apollo Studio Explorer Settings. You will only be able to set up a script if you have the role of Contributor or Admin for this particular graph.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1002" height="276" src="https://wp.apollographql.com/wp-content/uploads/2022/01/image2.png" alt="Add a preflight script" class="wp-image-11856" srcset="https://wp.apollographql.com/wp-content/uploads/2022/01/image2.png 1002w, https://wp.apollographql.com/wp-content/uploads/2022/01/image2-300x83.png 300w, https://wp.apollographql.com/wp-content/uploads/2022/01/image2-768x212.png 768w" sizes="auto, (max-width: 1002px) 100vw, 1002px" /></figure>



<p>Clicking on the “Add script” button will open up the preflight script editor panel. In the editor you’ll find some code snippets to help you get started. You can simply click on the plus icon for adding snippets and start writing your preflight script.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1184" height="623" src="https://wp.apollographql.com/wp-content/uploads/2022/01/image1.gif" alt="Edit your preflight script" class="wp-image-11858"/></figure>



<h2 class="wp-block-heading"><a href="#test-and-publish-your-script" aria-hidden="true" class="aal_anchor" id="test-and-publish-your-script"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Test and publish your script</h2>



<p>As you develop your script in the script editor panel, you can click “Test script” to test its execution. Console messages are printed in the Console output panel. Setting any <a href="https://www.apollographql.com/docs/studio/explorer/connecting-authenticating/#environment-variables">environment variables</a> in the above dialog will also be reflected in Explorer. Once you are ready, click Save and the script will be available to all team members executing operations against this graph variant in Explorer.</p>



<p>Below is an example of a preflight script that refreshes access tokens after a specific period of time. </p>



<p>⚠️ <strong>Note:</strong> This script exactly as is will not work since it is using a dummy OAuth server.</p>



<pre class="wp-block-code"><code>if (new Date().getTime() &gt; explorer.environment.get(&quot;token_expires_at&quot;)) {
  const { access_token, expires_at, refresh_token } = await explorer.fetch(
      &quot;https://example.com/token&quot;,
      {
        method: &quot;POST&quot;,
        header: {
            &quot;Content-Type&quot;: &quot;application/json&quot;,
            //...
        },
        body: JSON.stringify({
            refreshToken: explorer.environment.get(&quot;refresh_token&quot;),
        }),
      },
    )
    .then((response) =&gt; response.json());

  explorer.environment.set(&quot;token&quot;, access_token);
  explorer.environment.set(&quot;refresh_token&quot;, refresh_token);
  explorer.environment.set(&quot;token_expires_at&quot;, expires_at);
}</code></pre>



<p>Additionally, we will need to perform the following steps:</p>



<ol class="wp-block-list"><li>Authenticate server outside of Apollo Studio to retrieve token, refresh_token and token_expires_at.</li><li>Add these values as environment variables in Explorer.</li><li>Now, with the preflight script running, when the token expires the script will automatically refresh the token and there is no need to manually authenticate again.</li></ol>



<h2 class="wp-block-heading"><a href="#write-your-preflight-script-today" aria-hidden="true" class="aal_anchor" id="write-your-preflight-script-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Write your preflight script today!</h2>



<p>Head over to Apollo Studio Explorer and write your preflight script to make authentication before operations are executed easy for your consumers! Learn more <a href="https://www.apollographql.com/docs/studio/explorer/connecting-authenticating/#preflight-scripts">here</a> and as always, we love hearing from you, so if you have any feedback, please drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


Automatically Authenticate with Preflight Scripts in Apollo Studio Explorer

Introducing Apollo Kotlin


<p>When you’re making changes to your GraphQL schema, you probably make those changes locally before you publish them to a graph registry like Apollo Studio. </p>



<p>We created <a href="https://www.apollographql.com/blog/announcement/platform/apollo-sandbox-an-open-graphql-ide-for-local-development/">Apollo Sandbox</a> so that you can use the best GraphQL IDE when working locally, but wouldn’t it be great if you could easily see the diff between your local schema and the existing schema in Studio? </p>



<p>And even better &#8211; what if you could run checks to see if your local changes could break operations against the production graph? Well, now you can do both right from Apollo Sandbox! Let’s take a look at how:</p>



<h2 class="wp-block-heading"><a href="#validate-your-schema-changes-before-publishing-them-to-studio" aria-hidden="true" class="aal_anchor" id="validate-your-schema-changes-before-publishing-them-to-studio"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Validate your schema changes before publishing them to Studio!</h2>



<p>Want to feel confident about your schema changes before publishing them to Studio? Simply head over to <a href="http://studio.apollographql.com/sandbox/">Apollo Sandbox</a> and connect to your localhost via the Sandbox endpoint field (or you can connect to a remote endpoint if you like).</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1433" height="829" src="https://wp.apollographql.com/wp-content/uploads/2021/12/image1.gif" alt="" class="wp-image-11504"/></figure>



<h3 class="wp-block-heading"><a href="#compare-your-schema-to-a-registered-graph-in-studio" aria-hidden="true" class="aal_anchor" id="compare-your-schema-to-a-registered-graph-in-studio"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Compare your schema to a registered graph in Studio</h3>



<p>Go to the Diffs tab and sign into Studio to select a registered graph to diff your local schema against and explore your diff! See a summary of how many types and fields have been added or removed and select to view it as a line wrap if needed.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1434" height="829" src="https://wp.apollographql.com/wp-content/uploads/2021/12/image4.gif" alt="" class="wp-image-11510"/></figure>



<h3 class="wp-block-heading"><a href="#make-sure-there-are-no-breaking-changes" aria-hidden="true" class="aal_anchor" id="make-sure-there-are-no-breaking-changes"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Make sure there are no breaking changes</h3>



<p>Try running an operation check on your local schema by either:</p>



<ol class="wp-block-list"><li>Using the Run check button from the loaded diff view or</li><li>Going to the Checks tab and selecting a registered graph to check against</li></ol>



<p>Once you see a summary of results, you can also view more details by navigating to the main checks page on Studio.</p>



<p>Remember, you can always move back and forth between Sandbox and the full Studio experience by clicking the box icon in the top righthand corner in the navigation bar.</p>



<p>⚠️ <strong>Note:</strong> For checks to work, you’ll need to have a Studio account with a registered graph that is receiving traffic and access to Checks, which is available on Team and Enterprise plans only.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1430" height="824" src="https://wp.apollographql.com/wp-content/uploads/2021/12/image3.gif" alt="" class="wp-image-11507"/></figure>



<h2 class="wp-block-heading"><a href="#try-these-new-improvements-out-today" aria-hidden="true" class="aal_anchor" id="try-these-new-improvements-out-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Try these new improvements out today!</h2>



<p><a href="https://studio.apollographql.com/sandbox/">Head over to Apollo Sandbox</a> and compare your local changes with registered graphs and ensure there are no breaking changes! And as always, we love hearing from you, so if you have any feedback, please fill out this <a href="https://forms.gle/4G2cEumrh85jgDF1A">feedback form</a> or drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


How to run diffs and operation checks in Apollo Sandbox


<p>The Apollo Studio Explorer is an incredible GraphQL IDE that makes it quick and easy to browse schemas and run operations against them. But wouldn’t it be awesome if you could embed the Explorer into external pages so that you could use it inside your product documentation, internal wiki, or blog post? Now you can! Let’s take a look at how.&nbsp;</p>



<h2 class="wp-block-heading"><a href="#make-the-graph-you-want-to-embed-publicly-visible" aria-hidden="true" class="aal_anchor" id="make-the-graph-you-want-to-embed-publicly-visible"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Make the graph you want to embed publicly visible</h2>



<p>Making your graph publicly visible is as easy as flipping a switch. Simply navigate to the Settings page for your graph in Apollo Studio and under the Access tab, set a variant of your choosing as “public.” That particular variant of your graph is now publicly visible in Apollo Studio! When a variant of a graph is set to public, anyone can navigate to the public Studio URL for that variant and access the README, schema reference, changelog, and Explorer (this is equivalent to <a href="https://www.apollographql.com/blog/announcement/platform/sharing-your-graph-just-got-a-whole-lot-easier-announcing-unlimited-consumer-seats/">Consumer-level access</a>).&nbsp;</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh5.googleusercontent.com/pW9HiTs_J8dA1QhnrQryA59ueVwl5MQ7mEwMuKMK_SyF9zqgOVyolSFsP2kDwkoy-Rj33p0SZ8cal8DiUd1MsbjQyJS_yyE2FZuaXUB228HeB0GhgAJLoEYzBo1AUPLTQhF838ie" alt=""/></figure>



<h2 class="wp-block-heading"><a href="#copy-the-embed-code-snippet" aria-hidden="true" class="aal_anchor" id="copy-the-embed-code-snippet"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Copy the embed code snippet</h2>



<p>Now that your graph is public, head over to Explorer for that graph. If you would like to embed Explorer with a default operation, enter the operation in the editor pane in Explorer before copying the embed snippet (also, maybe test it out first to make sure it works 😄). Then click on the meatball menu right of your operation and click on “Embed this operation.” You can also find the action to embed under the Explorer Settings tab in Explorer.  </p>



<figure class="wp-block-image"><img decoding="async" src="https://lh6.googleusercontent.com/XRgQ7j_JjZL6F4abOOnySqohxEq6w_S0JyR70EB7X6l4TfZHmbEUJ_NeZS5jnHpxfDvN6ASdTyrIHfsuyAgYyNa2mAA1otknS69127ZDJKIoNX2MvPmKwkjw-ZDThM4EFUYW8oJy" alt=""/></figure>



<p>In the embed modal, you can also toggle any configuration options that you would like such as embedded Explorer with dark theme and keeping the docs panel closed by default. Once you have configured it to your liking, copy the code snippet to embed!</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh6.googleusercontent.com/5brrxUjyTiICqeeApWh2uh4FQ_dW_GEZ4Vw-snud_9sJ2-hINyfx6dXUKOEqbysPo1Ey0khiQUUYFxLjLCMk7eIXpBRzDld0sJF9BVbtgzMuQdt65WV7lG6t9tgK4qvWyy4SeoZT" alt=""/></figure>



<h2 class="wp-block-heading"><a href="#paste-the-embed-code-snippet-in-the-parent-page" aria-hidden="true" class="aal_anchor" id="paste-the-embed-code-snippet-in-the-parent-page"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Paste the embed code snippet in the parent page</h2>



<p>Now all you have to do is take the embed code snippet and paste it in the code of any webpage where you would like to embed Explorer like we have done here! Try the embedded Explorer for yourself below.</p>



<div style="width: 100%; height: 500px;" id="embedded-explorer"></div>
<script src="https://embeddable-explorer.cdn.apollographql.com/_latest/embeddable-explorer.umd.production.min.js"></script> 
<script>
  new window.EmbeddedExplorer({
    target: '#embedded-explorer',
    graphRef: 'SpaceX-pxxbxen@current',
    endpointUrl: 'https://api.spacex.land/graphql/',
    persistExplorerState: false,
    initialState: {
      document: `query ExampleQuery {
  company {
    ceo
  }
  roadster {
    apoapsis_au
  }
}`,
      variables: {},
      headers: {},
      displayOptions: {
        showHeadersAndEnvVars: false, 
        docsPanelState: 'closed', 
        theme: 'dark',
      },
    },
  });
</script>



<h2 class="wp-block-heading"><a href="#embed-your-graphs-with-explorer-today" aria-hidden="true" class="aal_anchor" id="embed-your-graphs-with-explorer-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Embed your graphs with Explorer today!</h2>



<p>Excited? We hope so! Sharing graphs with a broader audience on your own documentation portals using Apollo Explorer’s amazing experience could not get any easier. <a href="https://studio.apollographql.com/sandbox/explorer?endpoint=https%3A%2F%2Fapi.spacex.land%2Fgraphql%2F&amp;explorerURLState=N4IgJg9gxgrgtgUwHYBcQC4QEcYIE4CeABADICGMSUAFggM5HAA6SRRANhVbQ862xy40A%2BgQRk8LAUTgBLOnVkQkwpGURSiAXxZaQAGhAA3CbLIAjdvQwgQWoA">Head over to Studio</a> and get wider adoption of your graph today! And as always, we love hearing from you, so if you have any feedback, please drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


Embed Apollo Explorer Anywhere


<p>GraphQL Summit welcomed more than 10,000 developers and engineering leaders virtually on November 10 &amp; 11 for two days of sessions, panels, and workshops. New for the fall Summit, attendees could choose from two session tracks (Build and Scale) on Day 1. The Build Track offered best practices for building, testing, and maintaining GraphQL. The Scale Track presented insights into the key considerations for scaling the graph to improve innovation, velocity, and productivity.</p>



<p>On Day 2, community Graph Champions covered graph strategy, transformation, and stewardship in our roundtables, and hands-on workshops offered practical education and skills-building tailored for various stages of GraphQL maturity.</p>



<h2 class="wp-block-heading"><a href="#product-announcements" aria-hidden="true" class="aal_anchor" id="product-announcements"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Product announcements</h2>



<p>Alongside the many talks, Apollo also announced several new releases and improvements to the Apollo Graph Platform, including:</p>



<h3 class="wp-block-heading"><a href="#federation-2-now-available-in-alpha" aria-hidden="true" class="aal_anchor" id="federation-2-now-available-in-alpha"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Federation 2 &#8211; now available in alpha</strong></h3>



<p><a href="https://www.apollographql.com/blog/announcement/backend/announcing-federation-2/">Apollo Federation 2</a> is the evolution of our source-available GraphQL spec that makes it simple for anyone to build, manage, and scale a unified graph, enabling faster app delivery, increased innovation, and better control over the graph. Learn more about Federation 2 in the “The Future of Apollo Federation” session, available now <a href="https://www.apollographql.com/events/virtual-event/graphql-summit-november-2021/the-future-of-apollo-federation/">on-demand.</a></p>



<h3 class="wp-block-heading"><a href="#apollo-router-now-available-in-alpha" aria-hidden="true" class="aal_anchor" id="apollo-router-now-available-in-alpha"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Apollo Router &#8211; now available in alpha</strong></h3>



<p><a href="https://www.apollographql.com/blog/announcement/backend/apollo-router-our-graphql-federation-runtime-in-rust/">Apollo Router</a> is our next-generation, source-available Federation runtime written in Rust. It’s 10x faster than the Apollo Gateway and 12x more efficient to operate. An efficiency increase of this magnitude delivers material cost savings in cloud resources and a better experience for your users and customers, especially at scale. Learn more about the Apollo Router in the “The Future of Apollo Federation” session, available now <a href="https://www.apollographql.com/events/virtual-event/graphql-summit-november-2021/the-future-of-apollo-federation/">on-demand.</a></p>



<h3 class="wp-block-heading"><a href="#public-graphs-embeddable-explorer-generally-available" aria-hidden="true" class="aal_anchor" id="public-graphs-embeddable-explorer-generally-available"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Public graphs &amp; embeddable Explorer &#8211; generally available</strong></h3>



<p>You can now <a href="https://www.apollographql.com/docs/studio/org/graphs/#making-a-variant-public">make your graphs publicly visible</a> in Studio, allowing developers to access the README, Schema Reference, and Explorer without logging in. We also announced the ability to <a href="https://www.apollographql.com/docs/studio/embed-explorer/#postmessage-setup">embed Explorer</a> into external pages for public graphs. To see these features in action, watch “The Secret to Successful Graph Onboarding” session, available now <a href="https://www.apollographql.com/events/virtual-event/graphql-summit-november-2021/the-secret-to-successful-graph-onboarding/">on-demand</a>. (And check out the embedded Explorer below 👇)</p>



<div style="width: 100%; height: 500px;" id="embedded-explorer"></div>
<script src="https://embeddable-explorer.cdn.apollographql.com/_latest/embeddable-explorer.umd.production.min.js"></script> 
<script>
  new window.EmbeddedExplorer({
    target: '#embedded-explorer',
    graphRef: 'SpaceX-pxxbxen@current',
    endpointUrl: 'https://api.spacex.land/graphql/',
    persistExplorerState: false,
    initialState: {
      document: `query ExampleQuery {
  company {
    ceo
  }
  roadster {
    apoapsis_au
  }
}`,
      variables: {},
      headers: {},
      displayOptions: {
        showHeadersAndEnvVars: true, 
        docsPanelState: 'open', 
        theme: 'dark',
      },
    },
  });
</script>



<h3 class="wp-block-heading"><a href="#contracts-available-in-preview-on-apollo-studio-enterprise" aria-hidden="true" class="aal_anchor" id="contracts-available-in-preview-on-apollo-studio-enterprise"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Contracts &#8211; available in preview on Apollo Studio Enterprise</strong></h3>



<p>Using <a href="https://www.apollographql.com/docs/studio/contracts/">Contracts</a>, graph platform teams can apply filters to the unified graph to create tailored contract graphs specific to a particular audience. Contracts are now available in public preview for Apollo Enterprise customers. Learn more about Contracts in the “How to Serve Many Audiences with One Graph” session, available now <a href="https://www.apollographql.com/events/virtual-event/graphql-summit-november-2021/how-to-serve-many-audiences-with-one-graph/">on-demand</a>.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1000" height="642" src="https://wp.apollographql.com/wp-content/uploads/2021/11/contract-tags.jpeg" alt="" class="wp-image-11212" srcset="https://wp.apollographql.com/wp-content/uploads/2021/11/contract-tags.jpeg 1000w, https://wp.apollographql.com/wp-content/uploads/2021/11/contract-tags-300x193.jpeg 300w, https://wp.apollographql.com/wp-content/uploads/2021/11/contract-tags-768x493.jpeg 768w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></figure>



<p>If you missed out on any of the GraphQL Summit sessions, watch them <a href="https://www.apollographql.com/events/virtual-event/graphql-summit/">on-demand now.</a> Stay tuned to the blog, as we’ll be releasing more posts over the next few weeks recapping GraphQL Summit.</p>


GraphQL Summit Recap: Everything We Launched

Apollo Router: our GraphQL Federation runtime in Rust


<p>At Apollo, we talk a lot about building a unified graph, and for good reason. A unified graph provides incredible benefits &#8211; a single source of truth for all services, faster apps, faster delivery, less maintenance overhead, and more.&nbsp;</p>



<p>But unification introduces new challenges, especially at scale;</p>



<p><em>“How do I support different experiences and levels of access for different personas or types of users like customers, employees, suppliers, and partners?”</em></p>



<p><em>“How do I provide my partners and public API users with a schema scoped for their integration and app development needs?”</em></p>



<p><em>“How do I provide client-specific BFFs and experience-driven schemas alongside a canonical domain-driven schema?”</em></p>



<p><em>“How do I restrict access to experimental or non-stable parts of the schema, but still allow access for testing and early adopters?”</em></p>



<p>These common challenges boil down to one question: <strong>“how do I serve multiple different audiences with a single unified graph?”</strong> Today, we’re excited to announce Contracts, a new feature in preview on Apollo’s Enterprise plan that allows you to create tailored graphs for different audiences by applying filters to a single unified graph.</p>



<h2 class="wp-block-heading"><a href="#modularity-when-consuming-the-graph" aria-hidden="true" class="aal_anchor" id="modularity-when-consuming-the-graph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Modularity when consuming the graph</h2>



<p>We often discuss consolidating APIs, but there are benefits to separation as well. Separate APIs can be managed by independent backend teams with less coordination. They can also be tailored to whoever will be consuming them and individually governed for granular access control.&nbsp;</p>



<p>We want to unify our services into a single graph to reduce manual API maintenance and improve delivery velocity, but we don’t want to lose the benefits of separate APIs. Apollo Federation accomplishes this for the backend by modularizing the graph into subgraphs that can be modified asynchronously, allowing service teams to build a unified graph while still operating independently. Contracts deliver the same modularity for the frontend.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh4.googleusercontent.com/C7ycR2cyk5VACxMpjCNerLEc4vf7VgJlPe8HArwSnkw8RTSMxaZkfjKdvoYHTpOCND1DUuDOnzsCArDtat1hoaD7TCOxmauJG5aTiAGLFH0LEWKG3w8lAl63TdeVwO8Fceh46D86" alt=""/></figure>



<p>With Contracts, graph platform teams can create tailored experiences for multiple audiences by creating contract graphs that contain a filtered subset of the unified graph. Each contract can align with a particular developer audience to streamline the graph experience, rather than providing the entire graph to every internal and external developer. </p>



<p>Using contracts you can create separate graphs for partner developers, specific client applications, public APIs, experimental features, and more without losing any of the benefits of the unified graph.</p>



<h2 class="wp-block-heading"><a href="#creating-contracts" aria-hidden="true" class="aal_anchor" id="creating-contracts"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Creating contracts</h2>



<p>Contracts work with a simple but powerful new <code>@tag</code> directive which you can apply to fields, interfaces, objects, and unions in your subgraph schemas. You then create filter rules which include or exclude certain tags. Anything not included in the contract will be removed from the client-facing schema for that contract but will still be included in the internal supergraph schema to be used for Federation and routing.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh3.googleusercontent.com/V-ik_hqpTy-DVEAc5xkokOWohdmOjPJxGeMdw9LJkIv2oUSd6wqNz3eVk3q382a0TZI9CcsCAfaAvMwMsOBEc05fIicHxTBVJd6jH5i7byd6lUR0cOq2jcJpK8NpXJkIPvS7zO-e" alt=""/></figure>



<h2 class="wp-block-heading"><a href="#documentation-contracts-vs-deployed-contracts" aria-hidden="true" class="aal_anchor" id="documentation-contracts-vs-deployed-contracts"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Documentation contracts vs deployed contracts</h2>



<p>There are two ways you can use a contract schema &#8211; as documentation or as a running endpoint.&nbsp;</p>



<h3 class="wp-block-heading"><a href="#documentation-contracts" aria-hidden="true" class="aal_anchor" id="documentation-contracts"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Documentation contracts</h3>



<p>You might use a contract schema just for documentation if you simply want to streamline the graph experience for internal developers by only showing them the fields they need from the graph. For example, you could create a mobile contract schema that only includes parts of the graph that are relevant to mobile developers and removes unnecessary parts that may only be useful for web or IoT applications.&nbsp;</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh3.googleusercontent.com/y_CGjvKlyyQzkjf26IxM_asEz_wQt-q0nmHnVYohm86YXqsK494uYMGicqDzQlCrpC86NSXs_JbTwtRQTdrUjYHAvsA9vcPzQIbG2uQunP8AkUl65-92ckPVJz1dFBriVy2Nga0I" alt=""/><figcaption><meta charset="utf-8"><em>Documentation contract</em></figcaption></figure>



<p>With Apollo Studio you can point consumers at the tailored contract schema so that they get the full Studio experience with a changelog, comprehensive schema reference, and interactive Explorer scoped to the relevant subset of the graph.</p>



<h3 class="wp-block-heading"><a href="#deployed-contracts" aria-hidden="true" class="aal_anchor" id="deployed-contracts"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Deployed contracts</h3>



<p>There may be times, however, when we want to restrict not only what appears in the documentation, but also what can actually be queried by a particular audience. To accomplish this, we can deploy a dedicated Apollo Gateway or Router to run the contract schema as a separate endpoint.&nbsp;</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh5.googleusercontent.com/CFHUa0cKxHz4zBzLtWflZm6Fx8vkGAK5Ma4ueehqJX9dQUEzqC3T5POt84Y9zN_6xTDsHEYHDA61mBM1JbYqIxw8ZtxbjNKcP6nCVLZ1oW2qM4UtPsSgmRa229YQeFY4GNMUiQGl" alt=""/><figcaption><em>Deployed contract</em></figcaption></figure>



<p>Developers accessing the deployed contract endpoint will only be able to query parts of the graph that exist in the contract schema and will encounter an error if they try to query for fields that are not included in the contract. This can be particularly useful for building endpoints for external partners or for a public-facing API.</p>



<h2 class="wp-block-heading"><a href="#managed-federation-managed-contracts" aria-hidden="true" class="aal_anchor" id="managed-federation-managed-contracts"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Managed Federation, managed contracts</h2>



<p>BFFs and other customized APIs for different audiences are fantastic for providing a streamlined developer experience, but they also create overhead for whoever maintains them. One of the best things about contracts is that they automatically remain up-to-date without any manual work when combined with Apollo Managed Federation.</p>



<figure class="wp-block-image"><img decoding="async" src="https://lh3.googleusercontent.com/Y8eIp6JgHd123W0MoVL_Odzun7AVC4iST_ajRRz1bVoIANjAfmvXCm_Tn71-WJscA-YXHvVbDr9UN50fWnDGTXWRn-CfsfJT9qNQdc9lxGoEDlRKPzpEKL1a_ugBIOs3VadAp2xB" alt=""/></figure>



<p>With Managed Federation in Apollo Studio, independent backend service teams publish subgraph schema updates into Apollo, including any tags to be used for contracts. The subgraph schemas are composed together into a supergraph schema which is then used to power a graph router like the Apollo Gateway or Apollo Router. Using the included tags, contract filters are run on the unified supergraph schema automatically deriving subset contract schemas.</p>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get started</h2>



<p>Contracts are available in preview today on Apollo’s Enterprise plan! If you’d like to learn more about Contracts, check out our <a href="https://www.apollographql.com/docs/studio/contracts/">documentation</a> or join us virtually today at <a href="https://summit.graphql.com/">GraphQL Summit</a> where we’ll be doing a deep dive and demo on contracts during the “How to Serve Many Audiences with One Graph” talk! If you aren’t on Apollo Enterprise and would like to try it out, <a href="https://www.apollographql.com/contact-sales/">talk to us</a> about an Enterprise trial.</p>


Introducing Contracts: serve many audiences with a unified graph


<p><em>🚀 🎉  Heads up &#8211; Federation 2 and Gateway 2.x are now GA! Check out the <a href="https://www.apollographql.com/blog/apollo-federation-2-is-now-generally-available/" data-type="URL" data-id="https://www.apollographql.com/blog/apollo-federation-2-is-now-generally-available/">GA announcement blog</a> or head over to the <a href="https://www.apollographql.com/docs/federation/" data-type="URL" data-id="https://www.apollographql.com/docs/federation/">Federation docs</a> to get started.</em></p>



<hr class="wp-block-separator"/>



<p>It&#8217;s been amazing to see the momentum grow around Apollo Federation with over 1M weekly downloads and 12K+ projects using Apollo Federation. Thanks to community contributions, the thriving ecosystem around Apollo Federation means you can federate subgraphs written in <a href="https://www.apollographql.com/docs/federation/other-servers/">over 12 languages</a> and frameworks.</p>



<p>Originally <a href="https://www.apollographql.com/blog/announcement/apollo-federation-f260cf525d21/">released in 2019</a>, Federation powers some of the largest graphs in the world, including <a href="https://netflixtechblog.com/how-netflix-scales-its-api-with-graphql-federation-part-2-bbe71aaec44a">Netflix</a>, <a href="https://medium.com/walmartglobaltech/federated-graphql-walmart-bfc85c2553de">Walmart</a>, <a href="https://engineering.ziffmedia.com/retailmenot-graphql-federation-3bb36dac5aaa">RetailMeNot</a>, and <a href="https://medium.com/paypal-tech/graphql-at-paypal-an-adoption-story-b7e01175f2b7">PayPal</a>. Developers are choosing Apollo Federation because it’s a proven approach for rapidly scaling a graph across multiple teams.</p>



<p>Today, we’re excited to celebrate the next major milestone: Apollo Federation 2. The new version builds on the success of the original with an improved shared ownership model, enhanced type merging, and cleaner syntax for a smoother developer experience. It’s backwards compatible, requiring no major changes to your subgraphs. <a href="https://www.apollographql.com/docs/federation/v2/quickstart/">Try the alpha today!</a> 🚀</p>



<h2 class="wp-block-heading"><a href="#apollo-federation-2" aria-hidden="true" class="aal_anchor" id="apollo-federation-2"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Apollo Federation 2</h2>



<p>Apollo Federation is an architecture for declaratively composing subgraphs into a unified graph. Each team can own their slice of the graph independently, empowering them to deliver autonomously and incrementally.</p>



<p>Designed in collaboration with the GraphQL community, Federation 2 is a clean-sheet implementation of the core composition and query-planning engine at the heart of Apollo Federation. We’ve improved the developer experience by adding deeper static analysis, cleaner error messages, and new composition hints that help you catch errors sooner and understand how your schema impacts performance. With the new version, we’ve streamlined common tasks like extending a type and simplified advanced workflows like migrating a field across subgraphs with no downtime.</p>



<p>Following in the footsteps of modern infrastructure projects like Elasticsearch and MongoDB, <a href="https://www.apollographql.com/blog/announcement/moving-apollo-federation-2-to-the-elastic-license-v2">we’re moving Federation 2 to the Elastic License v2</a> &#8212; an open and&nbsp;permissive license with few restrictions. This change shouldn’t affect the vast majority of our community, and the new code is still free to use and modify. Subgraph packages will remain MIT, as well as the 0.x Federation packages, so there are no changes to what you’re doing today.</p>



<h3 class="wp-block-heading"><a href="#build-with-any-natural-graphql-schema" aria-hidden="true" class="aal_anchor" id="build-with-any-natural-graphql-schema"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Build with any natural GraphQL schema</h3>



<p>Federation 2 adds first-class support for shared interfaces, enums, and other value types. Common tasks like extending a federated type or denormalizing a field for better performance are now possible without special directives and keywords.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="405" src="https://wp.apollographql.com/wp-content/uploads/2021/11/image-21-natural-graphql-1024x405.png" alt="" class="wp-image-10646" srcset="https://wp.apollographql.com/wp-content/uploads/2021/11/image-21-natural-graphql-1024x405.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-21-natural-graphql-300x119.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-21-natural-graphql-768x304.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-21-natural-graphql-1536x607.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-21-natural-graphql-2048x810.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-21-natural-graphql-1200x474.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-21-natural-graphql-1980x783.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h3 class="wp-block-heading"><a href="#deliver-smaller-increments-with-better-shared-types" aria-hidden="true" class="aal_anchor" id="deliver-smaller-increments-with-better-shared-types"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Deliver smaller increments with better shared types</h3>



<p>Apollo Federation already supports a shared ownership model that lets you spread a federated type across subgraphs to distribute its implementation. You can reuse common value types like interfaces and enums. However, there are restrictions on how shared types can be defined and evolved. As a result, teams may find themselves stuck when making changes to shared types until all subgraphs are able to deliver a coordinated change in lockstep.</p>



<p>Federation 2 removes these restrictions with an improved shared ownership model and enhanced type merging that enables teams to deliver smaller incremental changes with a cleaner separation of concerns.</p>



<p><strong>Flexible value type merging </strong>is now supported, so value types don’t need to be identical across subgraphs. Value type definitions are now merged into a single unified type, much like type merging support for federated types today. Smaller incremental changes, like adding a field, can often be rolled out one subgraph at a time.</p>



<p><strong>Federated types have improved shared ownership,</strong> which means fields can now exist in multiple subgraphs simultaneously. This paves the way for natively supported field migrations with an asynchronous transfer of ownership from one subgraph to another with no downtime or tight release coordination.</p>



<h3 class="wp-block-heading"><a href="#catch-errors-sooner-with-improved-static-analysis" aria-hidden="true" class="aal_anchor" id="catch-errors-sooner-with-improved-static-analysis"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Catch errors sooner with improved static analysis</h3>



<p>Federation 2 has deeper static analysis, better error messages and a new generalized composition model that helps you catch more errors at build-time instead of at runtime. The rewritten composition engine now validates all theoretically possible queries and provides more descriptive error messages when a query can’t be satisfied.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="484" src="https://wp.apollographql.com/wp-content/uploads/2021/11/image-19-deeper-validation-1024x484.png" alt="" class="wp-image-10612" srcset="https://wp.apollographql.com/wp-content/uploads/2021/11/image-19-deeper-validation-1024x484.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-19-deeper-validation-300x142.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-19-deeper-validation-768x363.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-19-deeper-validation-1536x726.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-19-deeper-validation-2048x968.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-19-deeper-validation-1200x567.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/11/image-19-deeper-validation-1980x936.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>New composition hints help you understand how schema definitions influence query planning and performance. We’ve integrated them into the <a href="https://www.apollographql.com/blog/announcement/tooling/powerful-new-graphql-tools-for-apollo-federation/">powerful tools for Apollo Federation</a>:</p>



<ul class="wp-block-list"><li><a href="https://marketplace.visualstudio.com/items?itemName=apollographql.apollo-workbench">Apollo Workbench</a> shows composition hints in the problems tray with new hover tips.&nbsp;</li><li><a href="https://www.apollographql.com/docs/rover/">Rover</a> includes composition hints in both standard and structured JSON output so you can integrate them with other tools in your pipeline.</li><li><a href="https://www.apollographql.com/docs/studio/">Apollo Studio</a> uses composition hints to help you ensure design guidelines and best practices.</li></ul>



<p>While Federation 2 is<a href="https://www.apollographql.com/docs/federation/v2/federation-2/backward-compatibility/"> backwards compatible</a>, its enhanced validation might catch a few things that the original Federation didn&#8217;t. Things you&#8217;ll be happy to know about!</p>



<h2 class="wp-block-heading"><a href="#quick-tour-of-federation-2" aria-hidden="true" class="aal_anchor" id="quick-tour-of-federation-2"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Quick tour of Federation 2</h2>



<p>We’ve prepared this video to highlight some key improvements in Federation 2, including Apollo Workbench support for composition hints. You’ll also learn how to compose and run a graph with Federation 2 using the v2 gateway and Apollo Studio.</p>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="Apollo Federation 2: Preview Demo with Apollo Studio and Workbench" width="580" height="326" src="https://www.youtube.com/embed/WcHYa39bUk8?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started</h2>



<p>We’d love your early feedback on the initial alpha release!</p>



<ul class="wp-block-list"><li><a href="https://www.apollographql.com/docs/federation/v2">Read the docs</a></li><li><a href="https://www.apollographql.com/docs/federation/v2/quickstart/">Try it out</a></li><li><a href="https://community.apollographql.com/t/announcing-apollo-federation-2/1821">Let us know what you think!</a></li></ul>



<h2 class="wp-block-heading"><a href="#whats-next" aria-hidden="true" class="aal_anchor" id="whats-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s next?</h2>



<p>There’s a lot we’re adding in the coming months:</p>



<ul class="wp-block-list"><li>New directives that support a stronger source of truth, field migration across subgraphs, and type merging that can be relaxed even further.</li><li>Expanded use of <a href="https://specs.apollo.dev/core/v0.2">core schemas</a> to compose your own directives in subgraphs and process supergraph schemas with a new <a href="https://github.com/apollographql/core-schema-js">core-schema-js</a> library.</li><li>Harmonizing shared value types across subgraphs to steward core common types to a desired state.</li><li>Importing shared types into subgraph schemas, to keep things more DRY.</li><li>Advanced caching, auth, demand control, rate limiting, governance, and more!</li></ul>



<h2 class="wp-block-heading"><a href="#learn-more-at-graphql-summit" aria-hidden="true" class="aal_anchor" id="learn-more-at-graphql-summit"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Learn more at GraphQL Summit</h2>



<p>See Federation 2 in action at GraphQL Summit on November 10th and 11th, 2021.&nbsp;</p>



<p><a href="https://summit.graphql.com/#register">Register for free</a> and join us for the keynote and a deep dive session on “The Future of Apollo Federation.” We’ll discuss and demo Federation 2, designed in collaboration with Netflix, to make it even easier to build, use and scale your graph!</p>



<h2 class="wp-block-heading"><a href="#get-involved" aria-hidden="true" class="aal_anchor" id="get-involved"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Get involved!</h2>



<ul class="wp-block-list"><li><a href="https://github.com/apollographql/federation">GitHub</a></li><li><a href="https://community.apollographql.com/">Apollo Community Forum</a></li><li><a href="https://community.apollographql.com/t/apollo-federation-subgraph-library-maintainer-support/1112">Subgraph Library Maintainer Support</a></li></ul>


Announcing Apollo Federation 2


<p>Today, we are introducing <a href="https://www.apollographql.com/blog/announcement/backend/announcing-federation-2">Apollo Federation 2</a>, a major update to our graph composition technology that lets developers build and evolve a unified graph in a modular, principled way. Federation 2 is a new implementation of our query planner and execution gateway that introduces a more flexible model for how types and fields compose across subgraphs. As part of this release, we’re changing the license for the new core federation libraries to the <a href="https://www.apollographql.com/docs/resources/elastic-license-v2-faq">Elastic License v2</a> (ELv2).</p>



<h2 class="wp-block-heading"><a href="#why-the-new-license" aria-hidden="true" class="aal_anchor" id="why-the-new-license"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Why the new license?</strong></h2>



<p>The Apollo developer community is at the heart of everything we do. As stewards of our community, we have a responsibility to prevent harm from anyone who intends to exploit our work without contributing back. We want to continue serving you by funding the development of important open-source graph technology, like our MIT-licensed projects Apollo Client, Apollo Server, and <code>apollo-rs</code>, for years to come. To honor that commitment, we’re moving Apollo Federation 2 to the Elastic License v2 (ELv2).</p>



<p><br>Open-source licensing is evolving with the cloud. Many successful companies built on open-source technology (such as <a href="https://www.elastic.co/blog/elastic-license-v2">Elastic</a>, <a href="https://www.mongodb.com/blog/post/mongodb-now-released-under-the-server-side-public-license">MongoDB</a>, and <a href="https://www.confluent.io/blog/license-changes-confluent-platform/">Confluent</a>) have followed the path we’re taking to protect their communities and combine open, collaborative development with the benefits of cloud services that are easy to adopt and manage. In that spirit, we worked with <a href="https://heathermeeker.com/about-me/">Heather Meeker</a>, a lawyer specializing in open-source software who has worked with Mozilla and Elastic, to steer us toward the best open license for Apollo Federation.</p>



<h2 class="wp-block-heading"><a href="#elastic-license-v2" aria-hidden="true" class="aal_anchor" id="elastic-license-v2"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Elastic License v2</strong></h2>



<p>Instead of creating our own license, we chose ELv2 because of its simplicity and permissiveness. You shouldn’t have to involve your company’s legal department to adopt Apollo Federation, which is why we chose a license that’s already familiar if you’re using Elasticsearch. Although this change shouldn’t affect the vast majority of our community and customers, we want your migration to Apollo Federation 2 to be friction-free. Read <a href="https://www.apollographql.com/docs/resources/elastic-license-v2-faq">the FAQ</a> for more guidance.</p>



<p>The <a href="https://www.elastic.co/licensing/elastic-license">Elastic License v2 (ELv2)</a> is simple and permissive. You can use, copy, modify, and distribute the software as long as you stay within three limitations. You can’t:</p>



<ol class="wp-block-list"><li>Provide federation tooling as a managed service</li><li>Circumvent the license key functionality or remove/obscure features protected by license keys&nbsp;</li><li>Remove or obscure any licensing, copyright, or other notices</li></ol>



<p>There is no impact to most of our community and customers. Just as before, running a federated graph in production (both public and private) is permitted, as is modifying or extending any part of the federation code. To address your questions, we’ve included some examples in <a href="https://www.apollographql.com/docs/resources/elastic-license-v2-faq">our FAQ</a> that explain the limitation on “managed services.”</p>



<h3 class="wp-block-heading"><a href="#libraries-under-the-elastic-license-v2" aria-hidden="true" class="aal_anchor" id="libraries-under-the-elastic-license-v2"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Libraries under the Elastic License v2</strong></h3>



<p>We’re licensing the following libraries under ELv2:</p>



<ul class="wp-block-list"><li>Apollo Federation 2 gateway and libraries, starting with the v2.0.0-alpha.* release</li><li>Rover composition add-on (<code>rover-fed2</code>)</li><li>Apollo Workbench</li></ul>



<p>The license applies to the source code, as well as the binaries and packages distributed on npm and the VS Code Marketplace.</p>



<h3 class="wp-block-heading"><a href="#libraries-that-remain-mit-licensed" aria-hidden="true" class="aal_anchor" id="libraries-that-remain-mit-licensed"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Libraries that remain MIT-licensed</strong></h3>



<p>Excluding our Federation 2 libraries, nearly all of our 100+ public repositories on <a href="https://github.com/apollographql">GitHub</a> are MIT-licensed. The open-source libraries you know and love, such as Rover, Apollo Client, and Apollo Server, will stay MIT-licensed.</p>



<p>Apollo Federation 0.x libraries will remain MIT-licensed. We want you to migrate at your own pace, so we will actively maintain the Apollo Federation 0.x packages by merging compatibility updates, bug fixes, security patches, and select feature enhancements through the end of 2022.</p>



<p>We’re grateful for the subgraph maintainers who have built a healthy ecosystem around Apollo Federation. Over 12 GraphQL servers, <a href="https://www.apollographql.com/docs/federation/other-servers/">in languages ranging from Kotlin to Ruby</a>, all support Apollo Federation for composing subgraphs. All subgraph libraries under <code>@apollo/subgraph</code> will remain MIT-licensed.</p>



<p>We’re committed to developing and maintaining open-source software for the graph ecosystem. It’s why we’ve released software we use to build Apollo Federation, such as <a href="https://www.apollographql.com/blog/announcement/tooling/apollo-rs-graphql-tools-in-rust/">apollo-rs</a> (a GraphQL parser for Rust), under the MIT license.</p>



<h2 class="wp-block-heading"><a href="#a-call-for-a-standard-open-license" aria-hidden="true" class="aal_anchor" id="a-call-for-a-standard-open-license"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>A call for a standard open license</strong></h2>



<p>When <a href="https://www.elastic.co/blog/elastic-license-v2">the Elastic License v2 was released</a>, Elastic CEO Shay Banon called upon open-source companies facing a similar decision to “coalesce around a smaller number of licenses.” We’re excited to be part of this coalition of modern infrastructure companies building businesses that empower developers. Adopting software shouldn’t require a legal degree to decipher complex licenses and restrictions, which is why we are championing a single, standard open license with the simplest language and least amount of limitations necessary.</p>



<p>Not only do you deserve a friction-free development experience, you also deserve choice. We’re seeing a rapid shift toward unbundling the cloud where you can compose the best tools and services for your needs by mixing and matching them seamlessly. You should pick the stack that’s best for you, instead of picking a service because it comes from the same vendor providing other parts of the stack.</p>



<p>Apollo has always been about helping developers build amazing applications. Moving the Apollo Federation libraries and gateway to ELv2 helps us focus on our mission: empowering all of you.</p>


Apollo is moving Federation 2 to the Elastic License v2

Moving Apollo Federation 2 to the Elastic License v2

Announcing apollo-rs, new GraphQL tools in Rust

apollo-rs: spec-compliant GraphQL tools in Rust

Launch with confidence: introducing the Apollo Studio Launches dashboard


<p>Ever faced the conundrum of how to share your GraphQL schema with users outside of your organization, perhaps with partner or vendor developers? If so, Apollo now has a simple solution for you! We recently launched the ability to make graphs in Apollo Studio publicly visible so that you share your graph with anyone, even those without a Studio login.</p>



<h2 class="wp-block-heading"><a href="#how-to-share-graphs-outside-of-your-apollo-organization" aria-hidden="true" class="aal_anchor" id="how-to-share-graphs-outside-of-your-apollo-organization"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How to share graphs outside of your Apollo organization</h2>



<p>Making your graph publicly visible is as easy as flipping a switch. Simply navigate to the Settings page for your graph in Apollo Studio and under the Access tab, set <em>a variant of your choosing as “public.” </em>That particular variant of your graph is now publicly visible in Apollo Studio!</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="409" src="https://wp.apollographql.com/wp-content/uploads/2021/10/public-switch-1024x409.png" alt="" class="wp-image-9554" srcset="https://wp.apollographql.com/wp-content/uploads/2021/10/public-switch-1024x409.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/10/public-switch-300x120.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/10/public-switch-768x307.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/10/public-switch-1536x614.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/10/public-switch-1200x480.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/10/public-switch-1980x791.png 1980w, https://wp.apollographql.com/wp-content/uploads/2021/10/public-switch.png 1999w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>Toggle a variant to public in Graph Settings → Access</figcaption></figure>



<h2 class="wp-block-heading"><a href="#whats-visible-when-a-graph-is-public" aria-hidden="true" class="aal_anchor" id="whats-visible-when-a-graph-is-public"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s visible when a graph is public?</h2>



<p>When a variant of a graph is set to public, anyone can navigate to the public Studio URL for that variant and access the README, schema reference, changelog, and Explorer (this is equivalent to <a href="https://www.apollographql.com/blog/announcement/platform/sharing-your-graph-just-got-a-whole-lot-easier-announcing-unlimited-consumer-seats/">Consumer-level access</a>). You can preview how the public view will appear to external users by clicking the <code>Public ↗︎</code> icon in the top nav.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1426" height="805" src="https://wp.apollographql.com/wp-content/uploads/2021/10/preview-public-view.gif" alt="" class="wp-image-9558"/></figure>



<p>You can share the public link with any user, even outside of the Studio organization to explore and consume your graph!</p>



<p><strong>⚠️ Note:</strong> When a specific graph variant is marked as “public”, any unauthenticated user on the internet with the link to the public variant can access its schema. However, accessing endpoint to query data could require authentication depending on the GraphQL endpoint configuration.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1424" height="853" src="https://wp.apollographql.com/wp-content/uploads/2021/10/copy-public-url.gif" alt="" class="wp-image-9561"/></figure>



<h2 class="wp-block-heading"><a href="#give-all-developers-a-great-ux-for-your-graph" aria-hidden="true" class="aal_anchor" id="give-all-developers-a-great-ux-for-your-graph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Give all developers a great UX for your graph</h2>



<p>You may be wondering, “GraphQL already has introspection, why shouldn’t I just use that?”&nbsp;Well, in addition to the many <a href="https://www.apollographql.com/blog/graphql/security/why-you-should-disable-graphql-introspection-in-production/">security considerations</a> that make disabling introspection in production a good idea, there are also many UX benefits that you miss out on with introspection alone.</p>



<h3 class="wp-block-heading"><a href="#a-better-onboarding-experience-for-new-developers" aria-hidden="true" class="aal_anchor" id="a-better-onboarding-experience-for-new-developers"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>A better onboarding experience for new developers</strong></h3>



<p>By making your graph public in Apollo Studio, every developer automatically gets access to the README, schema docs, changelog, and Explorer, all in one central location. No more building custom documentation portals and changelogs that have to be manually updated.</p>



<h3 class="wp-block-heading"><a href="#be-specific-about-what-you-share-externally" aria-hidden="true" class="aal_anchor" id="be-specific-about-what-you-share-externally"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Be specific about what you share externally</strong></h3>



<p>A key problem with introspection is that it makes your entire graph visible, including things like experimental fields that you may not want external developers to use yet. With Apollo Studio, you can make an approved, production variant public and keep private, pre-production variants to create and test new fields. In the near future, we’ll be adding more features to make sharing even more customizable!</p>



<h2 class="wp-block-heading"><a href="#share-your-graphs-today" aria-hidden="true" class="aal_anchor" id="share-your-graphs-today"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Share your graphs today!</h2>



<p>Excited? We hope so! Sharing graphs with a broader audience could not get any easier. And don’t forget to update the <a href="https://www.apollographql.com/blog/announcement/platform/create-a-readme-to-onboard-developers-to-the-graph/">README</a> of your graph before sharing. <a href="https://studio.apollographql.com/sandbox/explorer?endpoint=https%3A%2F%2Fapi.spacex.land%2Fgraphql%2F&amp;explorerURLState=N4IgJg9gxgrgtgUwHYBcQC4QEcYIE4CeABADICGMSUAFggM5HAA6SRRANhVbQ862xy40A%2BgQRk8LAUTgBLOnVkQkwpGURSiAXxZaQAGhAA3CbLIAjdvQwgQWoA">Head over to Studio</a> and get wider adoption of your graph today! And as always, we love hearing from you, so if you have any feedback, please drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


Make your GraphQL schema publicly visible without introspection


<p>Intrigued? We hope so! We recently introduced three of the most requested features from our developer community &#8211; tabs in Explorer, offline support for local development in Sandbox, and an improved integration experience between VS Code and Apollo Studio. The request for tabs in Explorer, especially, has been overwhelming:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="322" src="https://wp.apollographql.com/wp-content/uploads/2021/10/image-3-1024x322.png" alt="" class="wp-image-9472" srcset="https://wp.apollographql.com/wp-content/uploads/2021/10/image-3-1024x322.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/10/image-3-300x94.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/10/image-3-768x242.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/10/image-3.png 1068w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>We even dedicated a Slack emoji to it!</p>



<figure class="wp-block-image size-full is-resized"><img loading="lazy" decoding="async" src="https://wp.apollographql.com/wp-content/uploads/2021/10/tab-msg.gif" alt="" class="wp-image-9474" width="600" height="199"/></figure>



<h2 class="wp-block-heading"><a href="#1-tabs-in-explorer" aria-hidden="true" class="aal_anchor" id="1-tabs-in-explorer"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>1. Tabs in Explorer</strong></h2>



<p>Need I say more? Test out <a href="https://www.apollographql.com/blog/tooling/graphql-ide/the-5-most-useful-features-of-apollo-studio-explorer-that-you-didnt-know-existed/#:~:text=1.%20Multiple%20operations">multiple operations in the same tab</a> or multiple operations in different tabs when exploring your GraphQL endpoint in Explorer! Testing and managing multiple operations in Explorer could not get any easier.&nbsp;</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1435" height="788" src="https://wp.apollographql.com/wp-content/uploads/2022/01/Screen-Recording-2022-01-27-at-10.53.12-AM.gif" alt="" class="wp-image-11987"/></figure>



<h2 class="wp-block-heading"><a href="#2-offline-support-for-local-development-in-sandbox" aria-hidden="true" class="aal_anchor" id="2-offline-support-for-local-development-in-sandbox"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>2. Offline support for local development in Sandbox</strong></h2>



<p>We launched <a href="https://www.apollographql.com/blog/announcement/platform/apollo-sandbox-an-open-graphql-ide-for-local-development/">Apollo Sandbox</a> three months ago. And now, we are making it available offline for local development. Flaky internet? Worry no more! If you are developing <em>locally</em> using Sandbox, you can continue to work without any internet connection.&nbsp;</p>



<p>⚠️ <strong>Note:</strong> you’ll need to load at least one Sandbox tab while you’re connected to the internet to update to the latest bundle, but after that, you can continue to work without any internet connection.</p>



<h2 class="wp-block-heading"><a href="#3-run-operations-in-apollo-studio-from-vscode" aria-hidden="true" class="aal_anchor" id="3-run-operations-in-apollo-studio-from-vscode"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>3. Run operations in Apollo Studio from VSCode</strong></h2>



<p>The final feature that we recently added is the “Run in Studio” button in our <a href="https://marketplace.visualstudio.com/items?itemName=apollographql.vscode-apollo">VS Code extension</a>. There is now a hover on the play button in VS Code, which opens the exact operation and fragments that you want to test in Apollo Studio Explorer, saving you dozens of clicks and the tedious task of setting up an operation to test!</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1266" height="877" src="https://wp.apollographql.com/wp-content/uploads/2021/10/Screen-Recording-2021-09-23-at-08.29.42-PM.gif" alt="" class="wp-image-9446"/></figure>



<h2 class="wp-block-heading"><a href="#get-started" aria-hidden="true" class="aal_anchor" id="get-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Get Started!</strong></h2>



<p>So what are you waiting for? All these features are now available in Apollo Studio Explorer and Apollo Sandbox. <a href="https://studio.apollographql.com/sandbox/explorer?endpoint=https%3A%2F%2Fapi.spacex.land%2Fgraphql%2F&amp;explorerURLState=N4IgJg9gxgrgtgUwHYBcQC4QEcYIE4CeABADICGMSUAFggM5HAA6SRRANhVbQ862xy40A%2BgQRk8LAUTgBLOnVkQkwpGURSiAXxZaQAGhAA3CbLIAjdvQwgQWoA">Head over there</a> and try them out! And as always, we love hearing from you, so if you have any feedback, please drop a post on the <a href="https://github.com/apollographql/apollo-studio-community/issues">Apollo Studio GitHub Community</a>!</p>


We’re shipping 3 of our most requested features!


<p>When you’re maintaining a graph that’s used by multiple developers, it’s important to make sure everyone is on the same page by providing instructions on how to get started with consuming and contributing to the graph. Today, we’re introducing a way to do that natively in Apollo Studio with the new README page.</p>



<p>The README appears as a new 🏠 icon in the left nav in Apollo Studio and will now be the default page shown when navigating to any graph in Apollo.</p>



<h2 class="wp-block-heading"><a href="#what-is-the-readme" aria-hidden="true" class="aal_anchor" id="what-is-the-readme"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What is the README?</h2>



<p>The new page includes helpful graph metadata like its name, when it was last updated, its endpoint, the most recent commit hash, links to Explorer and its changelog, and, most importantly, a README! As more developers and teams begin to use your graph, the README ensures that everyone has the information they need to onboard quickly and more independently.</p>



<figure class="wp-block-image size-large is-style-default"><img loading="lazy" decoding="async" width="1024" height="520" src="https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-1024x520.png" alt="" class="wp-image-9251" srcset="https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-1024x520.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-300x152.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-768x390.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-1536x780.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-2048x1040.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-1200x609.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/09/studio.apollographql.com_graph_acephei_home_variantproduction-1-1980x1005.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#customizing-your-readme" aria-hidden="true" class="aal_anchor" id="customizing-your-readme"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Customizing your README</h2>



<p>The README for each variant contains default markdown content to help get you started, but it can easily be updated to include any pertinent information for your graph like:</p>



<ul class="wp-block-list"><li>A description of your graph</li><li>Instructions for access and authentication</li><li>Example operations to showcase how the graph can be used</li><li>And more!</li></ul>



<p>Unlike a plain markdown document, the README in Apollo Studio also offers graph shortcodes that allow you to reference graph variables with just a click.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="800" height="450" src="https://wp.apollographql.com/wp-content/uploads/2021/09/readme.gif" alt="" class="wp-image-9272"/></figure>



<h2 class="wp-block-heading"><a href="#go-make-a-readme" aria-hidden="true" class="aal_anchor" id="go-make-a-readme"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Go make a README!</h2>



<p>The README is available right now in Apollo Studio, so what are you waiting for? <a href="http://studio.apollographql.com">Head over there</a> and make an awesome README to help developers make the most of your graph! And as always, we love hearing from you, so if you have any feedback on the README feature in Apollo Studio, please fill out our <a href="https://docs.google.com/forms/d/e/1FAIpQLScIBKsl_s7GO7ebwG3JAbPdcszn5IErni3nyyjMW9lfnXsUpw/viewform?usp=sf_link">feedback survey</a>!</p>


Create a README to onboard developers to the graph


<p>Today, we’re delighted to share that we’ve raised a $130M Series D led by Insight Ventures, with participation from existing investors Andreessen Horowitz and Matrix Partners. This new round is an exciting milestone for Apollo, now valued at over $1.5B.</p>



<p>We see this news as a win for developers everywhere because Apollo’s mission is to help app developers help the world. We will use the funding to create pioneering open-source graph technology that makes app development faster and more accessible for everyone.</p>



<p>The graph has exploded in popularity among developers. 86% of JavaScript developers rank GraphQL as the <a href="https://2020.stateofjs.com/en-US/awards/">top technology they want to learn</a>. Developers trust Apollo to implement their graph, with over 17M monthly open-source downloads and over 6B queries run on the Apollo graph each day.</p>



<p>Apollo has always been first and foremost a developer community, and I’m so proud of what we’ve all accomplished together. It’s an exciting time for all of us and I can’t wait for what’s next. 🚀</p>



<h2 class="wp-block-heading"><a href="#rise-of-the-graph" aria-hidden="true" class="aal_anchor" id="rise-of-the-graph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a><strong>Rise of the graph</strong></h2>



<p>We created Apollo to solve the biggest drag on app developer productivity: the data layer that connects apps to backend services.</p>



<p>Today, instead of building features, developers spend the majority of their time writing data-plumbing code to connect an ever-increasing number of clients and microservices. Architectures such as backends-for-frontends and API gateways add to the complexity for client development teams, who have to duplicate data-fetching code for each client they support.</p>



<p>The <strong>graph</strong> is a new layer of the stack that solves this problem by connecting apps to the backend microservices they rely on in a unified way. Client developers write a single GraphQL query to fetch all the data they need, while frontend and backend teams can rely on the graph as a shared contract without tightly coupling their work.</p>



<figure class="wp-block-image alignwide size-large"><img loading="lazy" decoding="async" width="1024" height="319" src="https://wp.apollographql.com/wp-content/uploads/2021/08/apollo-graph-diagram-1-1024x319.png" alt="The graph connects client apps to backend microservices in a unified way." class="wp-image-8691" srcset="https://wp.apollographql.com/wp-content/uploads/2021/08/apollo-graph-diagram-1-1024x319.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/08/apollo-graph-diagram-1-300x93.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/08/apollo-graph-diagram-1-768x239.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/08/apollo-graph-diagram-1.png 1108w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>Engineering leaders in every industry are choosing Apollo because the graph has transformed how companies develop apps. Companies in industries ranging from retail (Walmart, Wayfair), financial services (PayPal), and media (The New York Times) have accelerated product delivery with a graph. Expedia was able to rebuild their entire Trips experience in less than a year with an Apollo graph, estimated to take three years with their old architecture.</p>



<p>Developers are driving the momentum behind the graph and changing how companies build software. Their technology choices can have a profound impact on the global economy. That’s why Apollo is dedicated to our mission to help developers help the world.</p>



<h2 class="wp-block-heading"><a href="#scaling-the-graph" aria-hidden="true" class="aal_anchor" id="scaling-the-graph"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Scaling the graph</h2>



<p>While the graph’s flexibility and power is a great strength, it can also become a drawback when teams spin up multiple, unconnected graphs without a strategy. It’s important to be intentional when rolling out a graph and adopt a unified graph strategy once GraphQL usage spreads across multiple teams.</p>



<figure class="wp-block-image alignwide size-large"><img loading="lazy" decoding="async" width="1024" height="433" src="https://wp.apollographql.com/wp-content/uploads/2021/08/apollo-graph-platform-1-1024x433.png" alt="The Apollo Graph Platform helps developers build a unified graph." class="wp-image-8687" srcset="https://wp.apollographql.com/wp-content/uploads/2021/08/apollo-graph-platform-1-1024x433.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/08/apollo-graph-platform-1-300x127.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/08/apollo-graph-platform-1-768x325.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/08/apollo-graph-platform-1.png 1108w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>A <strong>unified graph</strong> provides a single view of your company’s data, services, and capabilities. The Apollo Graph Platform helps developers incrementally adopt a unified graph with end-to-end tooling built on Apollo’s open-source software.</p>



<p>When developers adopt a unified graph, they can build functionality faster than ever before while maintaining a consistent UX across platforms. That speeds their progress in creating apps that make the world better for all of us.</p>



<h2 class="wp-block-heading"><a href="#whats-next-for-apollo" aria-hidden="true" class="aal_anchor" id="whats-next-for-apollo"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What&#8217;s next for Apollo</h2>



<p>This new round of funding brings more opportunities for Apollo to support our community and customers. We’re committed to advancing the graph with open-source software, as well as being responsible stewards of the resources we have to help developers. Here’s some of what’s next:</p>



<ul class="wp-block-list"><li><strong>Build open-source software for the GraphQL community:</strong> That includes evolving our current offerings such as Apollo Client and Federation, as well as investing in developer education and new projects. We’re excited to collaborate with the community on ideas that haven’t been explored yet as we push the graph ecosystem forward together.</li><li><strong>Expand Apollo Federation to more languages</strong>: From Walmart to Zillow, forward-thinking engineering leaders choose federation for architecting a unified graph. We want the federation experience to be seamless no matter what language you’re working with, so we’re adding first-class support for more languages such as Java and Ruby in collaboration with GraphQL server maintainers. If that’s you, <a href="https://community.apollographql.com/t/apollo-federation-library-maintainer-support/1112">let’s chat</a>!</li><li><strong>Scale our team:</strong> Over the past year, we’ve doubled the company to over 100 Apollonauts in 10 countries around the world. If building graph technology to help app developers sounds like a mission you can get behind, <a href="https://www.apollographql.com/careers/">come join us</a>! Current engineering needs include Rustaceans, cloud scalability engineers, and security experts. We’re adding new positions every week, so check our <a href="https://www.apollographql.com/careers/#positions">open roles</a> frequently.</li></ul>



<h2 class="wp-block-heading"><a href="#thank-you" aria-hidden="true" class="aal_anchor" id="thank-you"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Thank you</h2>



<p>The exponential growth of the Apollo community over the last two years has been both exhilarating and humbling. We are grateful for your support and the opportunity to serve the community. Many thanks to our customers for choosing to partner with Apollo to power their graphs. And thank you to all the Apollonauts who got us to this point.</p>



<p>This is just the beginning. We have only scratched the surface of what is possible with graph technology, and there is much more in store. I believe that the graph is a foundational technology that will truly change the world, just as the cloud, mobile devices, and big data have impacted how we all use technology every day. As excited as I am about our progress, I’m even more energized by what’s to come.</p>


Apollo raises $130M to pioneer the Graph for app developers


<p>Today, we’re introducing audit logs in Apollo Studio Enterprise. With audit logs, you can export a data file with key actions taken within your organization.</p>



<p>As your graph scales to more teams in your organization, you need visibility into all of the potential change points on your graph that could affect its stability or performance. We built audit logs to give you more confidence in your graph governance and help you meet any compliance or security requirements.</p>



<p><strong>Use Cases for Audit Log</strong></p>



<ul class="wp-block-list">
<li>Investigate an incident and see what actions lead up to that incident by exporting a log for a time period and graph</li>



<li>See what actions an individual has taken within a time period</li>



<li>Investigate your automated systems that are changing the graph</li>
</ul>



<p><strong>Some actions tracked by audit log:</strong></p>



<ul class="wp-block-list">
<li>Creating a graph or variant</li>



<li>Publishing of schema/subschema</li>



<li>Provisioning or inviting users</li>



<li>Adjusting billing</li>



<li>Provisioning or deleting an API key</li>



<li>Adjustments to settings for schema checks</li>
</ul>



<p>This is a partial list of what audit logs track, you can see the more complete list of actions tracked in our <a href="https://www.apollographql.com/docs/studio/audit-log/" target="_blank" rel="noreferrer noopener">docs</a>. Audit logs include actions done by individuals as well as automated actions via the API or CLI. Data for the audit log is retained for up to 180 days<strong>.</strong></p>



<p><p><strong>How to download an audit log</strong></p><p>Audit logs are accessible by organization admins via a new Audit tab inside Apollo Studio UI. When requesting a log, you can filter your exports to a specific actor, action on a specific graph, and/or specific time window. Once an audit log export is requested you’ll receive an on-screen indication as well as an email notification when the log is ready for download.</p></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="857" height="1024" src="https://wp.apollographql.com/wp-content/uploads/2021/08/image-1-857x1024.png" alt="Generate an audit log" class="wp-image-8261" srcset="https://wp.apollographql.com/wp-content/uploads/2021/08/image-1-857x1024.png 857w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1-251x300.png 251w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1-768x918.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1.png 1200w" sizes="auto, (max-width: 857px) 100vw, 857px" /><figcaption class="wp-element-caption">Create a customized audit log </figcaption></figure>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="399" src="https://wp.apollographql.com/wp-content/uploads/2021/08/image-1024x399.png" alt="Historical records of audit logs" class="wp-image-8259" srcset="https://wp.apollographql.com/wp-content/uploads/2021/08/image-1024x399.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-300x117.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-768x300.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1536x599.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-2048x799.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1200x468.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/08/image-1980x772.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">View all of the audit <em>logs</em> that have been requested</figcaption></figure>



<p></p>



<p><strong>Get started</strong><br>Audit logs are part of the Studio Enterprise plan. Please <a href="https://www.apollographql.com/contact-sales/?referrer=blog" data-type="URL" target="_blank" rel="noreferrer noopener">reach out to us </a>if you are interested in this feature.</p>


Audit Logs now available in Apollo Studio Enterprise


<p>How do you debug or optimize a request as it travels through all the layers of your stack: from the client, through the Apollo Gateway, through your subgraph services, all the way to your databases?</p>



<p>First, you need visibility into what your code is doing during that request, regardless of how that work is distributed across machines. Fortunately, this is easier than ever with a Cloud-Native Computing Foundation project called <a href="https://opentelemetry.io/">OpenTelemetry</a>!</p>



<p>As of version 0.31.1, <a href="https://www.apollographql.com/docs/federation/api/apollo-gateway">@apollo/gateway</a> natively supports OpenTelemetry as part of a complete picture of the performance and reliability of a federated GraphQL request. You can find <a href="https://www.apollographql.com/docs/federation/opentelemetry/">the documentation here</a>.</p>



<p>In this article, I’ll cover some OpenTelemetry basics, talk about the new support for OpenTelemetry in Apollo Gateway, and explain how Apollo Studio and OpenTelemetry work together to give you a complete picture of your graph.</p>



<h2 class="wp-block-heading"><a href="#what-is-opentelemetry" aria-hidden="true" class="aal_anchor" id="what-is-opentelemetry"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What is OpenTelemetry?</h2>



<p>OpenTelemetry (or OTel) is “an observability framework for cloud-native software”. It is a collection of libraries, systems, and applications for instrumenting, collecting, and exporting information about workloads that span multiple applications.</p>



<p>A unit of work in OTel is a “span”. You can wrap a function call in a span, recording its duration and other metadata. You can also install instrumentation that automatically hooks into modules and functions, like the <a href="https://www.npmjs.com/package/@opentelemetry/instrumentation-http">HTTP instrumentation</a> for Node.js.</p>



<p>A collection of related spans is called a “trace”. In a single system, a trace is very similar to a stack trace. But what makes OpenTelemetry (and its predecessors, OpenTracing and OpenCensus) powerful is the ability to correlate spans across systems. It does this by propagating trace identifiers in remote calls. When making HTTP requests, for example, OTel instrumentation adds trace IDs as HTTP headers.</p>



<p>Once you have a trace, you can aggregate them in a “collector” and efficiently send them to your observability tools with an “exporter”.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="605" src="https://wp.apollographql.com/wp-content/uploads/2021/07/OpenTelemetryApolloFederation-1024x605.png" alt="" class="wp-image-8203" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/OpenTelemetryApolloFederation-1024x605.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/OpenTelemetryApolloFederation-300x177.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/OpenTelemetryApolloFederation-768x454.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/OpenTelemetryApolloFederation.png 1144w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>A diagram of a request flowing through a federated GraphQL architecture with OpenTelemetry and Apollo traces published to an OTel collector and Apollo Studio, respectively.</figcaption></figure>



<p>There’s obviously a lot more to OpenTelemetry (<a href="https://opentelemetry.io/docs/concepts/what-is-opentelemetry/">see the docs!</a>), but that covers it in the context of Apollo Federation.</p>



<h2 class="wp-block-heading"><a href="#opentelemetry-in-apollo-server-and-apollo-gateway" aria-hidden="true" class="aal_anchor" id="opentelemetry-in-apollo-server-and-apollo-gateway"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>OpenTelemetry in Apollo Server and Apollo Gateway</h2>



<p>Apollo Server has always supported OpenTelemetry via the <a href="https://www.npmjs.com/package/@opentelemetry/instrumentation-graphql">@opentelemetry/instrumentation-graphql</a> library, which instruments the underlying <a href="https://www.npmjs.com/package/graphql">graphql.js</a> library.</p>



<p>However, Apollo Gateway doesn’t use graphql.js to execute a GraphQL request; instead, it executes a “query plan”, coordinating smaller requests to your subgraph services and assembling them into a single response. The Gateway executor has a few phases:</p>



<ul class="wp-block-list"><li>Validation</li><li>Planning</li><li>Execution</li><li>Fetching</li><li>Postprocessing</li></ul>



<p>Apollo Gateway now instruments these phases as spans in an OTel trace. Combined with HTTP instrumentation, which propagates the trace ID as headers in requests to subgraphs, we can now connect the gateway query planning and execution to the actual GraphQL field resolution work in your subgraph services.</p>



<p>Check out our <a href="https://www.apollographql.com/docs/federation/opentelemetry/#1-install-required-libraries">documentation on setting up OpenTelemetry</a> in your Apollo Gateway and Apollo Server apps.</p>



<p>Even if you’re using GraphQL framework other than Apollo Server or a language other than JavaScript, you can still use OTel to instrument your application. There are OTel instrumentation libraries for many other languages and frameworks, and <a href="https://opentelemetry.io/registry/?s=graphql&amp;component=&amp;language=">GraphQL-specific OTel support</a> is small but growing.</p>



<h2 class="wp-block-heading"><a href="#opentelemetry-in-your-infrastructure" aria-hidden="true" class="aal_anchor" id="opentelemetry-in-your-infrastructure"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>OpenTelemetry in your Infrastructure</h2>



<p>Instrumenting a request is cool, but it’s not very useful on its own. You can export traces into many different systems to view, inspect, or search traces.</p>



<p>The open-source projects Zipkin and Prometheus both support OpenTelemetry. Here’s an example of a federated GraphQL request in Zipkin.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="567" src="https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-23-at-9.55.49-AM-1024x567.png" alt="" class="wp-image-8205" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-23-at-9.55.49-AM-1024x567.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-23-at-9.55.49-AM-300x166.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-23-at-9.55.49-AM-768x425.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-23-at-9.55.49-AM-1536x850.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-23-at-9.55.49-AM-2048x1134.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-23-at-9.55.49-AM-1200x664.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-23-at-9.55.49-AM-1980x1096.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>A screenshot of a trace in the Zipkin web UI, showing spans for the gateway and multiple subgraphs.</figcaption></figure>



<p>The OpenTelemetry project has a number of exporters for various Application Performance Monitoring (APM) tools, including SaaS products like Datadog and Honeycomb, or cloud provider solutions like AWS X-Ray. You can find a complete list in the <a href="https://opentelemetry.io/registry/?s=&amp;component=exporter&amp;language=">OpenTelemetry Registry</a>.</p>



<h2 class="wp-block-heading"><a href="#opentelemetry-doesnt-replace-apollo-tracing" aria-hidden="true" class="aal_anchor" id="opentelemetry-doesnt-replace-apollo-tracing"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>OpenTelemetry doesn’t replace Apollo Tracing</h2>



<p>OpenTelemetry is great at recording what happened, but it doesn’t tell you much about what <em>could</em> happen. Apollo Studio uses the declarative nature of GraphQL to help you catch potential errors before they happen. Consider this GraphQL operation:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">query ProductsPage($categoryId: ID!) {
  products(category: $categoryId) {
    nodes {
      sku
      price
      reviews { # could return null
        nodes {
          id
          body
          rating
          author {
            name
            photoUrl 
          }
        }
      }
    }
  }
}</code></pre>



<p>If the <code>Product.reviews</code> field returns null, then the GraphQL executor won’t run resolvers for any of the fields nested inside that selection like <code>Review.id</code>, <code>Review.body</code>, or <code>Author.name</code>. OTel instrumentation won’t record any spans, so you’ll have no data about those fields.</p>



<p>However, if you remove or change the <code>Author.name</code> field, you could break all the clients that include that field in their operations.</p>



<p>We designed <a href="https://www.apollographql.com/docs/federation/metrics/">Apollo Federated Tracing</a> to collect field usage regardless of what actually happens (or doesn’t happen!) in your services. Our tracing data powers the <a href="https://www.apollographql.com/docs/studio/schema-checks/">Schema Checks</a> feature, alerting you of potentially breaking changes and giving you confidence as you evolve your API.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="638" src="https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.53.37-AM-1024x638.png" alt="" class="wp-image-8207" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.53.37-AM-1024x638.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.53.37-AM-300x187.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.53.37-AM-768x478.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.53.37-AM-1536x957.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.53.37-AM-2048x1276.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.53.37-AM-1200x748.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.53.37-AM-1980x1233.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>A screenshot of a failed check in Apollo Studio.</figcaption></figure>



<p>Apollo Studio also knows schema-related information like the <code>@deprecated</code> directive, so we can help you understand how clients are using deprecated fields.</p>



<figure class="wp-block-image size-large is-resized"><img loading="lazy" decoding="async" src="https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.50.03-AM-1024x210.png" alt="" class="wp-image-8209" width="610" height="125" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.50.03-AM-1024x210.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.50.03-AM-300x62.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.50.03-AM-768x158.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.50.03-AM-1536x316.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.50.03-AM-1200x247.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.50.03-AM.png 1732w" sizes="auto, (max-width: 610px) 100vw, 610px" /><figcaption>A screenshot of deprecation information in Apollo Studio.</figcaption></figure>



<p>It’s possible to cross-reference OTel traces and Apollo Studio traces by customizing the <a href="https://www.apollographql.com/docs/apollo-server/api/plugin/usage-reporting/">Usage Reporting plugin</a> in Apollo Server. By passing header values in trace sent to Studio that align with attributes on your OTel spans, you can jump between Studio and your OTel observability tooling to get a complete picture of a request.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="572" src="https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.52.54-AM-1024x572.png" alt="" class="wp-image-8211" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.52.54-AM-1024x572.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.52.54-AM-300x168.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.52.54-AM-768x429.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.52.54-AM-1536x858.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.52.54-AM-2048x1144.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.52.54-AM-1200x670.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-22-at-10.52.54-AM-1980x1106.png 1980w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /><figcaption>A screenshot of a trace in Apollo Studio with metadata you can use to associate this request with an OpenTelemetry trace.</figcaption></figure>



<h2 class="wp-block-heading"><a href="#wrapping-up" aria-hidden="true" class="aal_anchor" id="wrapping-up"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Wrapping Up</h2>



<p>OpenTelemetry is a fantastic open-source project and we’re excited to participate in the growing ecosystem. Combined with Apollo Studio, OpenTelemetry gives you a clear picture of your running systems, helping you debug, optimize, and evolve your federated graphs.</p>



<p>Check out the <a href="https://opentelemetry.io/docs/">OpenTelemetry documentation</a> and our <a href="https://www.apollographql.com/docs/federation/opentelemetry/">documentation on instrumenting federated graphs</a>.</p>


Introducing Open Telemetry for Apollo Federation


<h1 class="wp-block-heading"></h1>



<p>Two weeks ago, we hosted a<a href="https://www.apollographql.com/events/tech-talk/from-schema-stitching-to-federation-expedias-journey/"> webinar with Shane Myrick</a>, Senior Software Developer at Expedia Group entitled, “From Schema Stitching to Federation: Expedia’s Journey.” Shane’s talk covered Expedia’s motivation for adopting GraphQL and why they needed a distributed approach for managing their graph.&nbsp;</p>



<p>Prior to adopting GraphQL, the Expedia Group faced the challenge of delivering a wide array of travel experiences across a growing number of platforms and clients. Expedia adopted GraphQL as a way to simplify the connection layer between their backend capabilities and front-end clients. The graph provides a single point for clients to connect to and for service teams to expose to clients. Adopting the graph helped Expedia reduce the friction and the number of connections and coordination points across their boundary layers. They also saw benefits from adopting a strongly typed language and the performance benefits of adopting a declarative language that allows clients to request just the data they need. Lastly, they saw benefits in being able to extend and merge common types.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="543" src="https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6433ea44846ed12bb2-1024x543.png" alt="" class="wp-image-22924" srcset="https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6433ea44846ed12bb2-1024x543.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6433ea44846ed12bb2-300x159.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6433ea44846ed12bb2-768x407.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6433ea44846ed12bb2-1200x637.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6433ea44846ed12bb2.png 1276w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p><em>Building a graph across Expedia’s suite of travel products</em></p>



<p><strong>Scaling their graph with schema stitching</strong></p>



<p>As Expedia began to add more capabilities to their graph, they were concerned about it becoming a single point of failure and preventing conflicts as the number of contributors to their graph increased.</p>



<p>A core requirement was that they wanted to have one schema and one endpoint for their clients while allowing individual teams to own their services and update those services on their cadence. Expedia started using a gateway as a layer between their GraphQL services and their clients to achieve this. They started off using schema stitching as a way to merge types.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="534" src="https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6482536c5e195d99f-1024x534.png" alt="" class="wp-image-22929" srcset="https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6482536c5e195d99f-1024x534.png 1024w, https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6482536c5e195d99f-300x157.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6482536c5e195d99f-768x401.png 768w, https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6482536c5e195d99f-1200x626.png 1200w, https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase6482536c5e195d99f.png 1276w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p><em>Using a gateway to provide a single endpoint for developers across services</em></p>



<p>However, one downside of schema stitching is that Expedia needed to write a significant amount of gateway code to link types across different services. Shane walked through an example of how Expedia wrote code in their gateway to extend a type from their property service to include another type from their reviews service so that clients could query reviews by property. This code enabled the gateway to understand what types existed in different services and merged and extended the schema.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="894" height="728" src="https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase64d41caef3915787fa.png" alt="" class="wp-image-22931" srcset="https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase64d41caef3915787fa.png 894w, https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase64d41caef3915787fa-300x244.png 300w, https://wp.apollographql.com/wp-content/uploads/2023/11/pngbase64d41caef3915787fa-768x625.png 768w" sizes="auto, (max-width: 894px) 100vw, 894px" /></figure>



<p><em>Writing custom stitching code in the gateway.</em></p>



<p><strong>Challenges emerge with schema stitching</strong></p>



<p>As they introduced more stitching code in their gateway, challenges emerged. Their gateway code was becoming more complex, and there was no way to determine the “true schema” without running the gateway. Schema changes required a change to the underlying service and changes to the gateway code and a redeploy of all gateways. This complexity started to cause issues with managing their infrastructure. Additionally, Expedia began to be concerned about preventing conflicts when managing updates to their gateway code.</p>



<p><strong>Moving to Apollo Federation for their graph architecture</strong></p>



<p>When Apollo Federation was <a href="https://www.apollographql.com/blog/announcement/apollo-federation-f260cf525d21/">announced</a> in 2019, Expedia began investigating it as an alternative to schema stitching. They liked that<a href="https://www.apollographql.com/docs/federation/"> Federation</a> was published as an open-source <a href="https://www.apollographql.com/docs/federation/federation-spec/">specification</a> and its declarative, directive-based approach to merging types. Federation’s support for all GraphQL servers was compelling as Expedia had invested a lot in Kotlin and even open-sourced their own<a href="https://github.com/ExpediaGroup/graphql-kotlin"> GraphQL Kotlin</a> server.</p>



<p>With Federation, Expedia could use GraphQL directives to extend services without writing any custom gateway code. They did have to write resolver code in the underlying service to extend the type, but this was easier than the stitching approach as each team could own the evolution of its service.</p>



<p>Expedia saw the following benefits from adopting federation:</p>



<ol class="wp-block-list">
<li>Standardized the implementation as developers could follow the declarative approach to writing schemas.&nbsp;</li>



<li>Able to do offline composition and validation of the schema without spinning up a gateway.&nbsp;</li>



<li>Changed the coordination across teams to review gateway code to have a more strategic conversation about the schema architecture and design. The federated approach made reviewing changes to the schema easier as people reviewed the schema files vs. reviewing many lines of code.</li>
</ol>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="559" src="https://wp.apollographql.com/wp-content/uploads/2021/07/image-11-1024x559.png" alt="image.png" class="wp-image-8113" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/image-11-1024x559.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-11-300x164.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-11-768x420.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-11-1200x655.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-11.png 1276w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p> <em>Example of service level resolver code to extend a type across services</em></p>



<p><strong>Making the switch</strong></p>



<p>To safely migrate from stitching to Federation, Expedia first worked with the individual service teams to add the necessary federated directives, schemas, and resolver code to their GraphQL servers. Then Expedia set up two separate Apollo servers: one using schema stitching and one set up for Apollo Federation. They set up two variants in Apollo Studio’s schema registry to reflect the two different setups. They used a traffic router in front of the gateways to route traffic between the two graphs, eventually ramping up to a 50/50 split between the stitching and federated gateways.</p>



<p><strong>Benefits from moving from schema stitching to federation</strong></p>



<p>By running schema stitching versus Apollo Federation as an A/B test, Expedia was able to quantify the impact of moving to Federation, and they were pleased to see some immediate benefits. First, the federated implementation improved gateway processing latency which improved application performance compared to schema stitching. As Shane explained, “With Federation, we saw a reduced latency compared to schema stitching. Because there was a reduced latency, we were able to reduce our compute quite significantly by about 50%” Lastly, Expedia was able to delete many lines of gateway code which simplified their gateway deployments. Now, they can use almost a stock version of the gateway, making it easy for them to scale the gateway across their many brands since they no longer have much custom code in the gateway.</p>



<p><strong>Key takeaways from moving to Federation</strong></p>



<p>After moving to Federation, Shane says Expedia solved key customer and client problems by providing a single endpoint while ensuring that the service teams could independently deploy their changes. They also were able to reduce the potential impact of the gateway going down. They could remove the friction of having to work with multiple code bases to modify the schema. Additionally, they found the declarative approach of the Federation was more straightforward, which made it easier for teams to understand what’s happening and see the overall architecture, which elevated the discussions around the graph and reduced the coordination and complexity of scaling the graph.</p>



<p>To learn more about how Expedia’s journey from Schema Stitching to Federation, you can watch Shane’s talk<a href="https://www.apollographql.com/events/tech-talk/from-schema-stitching-to-federation-expedias-journey/"> on-demand</a> now.&nbsp; If you are looking to move from stitching to Apollo Federation, we’ve built a <a href="https://www.apollographql.com/docs/federation/migrating-from-stitching/">migration guide</a>.</p>


Moving from Schema Stitching to Federation: How Expedia improved performance


<p>I&#8217;ve been helping companies develop their graph using Apollo Federation for over two years now, and it&#8217;s amazing to see all the different applications they&#8217;ve enabled. </p>



<p>In developing one graph, companies often struggle to define a process for effectively governing changes to the federated schema. Some companies use a Google doc, while others use a blank piece of paper to plan out a new schema change. Regardless, there is always <em>some</em> medium used as a &#8220;template&#8221; for the desired governance process. In my experience, these primitive mediums always come with unnecessary challenges, whether it&#8217;s an electronic document that doesn&#8217;t have the context to the subgraph schemas or a monorepo that requires starting up all other services to plan a schema change.</p>



<p>We need a better way to design schema changes in a federated GraphQL architecture — one where we can <strong>understand our graphs composition at design time instead of the implementation phase</strong>. You shouldn&#8217;t have to write any code when planning a schema design; you should change be able to change the schema directly.</p>



<p>For this reason, we built Apollo Workbench: a better way to design your federated graph — whether you have an existing graph (monolith, BFF, schema stitched), you&#8217;re migrating to Apollo Federation, or you&#8217;re just getting started.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="576" src="https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-19-at-10.23.50-AM-1024x576.png" alt="" class="wp-image-8078" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-19-at-10.23.50-AM-1024x576.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-19-at-10.23.50-AM-300x169.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-19-at-10.23.50-AM-768x432.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-19-at-10.23.50-AM-1536x864.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-19-at-10.23.50-AM-1200x675.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/Screen-Shot-2021-07-19-at-10.23.50-AM.png 1920w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>Apollo Workbench is a tool built from experience working with our customers as they needed help designing their graphs. It dramatically reduces the feedback loop time when planning our changes to your graph. Specifically, Workbench helps you build faster with:</p>



<ul class="wp-block-list"><li>Composition Errors &#8211; For checking your design as you go</li><li>Query Explain &#8211; Understanding how a query will execute based on its generated query plan</li><li>Mocking your designs &#8211; This considerably improves the DX for client developers by enabling them to build directly against a locally mocked federated graph in development instead of having to spin up all the backing services or point to a production endpoint</li></ul>



<p>Let’s take a closer look at each.</p>



<h2 class="wp-block-heading"><a href="#composition-errors-checking-your-design" aria-hidden="true" class="aal_anchor" id="composition-errors-checking-your-design"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Composition Errors &#8211; Checking your design</h2>



<p>While working with companies on building their graph, the most common problem I saw was teams designing a schema change that led to some composition errors. After planning the design change in some electronic document, everyone would agree on the changes so the work would begin. Teams would implement the changes, but when the developer starts up the <code>ApolloGateway</code> instance, it wouldn&#8217;t be uncommon to find that it doesn&#8217;t start and that it has composition errors:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="310" src="https://wp.apollographql.com/wp-content/uploads/2021/07/image-3-1024x310.png" alt="carbon (3).png" class="wp-image-8062" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/image-3-1024x310.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-3-300x91.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-3-768x233.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-3-1536x465.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-3-1200x363.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-3-1980x599.png 1980w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-3.png 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>Other teams plan their design changes around a monorepo structure. The benefit here is that they could merely start everything and understand composition errors upfront, thereby improving the feedback loop. The challenge here arises when creating a new subgraph with a lot of <em>copypasta</em> throughout the project.</p>



<p>Today, Apollo Workbench enables you to work with your subgraph schemas directly, with any composition errors displayed prominently in the VS Code Problems Panel:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="575" src="https://wp.apollographql.com/wp-content/uploads/2021/07/image-4-1024x575.png" alt="Screen Shot 2021-07-14 at 9.51.01 AM.png" class="wp-image-8064" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/image-4-1024x575.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-4-300x169.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-4-768x432.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-4-1200x674.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-4.png 1276w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>This is great because now we can understand our design&#8217;s overall composition without starting anything up or writing any code. It also enables more people to be involved in the process since you&#8217;re just working with the schema directly. There is also IntelliSense for a composed graph where available types to extend are displayed (along with the owning service).</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="575" src="https://wp.apollographql.com/wp-content/uploads/2021/07/image-5-1024x575.png" alt="Screen Shot 2021-07-14 at 10.21.08 AM.png" class="wp-image-8066" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/image-5-1024x575.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-5-300x169.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-5-768x432.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-5-1200x674.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-5.png 1276w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>Suppose you&#8217;re using Apollo Studio and have integrated with the schema registry using Rover. In that case, you can log in to Apollo Workbench with <a href="https://studio.apollographql.com/user-settings">your user API key from your Personal Settings in Apollo Studio</a>. Then you can create designs from your graphs in Apollo Studio:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1920" height="1000" src="https://wp.apollographql.com/wp-content/uploads/2021/07/out-2.gif" alt="Logging into workbench" class="wp-image-8087"/></figure>



<h2 class="wp-block-heading"><a href="#query-explain" aria-hidden="true" class="aal_anchor" id="query-explain"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Query <code>EXPLAIN</code></h2>



<p>One of Apollo Federation&#8217;s significant benefits is understanding precisely how any given GraphQL operation will execute across your graph. This understanding comes in the form of a query plan generated for each unique operation. I like to think of the query plan as <code>EXPLAIN</code> for GraphQL queries. As teams design changes to their graph, they may need to contextualize a change to a GraphQL operation; this could be from a new set of functionality or a schema change that impacts operations currently running in Production.</p>



<p>With Apollo Workbench, you can add an operation to any design and view the query plan for any composing design:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1920" height="1000" src="https://wp.apollographql.com/wp-content/uploads/2021/07/out-3.gif" alt="" class="wp-image-8089"/></figure>



<p>Query <code>EXPLAIN</code> provides us with instant feedback on how a design might impact some existing operations. We all want performant queries, right? When you&#8217;re tweaking a design, it&#8217;s a great idea to start by looking at the query plan first and understanding how it changes with the tweaks you make.</p>



<p>If you&#8217;re using Apollo Studio and logged into Apollo Workbench, you can also click on a graph to load the operations from that graph variant. Then you can pull that operation into your design and see how it would execute:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1920" height="1000" src="https://wp.apollographql.com/wp-content/uploads/2021/07/out-4.gif" alt="Apollo Workbench Operations with Apollo Studio" class="wp-image-8095"/></figure>



<h2 class="wp-block-heading"><a href="#mocking-your-design" aria-hidden="true" class="aal_anchor" id="mocking-your-design"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Mocking your design</h2>



<p>Once you&#8217;ve created a design and you&#8217;re ready for the next steps, what do you do? A lot of companies explore some strategies around mocking to enable teams to develop independently. Client teams typically have some tooling to generate types, and they&#8217;ll want to do that for the new schema without waiting for the server team to spin something up. Apollo Workbench provides a simple mocking engine that will generate a mocked graph for any design you create.</p>



<p>Press the play button, and a mocked server will run locally for each subgraph and the graph router (<code>ApolloGateway</code> instance). The router will default to port <code>4000</code>, and the subgraphs will start by default on port <code>4001</code> and increment from there:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1920" height="1000" src="https://wp.apollographql.com/wp-content/uploads/2021/07/out-5.gif" alt="Apollo Workbench Mocks" class="wp-image-8097"/></figure>



<p><em>Hint: there are settings available in the extension to change what port you want the mocks to run on:</em></p>



<pre class="wp-block-code"><code>&quot;apollo-workbench.gatewayPort&quot;: 5000,&lt;br&gt;&quot;apollo-workbench.startingServerPort&quot;: 5001</code></pre>



<p>With Apollo Workbench, anyone can run a design with mocked data locally. The extension also has <code>faker</code> integrated into it, and you can write your own custom mocks:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="641" src="https://wp.apollographql.com/wp-content/uploads/2021/07/image-10-1024x641.png" alt="Apollo Workbench Custom Mocks" class="wp-image-8076" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/image-10-1024x641.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-10-300x188.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-10-768x481.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-10-1200x751.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-10.png 1276w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p><em>Note: a workbench file contains everything in the design, including the code snippet for your custom mocks. <code>eval</code> is used for the <code>JavaScript</code> that you write and a project is managed in the extensions global storage which provides you with feedback if you have errors.</em><br><br>Now you have all the tools you need to plan your graph designs with a complete understanding of what will execute without any code. Apollo Workbench provides insight into the graph and enables you to work only with the subgraph schemas to understand extension points, composition errors, and query execution plans. Once you’re complete with a design, you can mock it locally and use <a href="https://studio.apollographql.com/sandbox/explorer">Apollo Sandbox</a> to explore your graph.</p>



<h2 class="wp-block-heading"><a href="#getting-started" aria-hidden="true" class="aal_anchor" id="getting-started"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started</h2>



<p>To get started with Apollo Workbench for your next graph design, <a href="https://apollographql.github.io/apollo-workbench-vscode/">check out the official docs for installation instructions.</a></p>



<p>Workbench works best when you can design all your changes from one centralized schema registry. If you haven’t already, I recommend you <a href="https://studio.apollographql.com/signup">sign up for an account with Apollo Studio</a> and <a href="https://www.apollographql.com/docs/studio/schema/cli-registration/">push your subgraph schemas into the registry</a> with Rover. Oh yeah and don’t forget, the schema registry is free on our community tier forever.</p>



<p>Happy coding!</p>


Apollo Workbench: A Better Way to Design Federated Graphs


<p>When we released Apollo Server 2 in 2018, our goal was to make it the best-in-class GraphQL server by integrating many of the most useful GraphQL libraries available at the time. However, for backward compatibility reasons, this meant that Apollo Server 2 continued to include the 2018 versions of these libraries three years later. Apollo Server 3.0.0 changes that with a modernized codebase designed to serve as a scalable foundation for Apollo Server users well into the future.</p>



<h3 class="wp-block-heading"><a href="#a-more-modern-more-flexible-apollo-server" aria-hidden="true" class="aal_anchor" id="a-more-modern-more-flexible-apollo-server"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>A more modern, more flexible Apollo Server</h3>



<p>The many hardcoded dependencies in Apollo Server 2 made it increasingly difficult over time to build the new features that our users needed most. Because of that, our main focus when designing the initial release of Apollo Server 3 was to make it more flexible by removing as many hardcoded dependencies as possible. At the same time, we also prioritized increasing extensibility so that any capabilities lost in removing dependencies could easily be added back in and, unlike in v2, be easily upgraded over time.</p>



<p>Because of the approach we took, you may notice that most of the changes in 3.0.0 are under-the-hood improvements rather than new features which build upon recent 2.x versions. But, while it’s not packed with new features quite yet, what 3.0.0 does provide is a new foundation that will allow us to vastly improve our feature delivery velocity in the coming months. Here’s a quick look at some of the new things you may notice in 3.0.0 and a little sneak peek of what’s coming to Apollo Server 3 in the near future:</p>



<h3 class="wp-block-heading"><a href="#new-in-3-0-0" aria-hidden="true" class="aal_anchor" id="new-in-3-0-0"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>New in 3.0.0</h3>



<p>One of the main things you’ll notice in 3.0.0 is that <a href="http://studio.apollographql.com/sandbox">Apollo Sandbox</a> is now suggested as the main tool for querying your server. Apollo Server 2 shipped with GraphQL Playground, but that project was <a href="https://github.com/graphql/graphql-playground/issues/1143">retired last year</a>. Instead of only supporting a single frontend, Apollo Server 3 has a “landing page” API. You can keep using the retired GraphQL Playground by adding a single line of code to your app, but the default landing page helps you and your users use the actively maintained Apollo Sandbox tool. Sandbox provides a number of UX improvements over GraphQL Playground like one-click query building, intelligent field and path search, and even more, which you can read about in our <a href="https://www.apollographql.com/blog/announcement/platform/apollo-sandbox-an-open-graphql-ide-for-local-development/">Sandbox announcement blog</a>.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="3698" height="2016" src="https://wp.apollographql.com/wp-content/uploads/2021/07/image-1.png" alt="image.png" class="wp-image-7989" srcset="https://wp.apollographql.com/wp-content/uploads/2021/07/image-1.png 3698w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-1-300x164.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-1-1024x558.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-1-768x419.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-1-1536x837.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-1-2048x1116.png 2048w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-1-1200x654.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/07/image-1-1980x1079.png 1980w" sizes="auto, (max-width: 3698px) 100vw, 3698px" /></figure>



<p>3.0.0 also includes a number of less visible changes which improve the UX and extensibility of Apollo Server:</p>



<ul class="wp-block-list"><li>Apollo Server 3 now supports the latest version of Fastify (v3) and Hapi. We’ve made it easier to understand what web framework versions are supported by using peer dependencies more consistently.</li><li>Apollo Server’s AWS Lambda and Google Cloud Functions integrations are now built on top of our Express integration rather than reimplementing a subset of its logic from scratch. This means we support new Lambda integrations such as Application Load Balancers, and it will be much easier for new Apollo Server functionality to work in Lambda and Cloud Functions without having to write the same code three times. Additionally, because it now uses Express internally, you can extend your Lambda or Cloud Functions server’s HTTP functionality via standard Express middleware by using the new <code>expressAppFromMiddleware</code> option to <code>createHandler.</code></li><li>Bad request errors are handled in a more consistent manner across integrations and consistently return HTTP responses with a 4xx status</li><li>We’ve dropped support for Node 8 and 10 (which are no longer in LTS), which lets the TypeScript compiler output more efficient code that takes advantage of newer Node features.</li><li>Apollo Server 2 supported releases of graphql-js dating back to 2017’s 0.12.0. Apollo Server 3 requires the more modern 15.3.0 release of graphql-js, allowing us to rely on the last four years of added functionality.</li><li>We’ve refreshed all of our documentation. For example, check out our <a href="https://www.apollographql.com/docs/apollo-server/integrations/middleware/">new page which directly compares the different “flavors” of Apollo Server and helps you decide which one to use</a>.</li></ul>



<h3 class="wp-block-heading"><a href="#whats-coming-next" aria-hidden="true" class="aal_anchor" id="whats-coming-next"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What’s coming next?</h3>



<p>Now that we’ve modernized the Apollo Server codebase, we’re in a great position to start making big improvements. Here’s some of what we’re working on next.</p>



<p><strong>Response-shape-based usage reporting</strong>. Currently, getting insights into your Apollo Server’s usage and performance in Apollo Studio requires creating a detailed execution trace of every operation. While this gives you a very complete and detailed understanding of what’s going on in your graph, it can have a performance impact. Additionally, not every language’s GraphQL library has all the hooks required to make these traces, so if your federated subgraph doesn’t use one of the supported libraries you won’t get as much clarity in Studio. In a future release of Apollo Server 3, we plan to implement “response-shape-based reporting”, which enables most of Studio’s features without detailed per-field execution traces. This will improve your graph’s performance and let you use any GraphQL server for your subgraph without loss of Studio functionality.</p>



<p><strong>Additional directive support to improve response latency</strong>. One of the disadvantages of the GraphQL response/request model is that the response is not returned to the clients until the entire request has finished processing. We are excited to get started on adding support for additional directives such as <code>@defer</code> which allow responses to return in multiple payloads, prioritizing the most important data first.</p>



<h3 class="wp-block-heading"><a href="#getting-started-with-apollo-server-3" aria-hidden="true" class="aal_anchor" id="getting-started-with-apollo-server-3"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Getting started with Apollo Server 3</h3>



<p>We’re excited to get Apollo Server 3 in the hands of our community, and we would love to hear what you think as you start to use it! If you’re starting from scratch, our <a href="https://www.apollographql.com/docs/apollo-server/getting-started/">getting started docs</a> will walk you through setting up Apollo Server for the first time, or, if you’re already using Apollo Server 2, our <a href="https://www.apollographql.com/docs/apollo-server/migration/">migration guide</a> will help you upgrade. If you’d like to leave us any feedback on Apollo Server 3, we encourage you to do so by reaching out on <a href="https://community.apollographql.com/">https://community.apollographql.com</a> or <a href="https://github.com/apollographql/apollo-server">GitHub</a>.</p>


Announcement