
<p>Apollo GraphOS now supports custom schema checks, a new feature that addresses API platform teams’ demand for enhanced schema governance capabilities. This functionality allows organizations to integrate their own business logic, security policies, and rules into Apollo&#8217;s existing schema check workflow, ensuring that every schema change adheres to company-specific standards. The result is a more robust, flexible, and secure approach to maintaining schema integrity, allowing platform teams to uphold organizational standards in an automated manner while adhering to stringent organizational requirements.</p>



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



<p>API governance encompasses the policies and standards that an engineering organization employs to secure, standardize, and maintain its APIs over time. Engineers utilize various methods to manage changes to their APIs, one of which involves centralizing a space where these policies can be enforced. Governance policies may cover non-functional requirements, like enforcing style guidelines and ensuring that all changes align with established standards, or more complex workflows, such as conducting automated testing and leveraging historical data to ensure backward compatibility.</p>



<p>GraphOS currently offers several tools that help automate API governance, including operation checks, schema linting, composition checks, and proposal checks. <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/checks#operations-checks">Operation checks</a> compare proposed schema changes against historical operations to verify whether the changes break any of your graph&#8217;s active clients. <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/linting">Schema linting</a> allows you to configure style guidelines and analyze proposed schema changes for violations of formatting rules. <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/proposals/configure#configure-schema-checks">Proposal checks</a> validate whether your proposed schema changes have matching and approved schema proposals, and finally, <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/delivery/contracts/create#run-contract-checks">downstream checks</a> ensure that proposed schema changes don’t break any downstream contract variants.</p>



<p>As organizations grow and APIs scale, there are going to be facets of governance that extend outside the realm of what is offered by GraphOS. Because of this, we built custom schema checks to offer a hook into the GraphOS schema check workflow to support the injection of custom business logic or rules. This allows users to implement their own checks and push results into GraphOS for viewing in Studio while maintaining a unified check workflow, acting as a safeguard within their continuous integration pipelines for schema modifications.</p>



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



<p>Custom schema checks require an HTTPS endpoint that is accessible over the public internet. We offer an <a href="https://github.com/apollosolutions/custom-check-examples/">example implementation</a> for using an open-source linter, graphql-eslint, to lint the subgraph schemas modified by the check request. This sample is set up as a <a href="https://www.netlify.com/platform/core/functions/">Netlify function</a> but could be adapted to run on any serverless architecture or containerized system.</p>



<p>After checking out the code and following the steps in the README to deploy it, we can enable it in Studio through the custom check configuration page. After that, we can test our integration with an empty payload by clicking the “Send test notification” button.</p>



<p><img loading="lazy" decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXehd-VSLdSR_OZrwz45lg6SrCzrFhXFWqk3p3zrWoK7UHaSyrSMx_NofzLLK3lv2VWJ8BASrQlvjilWz2bPXot46a4tyGY3QkH545hKAfADdpzJpQ_RmZsquTrh4ixK6lxhlpgCmYnyF2wfMTH1q_HNpYM?key=4rXqpQwA4wPdxVzCiNTZCg" width="624" height="231"></p>



<p>If everything looks good in the function logs, we can then run a schema check using the <a href="https://www.apollographql.com/docs/rover/commands/subgraphs#subgraph-check">rover CLI</a>, and our endpoint will be called.&nbsp;</p>



<p><img loading="lazy" decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfCrh2mn7VqyiPQFAfOt7DNjOemAoloWaVDCdIQfrZcc58j-mOs7GgR1qeAllY5hJ6xs9_OB2qKY7NZ2a0oaDpdmFY5tlqkqA5nTownCtu9tKRe8R4Zfe2PwFgKQ-T-OnQMZql46balKGyyhIeueQLeIMur?key=4rXqpQwA4wPdxVzCiNTZCg" width="624" height="305"></p>



<p>The schema information will be passed to our endpoint, which will lint the schema and return the results to GraphOS. These results from our custom check task will be stored and viewable in Studio.</p>



<p><img loading="lazy" decoding="async" src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdl2aDeG2Jt8a9ideekPxnipH8qTElM7O1abofJAfqnTMsHGjhAfoQ8KS4MfNN7smuQyrXZbqXabngEhSuCHkALw2L8Icj0bRb_Y3wOy1L2ETqcdSa0Ns8ibiiXRsoMWtDJrvgkdcG7KXskmgziWFjt3WPC?key=4rXqpQwA4wPdxVzCiNTZCg" width="624" height="333"></p>



<p>The architecture we recommend for a custom check worker consists of two main components: one to receive the payload and the second to execute the business logic.</p>



