Enhance customer experiences with Apollo GraphOS

Platform Engineering for APIs


<p>The traditional approach to microservices in Kubernetes requires duplicating application logic into YAML config files. This leads to information fragmentation, inconsistencies, and ultimately bugs. With GraphQL and Apollo Federation, you can reduce the amount of required config, prevent duplication, and have a better experience maintaining your API. In particular, Apollo Federation can:</p>



<ol class="wp-block-list">
<li>Prevent conflicting API routes, and give better visibility into the entire API.</li>



<li>Ensure that routing rules always match the application code.</li>



<li>Make microservice dependencies declarative, and avoid custom networking rules between services.</li>
</ol>



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



<p>The new Kubernetes Gateway API provides a lot of ergonomic improvements over the older Ingress, and puts more power in the hands of application developers to define their routes. While this is likely a good choice for a REST API, it can also lead to unexpected behavior.</p>



<p>Consider a backend team at a retail company who are implementing a new feature: allowing users to subscribe to a product they purchase on a regular basis. They might introduce an <code>HTTPRoute</code> rule that looks like this:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml">rules:
 - matches:
     - path:
         type: RegularExpression
         value: /user/[^/]+/subscription</code></pre>



<p>Unfortunately, they don&rsquo;t know that the accounts team has already registered the <em>same</em> route to fetch a user&rsquo;s membership (formerly called &ldquo;subscription&rdquo;)! When they roll out these changes, one of a few things could happen:</p>



<ul class="wp-block-list">
<li>The rule isn&rsquo;t applied because the older membership route takes precedence. This is likely the preferred outcome: it doesn&rsquo;t break <em>existing</em> features (and it&rsquo;s what <a href="https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRouteRule">the docs</a> suggest should happen), but it can lead to head-scratching on the developers&rsquo; part. Ultimately, they&rsquo;ll call in the platform team to figure out what&rsquo;s going on.</li>



<li>Or, the rule <em>is</em> applied because, as is the case with the popular gateway I was testing, the alphabetical order of namespaces is used to resolve conflicts <em>without</em> considering the age of the config. This is risky business: the new feature appears to be working fine, and could pass QA despite having introduced a production issue. From here, it&rsquo;s only a matter of time before the error reveals itself and someone gets paged to diagnose it.&nbsp;</li>
</ul>



<p>Neither outcome is great. Wouldn&rsquo;t it be better if the products team were informed of the problem before ever deploying anything? With Apollo Federation, that&rsquo;s exactly what happens.</p>



<p>First off, the developers can delete their entire <code>HTTPRoute</code>; with Federation, the same code which defines the GraphQL API of a microservice determines how routing can work. Whether locally or in CI for their pull request, the product team encounters an error when they try to build (aka &ldquo;compose&rdquo;) their new <code>subscription</code> field:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-">INVALID_FIELD_SHARING: Non-shareable field &quot;User.subscription&quot; is resolved
 from multiple subgraphs: it is resolved from subgraphs 
 &quot;products&quot; and &quot;users&quot; and defined as non-shareable in all of them</code></pre>



<p>Not only does CI fail on the conflict and prevent them from deploying something that could potentially break production, but it also tells them which other service they&rsquo;re conflicting with. These early show-stopping errors carve a much faster path to diagnosis: informing the developer what happened, and where they can go to fix it.&nbsp;</p>



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



<p>A lesson we learn time and time again is that there should be a single source of truth for data, and configuration is no different. With a traditional REST microservices setup, there are at least two sources of truth for routing.</p>



<p>First, the developer needs to define the route in their web framework of choice. For example, they might have this FastAPI route in a Python service:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-python">@app.get(&quot;/items/{item_id}&quot;)
async def read_item(item_id: int) -&gt; Item:
  return Item.load(item_id)</code></pre>



<p>Second, they need to redefine the route in Kubernetes config. They&rsquo;ll probably end up with something closely resembling the application code:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml">rules:
 - matches:
     - path:
         type: RegularExpression
         value: /items/\d+/</code></pre>



<p>This works fine&mdash;that is, until the application updates to use opaque string IDs (like UUIDs). If the developer forgets to check on the Kubernetes config, the route will stop working. You could leave it to your QA team or some careful code review to catch this, or you could remove the possibility of this error entirely.</p>



<p>With GraphQL and Apollo Federation, the routing information all flows from a single source in the code, so it can never be out of sync! When a developer updates their microservice, the standard CI/CD process propagates that change automatically to the router, with no manual checks required. Better yet, if that change would break downstream clients, tools like <a href="https://bit.ly/3TcpBaP">Apollo GraphOS</a> catch and stop the release in its tracks before it even rolls out to the QA environment. That means less back-and-forth, and more shipping!</p>



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



<p>Most of the time, the only pods that should communicate with a microservice are the API Gateway&rsquo;s pods. Security best practices tell us to lock down networking to only those interactions that are required. As a result, we&rsquo;ll usually start each new microservice with a <code>NetworkPolicy</code> that looks something like this:</p>



<pre class="wp-block-prismatic-blocks"><code class="language-yaml">apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
 name: microservice-network-policy
spec:
 podSelector: {}
 policyTypes:
   - Ingress
 ingress:
   - from:
       - namespaceSelector:
           matchLabels:
             name: infra
         podSelector:
           matchLabels:
             app: gateway</code></pre>



<p>Here we&rsquo;re denying all ingress traffic for all pods unless it comes from the API Gateway.</p>



<p>Sometimes, though, one microservice needs data from another. Achieving this typically involves a request to the platform, infrastructure, and/or security teams to add a new rule for communication between those services. Worse, that rule will probably have to be broad enough in scope that <em>any</em> traffic is now allowed between those services,<em> loosening security</em> more than required. This direct communication also <em>tightens the coupling</em> between the microservices, making them harder to change and more likely to break.</p>



<p>With Apollo Federation, services can set up their dependencies declaratively and let the router take care of the rest. In this example, the <code>totalCost</code> field requires a <em>different</em> service&rsquo;s <code>products</code> field (specifically, the <code>price</code> and <code>shipping</code> subfields).</p>



<pre class="wp-block-prismatic-blocks"><code class="language-graphql">type Order @key(fields: &quot;id&quot;) {
   id: ID!
   products: [Product] @external
   totalCost: Int @requires(fields: &quot;products { price shipping }&quot;)
}</code></pre>



<p>Not only does this microservice not need to directly communicate with another microservice, it doesn&rsquo;t care <em>which</em> service provides the data it needs. This decouples the services, freeing up teams to evolve their projects independently. This process also explicitly documents dependencies, so CI can prevent changes that would cause issues for other services.</p>



<p>Only the data that is necessary for particular request will flow between microservices, and <em>everything</em> comes through the router. This means there&rsquo;s a central place to monitor and manage traffic, and networking rules can be simplified and standardized. Because adding a new dependency is a simple code change, developers can submit fewer tickets to the platform and security teams and greatly reduce the risk of shipping broken code.</p>



<h2 class="wp-block-heading"><a href="#simplify-your-kubernetes-config-today" aria-hidden="true" class="aal_anchor" id="simplify-your-kubernetes-config-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>Simplify your Kubernetes config today</h2>



<p>Using GraphQL with Apollo Federation can save time for your platform, infrastructure, and backend development teams while improving the reliability and maintainability of your microservices. It does this by removing application logic from your Kubernetes config, enabling each team to focus on what matters. If you&rsquo;re interested in learning more about Apollo Federation, <a href="https://discord.gg/amVehrwMpJ">join our Discord server</a> and chat with us in the <code>#apollo-federation</code> channel. If you have any ideas for improving a microservice platform that we should check out next, we&rsquo;d love to hear about that too!</p>


Remove Application Logic from Kubernetes Config


<p>In today&#8217;s digital world, optimizing APIs for efficiency and real-time performance is crucial. Your applications need to keep evolving by introducing new features or capabilities over time. Many organizations utilize platform engineering teams to create a self-service developer portal with the goal of accelerating their developers velocity building these new features.&nbsp;&nbsp;</p>



<p>We&rsquo;ve seen a trend of platform engineering teams leveraging GraphQL to power their self-service platform; this has been a game changer for them. Instead of shipping updates to your self-service platform in the magnitude of weeks or months, we find our customers are shipping updates daily with some making multiple changes a day. GraphQL is transforming the API landscape, but why are teams choosing GraphQL as their standard instead of other technologies like REST? I&rsquo;ll give you a hint, it&rsquo;s about the developer experience but let&rsquo;s explore that more.</p>



<h1 class="wp-block-heading"><a href="#what-is-graphql" aria-hidden="true" class="aal_anchor" id="what-is-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>What is GraphQL?</h1>



<p>Before we explore the benefits of GraphQL, let&#8217;s briefly understand what it is. GraphQL is a specification and query language that defines how to query, mutate, and subscribe to data within a graph. In simpler terms, it allows you to fetch data (queries), make changes or create data (mutations), and receive real-time updates (subscriptions) by specifying the exact fields you need. Unlike traditional REST APIs, GraphQL empowers the client developers to build features faster.</p>



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