<p>The first component is responsible for receiving the <a href="https://www.apollographql.com/docs/graphos/platform/schema-management/checks/custom#webhook-format">webhook payload</a> containing the metadata of the check request. It places this information onto a worker queue and promptly responds with a 200 OK status. This response indicates to GraphOS that the check request has been received.</p>



<p>The second component retrieves check requests from the queue and executes the necessary business logic, such as downloading schemas, performing custom linting, or implementing other schema governance tasks, and then calls back to the GraphOS Platform API with the results of the custom check.</p>



<p>There is no need to perform a custom check synchronously because the state machine that manages schema check workflows will wait up to 10 minutes for the callback mutation to be received. If no callback is received, the custom check tasks will be marked as failed with a timeout.&nbsp;</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>With custom schema checks, API platform teams can integrate their own custom business logic, security policies, and governance rules into the schema check workflow. This feature improves an API governance posture by allowing organizations to enforce company-specific standards, automate schema validation, and maintain a unified, flexible workflow for schema modifications. Custom checks are now available in GA for GraphOS Enterprise plans.<br>If you want to enable the custom configuration for your graph, head to the “Checks” tab in GraphOS Studio → Configuration → Custom checks. Or, if you haven’t set up schema checks yet for your graph, check out the <a href="https://www.apollographql.com/docs/graphos/delivery/schema-checks">documentation</a> to get started.</p>


Enforce Flexible Governance in GraphOS using Custom Checks


<p>How confident are you that changes to your API won&#8217;t break any clients? Not having confidence in knowing what could break when you release changes to your graph can grind teams to a halt and cause all sorts of problems for clients consuming your graph.</p>



<p>In this article, we&#8217;ll look at how adopting a DevOps culture can help you evolve your graph faster, improve communication around your data graph, as well as the role Apollo plays in achieving a DevOps workflow for your data graph.</p>



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



<p>DevOps is a set of practices that combines software development and IT operations. It aims to shorten the systems development life cycle and provide continuous delivery with high software quality. DevOps shares a lot of principles with Agile software development.</p>



<p>Implementing DevOps is not just about tools; it is also about how people work and the processes they use. DevOps is about unifying the engineering teams responsible for running an application or service in production.</p>



<p>Ideally, one team manages all aspects of the service, including security and testing functions. In larger organizations, there may still be some functional specialization. Still, it remains critical that the process and communication focus on the end-to-end delivery of the entire service.</p>



<h2 class="wp-block-heading"><a href="#how-does-devops-help-me-ship-more-quickly-and-reliably" aria-hidden="true" class="aal_anchor" id="how-does-devops-help-me-ship-more-quickly-and-reliably"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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 DevOps help me ship more quickly and reliably?</h2>



<p>One of the major benefits of adopting GraphQL is the ability to gradually evolve your API over time instead of being locked into versioning and large releases. However, as with all things, there&#8217;s an associated cost. Because it&#8217;s not a large coordinated effort to release changes to a graph, it&#8217;s pretty easy to change or remove a type or field that will break one or more clients.</p>



<p>Communication between everyone who consumes and maintains the graph can break down as your graph grows. To consistently meet clients&#8217; needs, we need to evolve a graph gradually, but we want to be able to do so quickly and reliably.</p>



<p>By adopting a DevOps culture and blending operations with development, we can greatly improve communication around a data graph. Improved communication leads to shorter feedback loops, fewer errors, and faster deployments.</p>



<p>Under a DevOps model, development and operations are no longer “siloed.” Instead, graph usage data is used in the build, test, and planning phases of a graph&#8217;s lifecycle.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="317" src="https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-7-1024x317.png" alt="" class="wp-image-7712" srcset="https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-7-1024x317.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-7-300x93.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-7-768x238.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-7-1536x475.png 1536w, https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-7-1200x371.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-7.png 1564w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<h2 class="wp-block-heading"><a href="#how-does-apollo-help-me-with-devops" aria-hidden="true" class="aal_anchor" id="how-does-apollo-help-me-with-devops"><svg aria-hidden="true" class="aal_svg" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 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 Apollo help me with DevOps?</h2>



<p>At Apollo, we believe that data graphs are the epicenter of communication for teams and companies that adopt GraphQL. It&#8217;s why we&#8217;ve invested so heavily in creating the tooling needed to set up DevOps best practices for GraphQL APIs. Apollo provides a platform on top of a schema registry that works together to help you at each stage in the DevOps lifecycle.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="432" src="https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-6-1024x432.png" alt="" class="wp-image-7715" srcset="https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-6-1024x432.png 1024w, https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-6-300x127.png 300w, https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-6-768x324.png 768w, https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-6-1200x506.png 1200w, https://wp.apollographql.com/wp-content/uploads/2021/06/build-test-release-6.png 1432w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



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