<p>One common question that arises is whether GraphQL replaces REST APIs entirely. The answer is no; GraphQL and REST can coexist harmoniously. In fact, many organizations leverage GraphQL to enhance their existing REST APIs. GraphQL can be implemented as a layer on top of REST, providing flexibility and improved developer experience. It also uses POST and GET requests, making it adaptable to various scenarios like CDN caching.</p>



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



<p>Many platform engineering teams have chosen GraphQL to power their self-service developer portal because of the benefits they immediately get:</p>



<ul class="wp-block-list">
<li><strong>Clear Observability</strong>: Implementing GraphQL over your APIs offers a unified view of usage and performance, providing a single source of truth to evaluate the effectiveness of your API investments.</li>



<li><strong>Accelerated Application Development</strong>: With GraphQL, developers are no longer hindered by the need to create new API endpoints. Anyone who can write a GraphQL query can add or modify fields to support new features and functionalities.</li>



<li><strong>Expanded Capabilities</strong>: GraphQL provides access to advanced features like real-time data with subscriptions and upcoming enhancements such as the <code>@defer</code> directive, which optimizes query execution.</li>



<li><strong>Improved User Experience</strong>: Ultimately, GraphQL&#8217;s goal is to create delightful experiences for users. By simplifying data access for client developers, it streamlines development and leads to better user interfaces.</li>
</ul>



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



<p>API architectures have been evolving for decades and we&rsquo;ve seen a shift towards architectures that empower development teams to build in a &ldquo;self-service&rdquo; way. They have a portal to discover the data they need and resources that help them deploy newly created capabilities based on the architecture they decided. Platform engineering is a more recent trend with the goal of automating the infrastructure and providing an internal delightful developer experience. And platform engineering is not going away, here is what Garnter said in their recent post <em>&nbsp;</em><a href="https://www.gartner.com/en/articles/what-is-platform-engineering"><em>What is Platform Engineering</em></a><em>?:</em></p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p>By 2026, 80% of large software engineering organizations will establish platform engineering teams as internal providers of reusable services, components and tools for application delivery. Platform engineering will ultimately solve the central problem of cooperation between software developers and operators.</p>



<p>&#8211; <em>Gartner, </em><a href="https://www.gartner.com/en/articles/what-is-platform-engineering"><em>What is Platform Engineering</em></a><em>?</em></p>
</blockquote>



<p>When you only have a single web application, it&rsquo;s hard to fully grasp how that might grow. As your project gains users and success, you start to get feature requests from end-users or internally. As you build your application, the day comes where you embark on your journey to build a mobile application to bring some of those web capabilities to your users phones. What do you do? Does the new mobile application use the web application&rsquo;s API? Do you create a new API for the mobile app that uses the web application&rsquo;s API in a backend-for-frontend (BFF) pattern? What happens when we need to build that next thing on top of large language models (LLM) or for that paradigm like voice (like Amazon Alexa)? <em><strong>When does it stop?</strong></em></p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="553" src="https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2024-01-04-at-10.08.02-AM-1024x553.png" alt="" class="wp-image-23085" srcset="https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2024-01-04-at-10.08.02-AM-1024x553.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2024-01-04-at-10.08.02-AM-300x162.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2024-01-04-at-10.08.02-AM-768x414.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2024-01-04-at-10.08.02-AM-1200x647.png 1200w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2024-01-04-at-10.08.02-AM.png 1264w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<p>As organizations grow, they face challenges in managing and connecting these diverse APIs efficiently. Developers become responsible for figuring out how to access the data they need to build that new feature. Adding GraphQL as a layer into your architecture can simplify the personas of your organization into consumers and contributors of your platform. A simple way to integrate new capabilities in your graph so that any of your client developers can use those new capabilities in their client applications:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="536" height="597" src="https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2024-01-04-at-10.30.35-AM.png" alt="" class="wp-image-23087" srcset="https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2024-01-04-at-10.30.35-AM.png 536w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2024-01-04-at-10.30.35-AM-269x300.png 269w" sizes="auto, (max-width: 536px) 100vw, 536px" /></figure>



<p>To address these challenges, large enterprises like Wayfair, Intuit, T-Mobile, and US Bank have successfully adopted an architecture that includes the Apollo Router. This router sits in front of multiple GraphQL APIs and orchestrates requests across the entire business. It combines these APIs into what is called the supergraph, enabling intelligent query execution. The router provides multiple benefits:</p>



<ul class="wp-block-list">
<li><strong>Language Agnostic</strong>: Apollo Federation supports over 40 different programming languages and frameworks, allowing flexibility in developing GraphQL APIs.</li>



<li><strong>Scalability</strong>: Adding more GraphQL servers to the infrastructure becomes straightforward, making GraphQL accessible to everyone.</li>



<li><strong>Observability</strong>: The router offers comprehensive observability, allowing organizations to track usage down to individual fields and operations.</li>



<li><strong>Real-time Support</strong>: GraphQL subscriptions and other real-time features are seamlessly integrated, simplifying the implementation of real-time experiences.</li>



<li><strong>Efficient Query Execution</strong>: The router optimizes query execution by creating query plans, enabling caching, and supporting advanced features like <code>@defer</code></li>



<li><strong>Security</strong>: Security controls are built into the router, ensuring a secure GraphQL infrastructure that benefits all client developers.</li>
</ul>



<h1 class="wp-block-heading"><a href="#advanced-graphql-features" aria-hidden="true" class="aal_anchor" id="advanced-graphql-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>Advanced GraphQL Features</h1>



<p>By using GraphQL for your platform, you instantly get access to new features released into the GraphQL spec. <code>@defer</code> is a new directive being added to the spec and provides a new way to progressively load data that gives a lot of power to your application developers. The <a href="https://github.com/graphql/graphql-wg">GraphQL working group</a> is very active and the community is always proposing new ideas that benefit everyone using GraphQL. </p>



<p>Some items that don&#8217;t make the spec go on to become established patterns in GraphQL. A good example is&nbsp;<a href="https://www.apollographql.com/docs/router/configuration/persisted-queries">Persisted Queries</a>. GraphQL has always supported GET requests but persisted queries doesn&#8217;t just url encode the GraphQL operation. They allow organizations to give an ID for every operation and enable requests to be smaller in size. Most teams also use this persisted query list to lock down production deployments to serve only pre-registered queries, enhancing security and control.</p>



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



<p>GraphQL&#8217;s upcoming <code>@defer</code> directive offers a solution for progressively loading data in queries. This directive allows client developers to indicate that certain data can be incrementally loaded when needed, improving the user experience by reducing loading times. All you have to do is add the <code>@defer</code> directive your GraphQL query and the router will figure out the rest:</p>



<figure class="wp-block-image size-large is-resized"><img loading="lazy" decoding="async" width="1024" height="496" src="https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-11-29-at-10.58.03-AM-1024x496.png" alt="" class="wp-image-23089" style="aspect-ratio:2.064516129032258;width:610px;height:auto" srcset="https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-11-29-at-10.58.03-AM-1024x496.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-11-29-at-10.58.03-AM-300x145.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-11-29-at-10.58.03-AM-768x372.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-11-29-at-10.58.03-AM-1200x581.png 1200w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-11-29-at-10.58.03-AM.png 1447w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



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



<p>GraphQL continues to push the boundaries of real-time capabilities. Features like `@stream` and new protocols within subscriptions, such as the HTTP callback protocol, enhance real-time experiences. The HTTP callback protocol reduces the need for long-lived connections and enables GraphQL APIs to publish updates to the router.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="469" src="https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-12-08-at-7.40.45-AM-1024x469.png" alt="" class="wp-image-23091" srcset="https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-12-08-at-7.40.45-AM-1024x469.png 1024w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-12-08-at-7.40.45-AM-300x137.png 300w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-12-08-at-7.40.45-AM-768x352.png 768w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-12-08-at-7.40.45-AM-1536x703.png 1536w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-12-08-at-7.40.45-AM-1200x550.png 1200w, https://wp.apollographql.com/wp-content/uploads/2024/01/Screenshot-2023-12-08-at-7.40.45-AM.png 1616w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></figure>



<h1 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</h1>



<p>GraphQL has proven to be a game-changer in the API landscape, offering efficiency, real-time capabilities, and a better developer experience. By implementing GraphQL in platform engineering efforts, organizations can modernize their APIs and provide delightful user experiences. The adoption of the Apollo Router and the use of advanced GraphQL features further elevate the capabilities of GraphQL-based ecosystems. With GraphQL, the future of API development looks promising and user-centric.&nbsp;If you want to learn more, start out with <a href="https://www.apollographql.com/docs/#for-api-implementers">docs for API implementers</a> or you can watch my talk from API world below &#128071;</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="GraphQL Makes Your APIs Better - Michael Watson / API World" width="580" height="326" src="https://www.youtube.com/embed/S28fI-a9Euw?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>


Platform Engineering

Platform Engineering for APIs

Remove Application Logic from Kubernetes Config

GraphQL in a Platform Engineering World

Stay in our orbit