<p>Apollo offers various tools to help you develop your API faster. From Apollo Explorer, a <a href="https://github.com/apollographql">cloud-based GraphQL IDE</a> specifically tailored to GraphQL developers, to <a href="https://github.com/apollographql">numerous open-source libraries</a>, Apollo is deeply invested in helping developers build data graphs faster.</p>



<p>When developing locally, you can <a href="https://www.apollographql.com/blog/announcement/platform/apollo-studio-a-graphql-ide-for-every-environment/">use development graphs</a>, which enables you to use all of Apollo Explorer’s powerful features (like intelligent search and variable extraction) with your locally running GraphQL server.</p>



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



<p><a href="https://www.apollographql.com/docs/studio/schema-checks/">Schema checks in Apollo Studio</a> help you collaborate on your graph with confidence. Checks validate your schema changes against historical operations to ensure changes will not break existing clients.</p>



<p>For federated graphs, we also understand how important it is to have visibility of your graph’s composition. That&#8217;s why <a href="https://www.apollographql.com/blog/announcement/build-checks-webhooks-apollo-studio/">we&#8217;ve introduced build checks and webhooks</a> to help you better understand the impact of schema changes, update your data graph faster, and allow more teams to contribute to the graph safely.</p>



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



<p>Our new <a href="https://www.apollographql.com/docs/rover/">Rover CLI</a> helps you safely publish and fetch GraphQL schemas (monolithic and federated) from the Apollo schema registry. It is the successor to the Apollo CLI as the primary command-line tool for working with graphs.</p>



<p>When it comes to deploying federated graphs, Apollo provides <a href="https://www.apollographql.com/docs/federation/managed-federation/overview/">managed federation</a>. With managed federation, your&nbsp;gateway&nbsp;is no longer responsible for fetching schemas from your&nbsp;subgraphs&nbsp;on startup. Instead, your subgraphs push their schemas to the Apollo schema registry, verifying that they successfully&nbsp;compose&nbsp;into a federated schema. Studio then updates your graph&#8217;s latest configuration on composition success and makes your changes available to your gateway.</p>



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



<p><a href="https://www.apollographql.com/studio/observe/">Apollo Studio&#8217;s observability features</a> give you insight into every way your graph is being used and helps you find what’s wrong, what’s new, or what’s recently changed and take action.</p>



<p><strong>Tracing &#8211;</strong> Automatically trace your operation’s resolvers, even across federated services, with no added configuration in Apollo Server. Visualize how your resolvers execute, identify bottlenecks, track headers and variables associated with your requests, and more.</p>



<p><strong>Clients &#8211;</strong> <a href="https://www.apollographql.com/blog/announcement/platform/how-apollo-studio-client-awareness-improved-our-lives/">See precisely which clients are querying your graph</a> and what operations they’re sending — track changes to operations, performance degradations, and error spikes across client versions.</p>



<p><strong>Deprecations &#8211;</strong> Studio’s field-level usage tracking tells you precisely which of your clients last used each of your schemas fields, giving you the confidence to deprecate fields and sunset them without breaking any active usage of your graph.</p>



<p>Aside from observability around graph performance, Apollo Studio also provides a history of your schema, daily reports, and <a href="https://www.apollographql.com/docs/studio/schema-change-integration/">schema change notifications</a> to help keep you and your team(s) informed.</p>



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



<p>With Apollo Studio, you can view everything about your graph in one place – what data types exist, their documentation and interrelationships, the services that implement them, who are using them, when they last changed, when they last changed, and explore your graph with Apollo Explorer.</p>



<p>When it comes to scaling beyond a single graph, <a href="https://marketplace.visualstudio.com/items?itemName=apollographql.apollo-workbench">Workbench</a> can help you design a federated graph from the comfort of your editor without changing code or running servers.</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>Adopting a DevOps culture provides your team(s) with the safety, trust, and agency needed to ship changes to your data graph quickly and reliably. Apollo provides an extensive platform that helps GraphQL API developers put DevOps best practices in place by providing CI/CD and observability for your graphs.</p>



<p>To get started with Apollo Studio, head to <a href="http://studio.apollographql.com/dev">studio.apollographql.com/dev</a>.</p>


GraphQL

Enforce Flexible Governance in GraphOS using Custom Checks

DevOps for GraphQL APIs – Build, Manage, and Scale the Graph

Stay in our orbit