# REST APIs Published articles for REST APIs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to Connect Your Twilio Agent to External APIs in Node.js DevFeed: [How to Connect Your Twilio Agent to External APIs in Node.js]() Original publisher: [Read original article]() Author: Dhruv Patel, Amanda Lange Published: 2026-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [AI Agent](), [Node.js](), [voice ai](), [REST API](), [OpenAI](), [Express]() Tags: [agent](), [ai](), [ai-agent](), [developer-insights](), [environment-variables](), [node-js](), [openai](), [rest-apis](), [visual-studio-code](), [voice]() ### AI overview This tutorial explains how to build a voice-enabled AI agent in Node.js with Twilio Conversation Relay and OpenAI. The agent uses LLM-driven tool calling to retrieve live data and take actions through an external REST API. ### Source excerpt Build a voice-enabled AI agent in Node.js with Twilio Conversation Relay and OpenAI to dynamically fetch live data from external REST APIs. ## MCP vs API DevFeed: [MCP vs API]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-08-14T07:35:02Z Content type: article Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [MCP vs API](), [API](), [Model Context Protocol](), [AI Models](), [Protocol (disambiguation)]() Tags: [ai-models](), [api](), [json-rpc](), [mcp](), [mcp-vs-api](), [rest-apis](), [rpc](), [vs]() ### AI overview This article explains that MCP and APIs serve different purposes. APIs connect software systems through predefined endpoints, while MCP lets AI models discover and use tools dynamically. MCP does not replace APIs; it operates on top of existing APIs as a standardized, AI-friendly translation layer. ### Source excerpt Ever since MCP became popular, I hear people saying "does MCP replace APIs?" Or do they both solve completely different problems? Firstly the facts: APIs connect software systems through predefined endpoints, while MCP enables AI models to discover and use tools dynamically. So, they are two different things, but can MCP replace APIs? More discussions ... ## Apollo is Recognized in Gartner® Voice of the Customer DevFeed: [Apollo is Recognized in Gartner® Voice of the Customer]() Original publisher: [Read original article]() Author: Ilan Belehssen Published: 2026-04-29T16:05:06Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [API](), [GraphOS]() Tags: [2026](), [announcement](), [api-management](), [apollo](), [apollo-connectors](), [customers](), [graphos](), [report](), [rest-apis]() ### AI overview Apollo announces that it was recognized for the first time in the 2026 Gartner Peer Insights "Voice of the Customer" report for API Management. The article reports a 4.7 out of 5 rating from 55 verified enterprise reviewers, with 98% saying they would recommend Apollo as of January 31, 2026, and says Apollo was named a Strong Performer. ### Source excerpt Apollo has been recognized in the 2026 Gartner Peer Insights "Voice of the Customer" for API Management for the first time ## Cursor Pagination vs Offset Pagination: Which One Should You Use? DevFeed: [Cursor Pagination vs Offset Pagination: Which One Should You Use?]() Original publisher: [Read original article]() Published: 2026-03-11T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [API](), [Databases](), [SQL](), [Query (disambiguation)]() Tags: [api](), [apis](), [b-tree](), [database](), [index](), [indexes](), [query-planner](), [rest-apis]() ### AI overview This tutorial compares offset, cursor, and keyset pagination for REST APIs. It explains that offset pagination becomes slower at deep pages because the database scans and discards preceding rows, while concurrent inserts can cause duplicates or skipped results. Cursor pagination uses an indexed position for more consistent performance but does not support random page access; keyset pagination generalizes the approach to arbitrary sort orders. ### Source excerpt . [Cursor vs Offset Pagination](cursor-pagination-vs-offset-pagination-cover... ## How Block Scaled Graph Adoption with Apollo and AI DevFeed: [How Block Scaled Graph Adoption with Apollo and AI]() Original publisher: [Read original article]() Author: Valeria Gomez Published: 2025-11-24T12:30:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Apollo Connectors](), [Model Context Protocol](), [AI Agent](), [gRPC](), [API](), [Tooling]() Tags: [ai-agent](), [apollo-connectors](), [events](), [graphql](), [learn](), [mcp](), [rest-apis](), [services](), [software]() ### AI overview The article recaps Block's GraphQL Summit 2025 session on scaling graph adoption. Block used Apollo Connectors to bring gRPC services onto a federated graph through their existing JSON translation layer, then combined Apollo MCP Server with its open-source AI agent Goose to generate Connector schemas, directives, types, and tests. ### Source excerpt A recap from Block's GraphQL Summit 2025 session on scaling graph adoption with Apollo Connectors, Apollo MCP, and AI When Block's GraphQL platform team discovered Apollo Connectors, they saw a path to bring thousands of existing APIs onto the graph without asking hundreds of engineering teams to run new services or learn new tooling. ## Simplify Your REST API Logic in React with Connectors for REST APIs and GraphQL DevFeed: [Simplify Your REST API Logic in React with Connectors for REST APIs and GraphQL]() Original publisher: [Read original article]() Author: Amanda Martin Published: 2025-05-28T16:41:05Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [Apollo Connectors](), [GraphQL](), [React](), [REST API](), [Next.js]() Tags: [apollo-connectors](), [graphql](), [next-js](), [react](), [rest-apis]() ### AI overview This tutorial shows how to replace repetitive REST API fetch orchestration in a React or Next.js application with a GraphQL layer powered by Apollo Connectors. It demonstrates defining a schema that combines earthquake and location data from REST services without custom resolvers or backend logic. ### Source excerpt If you've built a React or Next.js app that talks to multiple REST APIs, you've probably got a file like actions.ts set up as a central spot for fetch calls to public services like the USGS Earthquake API or Nominatim's reverse geocoder. It works, but the code often ends up repetitive, brittle, and difficult to maintain or scale when different endpoints need to talk to each other. ## JSON - The Fine Print: Part 3 - Zero vs Missing Values DevFeed: [JSON - The Fine Print: Part 3 - Zero vs Missing Values]() Original publisher: [Read original article]() Published: 2025-05-19T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [JSON](), [Go Language](), [Code]() Tags: [api-layers](), [code](), [common-serialization-errors](), [data-serialization](), [data-structure-separation](), [data-transmission](), [data-validation](), [encoding-json](), [go](), [go-json-types](), [go-language-serialization](), [go-language-validation](), [go-type-mapping](), [json](), [json-best-practices](), [json-go-mapping](), [json-marshaling](), [json-unmarshaling](), [json-validation](), [passing-serialized-data](), [rest-apis](), [schema-less-data-format](), [serialization](), [serialization-mistakes](), [serialization-protocols](), [unmarshalling]() ### AI overview This tutorial examines how to distinguish zero values from missing or NULL fields when consuming JSON in Go. It explains basic unmarshalling into structs, notes that absent fields do not cause errors, and introduces DisallowUnknownFields for validating exact JSON input. ### Source excerpt Introduction In part 1 we took a higher level view on serialization in general and JSON in specific. In part 2 we looked at emitting JSON. In part 3, we'll look at an issue you might encounter when consuming JSON, Zero vs NULL field values. To clarify the definition of NULL, this means the absence of value. So here is the question: Given a field in a Go struct set to its zero value, how do you know that zero value was set by the user or it's zero because it was never provided? ## Start building REST APIs with Django REST Framework DevFeed: [Start building REST APIs with Django REST Framework]() Original publisher: [Read original article]() Author: raffaelegrieco.it Published: 2025-05-13T09:45:18Z Content type: tutorial Language: en Sources: [Backend Job: skill, salary and insights - Codemotion Magazine]() Topics: [Django](), [API](), [Python](), [Framework](), [CRUD](), [Authentication](), [Authorization]() Tags: [api](), [authentication](), [authorization](), [backend](), [django](), [guide](), [how-to](), [json](), [process](), [python](), [rest-apis](), [routing](), [web-apis]() ### AI overview A step-by-step tutorial on building REST APIs with Django REST Framework in Python. It covers serializers, views, URL routing, CRUD operations, HTTP requests, authentication, authorization, filtering, throttling, pagination, and browsable API tools. ### Source excerpt Django REST Framework (DRF) is one of the most powerful and flexible tools for building RESTful APIs in Python. This article will guide you step by step through the process of creating your first API endpoint, covering the use of serializers, views, and URL routing. In my previous article, we discussed how to structure your... Read more The post Start building REST APIs with Django REST Framework appeared first on Codemotion Magazine. ## Why Directly Generating MCP Servers from OpenAPI Schemas Can Be Problematic DevFeed: [Why Directly Generating MCP Servers from OpenAPI Schemas Can Be Problematic]() Original publisher: [Read original article]() Author: David Gomes Published: 2025-05-01T19:07:18Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Model Context Protocol](), [OpenAPI Specification](), [Large Language Model](), [API](), [REST API](), [GitHub API](), [FastAPI](), [Claude](), [cursor]() Tags: [agents](), [api](), [claude](), [cursor](), [engineering](), [fastapi](), [github](), [llms](), [mcp](), [openapi](), [product](), [rest-apis]() ### AI overview The article examines whether existing REST APIs and OpenAPI schemas should be converted directly into Model Context Protocol servers. It argues that one-to-one generation can overwhelm language models with too many tools and complex JSON parameters, making tool selection unreliable, especially for large or sensitive APIs. ### Source excerpt Should we be generating Model Context Protocol (MCP) servers directly from existing API specs? MCP is designed to let AI agents like those in Claude, Cursor, and Windsurf interact with tools and APIs. So, can we just treat our existing REST APIs as the interface for LLMs and enti... ## What's New in GraphOS: Apollo Winter '25 Release - Apollo Connectors, Native Query Planner, Improved Tools, and More! DevFeed: [What's New in GraphOS: Apollo Winter '25 Release - Apollo Connectors, Native Query Planner, Improved Tools, and More!]() Original publisher: [Read original article]() Author: Rob Brazier Published: 2025-02-19T18:26:47Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [Apollo Connectors](), [GraphQL](), [REST API](), [Visual Studio]() Tags: [announcement](), [apollo-connectors](), [graphos](), [graphql](), [launch](), [platform](), [release](), [rest-apis](), [router-2-0](), [visual-studio]() ### AI overview Apollo's 2025 Winter Launch introduced general availability for Apollo Connectors for REST APIs and Router 2.0 with a native query planner. The release also included Visual Studio Extension enhancements, client library improvements, and a new free pricing plan. ### Source excerpt This week, the Apollo team 🚀SHIPPED 🚀 Our 2025 Winter Launch took place today, Wednesday, February 19, and was attended by hundreds of developers from across the GraphQL community. Our entire team had such a blast spending time with all of you and taking a deeper look at some of the powerful and exciting capabilities we've added to our GraphOS Platform. We're really proud of the work that went into this release, and it's always such a privilege to share that with all of you. ## REST API Orchestration With GraphQL DevFeed: [REST API Orchestration With GraphQL]() Original publisher: [Read original article]() Author: Matt DeBergalis Published: 2025-02-19T08:45:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [API](), [Orchestration](), [GraphQL](), [REST API](), [SDKs](), [Microservice]() Tags: [announcement](), [api](), [apollo-connectors](), [authorization](), [backends](), [declarative](), [error-handling](), [graph](), [graphql](), [graphql-federation](), [orchestration](), [performance](), [rest](), [rest-apis](), [router](), [sdks](), [teams]() ### AI overview Apollo announces Apollo Connectors, a declarative, graph-based technology for orchestrating REST API calls. The article explains how API calls can be chained, parallelized, transformed, and handled for errors, timeouts, authentication, and authorization. ### Source excerpt Today we are releasing Apollo Connectors, a major update that brings our declarative, graph-based orchestration technology to teams using REST APIs. 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. ## JSON - The Fine Print: Part 2 - Emitting JSON DevFeed: [JSON - The Fine Print: Part 2 - Emitting JSON]() Original publisher: [Read original article]() Published: 2025-02-04T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [JSON](), [API](), [Code](), [Structured-data]() Tags: [api](), [api-layers](), [code](), [common-serialization-errors](), [data](), [data-serialization](), [data-structure-separation](), [data-transmission](), [data-validation](), [encoding](), [encoding-json](), [function](), [go-json-types](), [go-language-serialization](), [go-language-validation](), [go-type-mapping](), [http](), [io](), [io-writer](), [json](), [json-best-practices](), [json-go-mapping](), [json-marshaling](), [json-unmarshaling](), [json-validation](), [map](), [passing-serialized-data](), [properties](), [rest-apis](), [schema](), [schema-less-data-format](), [serialization](), [serialization-mistakes](), [serialization-protocols](), [standard](), [structure](), [writing]() ### AI overview This tutorial explains how to emit JSON in Go using the encoding/json package. It compares json.Marshal, which returns bytes, with json.Encoder, which writes to an io.Writer, and discusses error handling in HTTP handlers. It also demonstrates marshaling maps and structs and using field tags to control JSON property names. ### Source excerpt Introduction In part 1 we took a high-level view on serialization and JSON. In this part, we'll roll our sleeves and start working with JSON, focused on emitting JSON. You might think this is a basic topic, but there is much more to it than just calling json.Marshal. json.Marshal vs json.Encoder The encoding/json package has two main APIs: Marshal and NewEncoder. The Marshal function returns a []byte while the NewEncoder function will write to an io.Writer. The question is: When should you use one API over the other? ## Effortless Data Fetching: Introducing Apollo Connectors for REST APIs DevFeed: [Effortless Data Fetching: Introducing Apollo Connectors for REST APIs]() Original publisher: [Read original article]() Author: Robert Walters Published: 2024-12-05T14:00:17Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [Apollo Connectors](), [GraphQL](), [REST API](), [React]() Tags: [announcement](), [apollo-connectors](), [graphql](), [net-conf](), [react](), [rest-apis](), [tutorial]() ### AI overview This tutorial demonstrates how Apollo Connectors can fetch data from REST APIs without custom GraphQL resolvers. It walks through a React currency-converter application using the Apollo GraphQL client, CurrencyAPI, Apollo Studio, and Rover CLI. ### Source excerpt 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. 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're trying to solve. ## JSON - The Fine Print: Part 1 DevFeed: [JSON - The Fine Print: Part 1]() Original publisher: [Read original article]() Published: 2024-10-23T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [JSON](), [API]() Tags: [api-layers](), [apis](), [common-serialization-errors](), [data-serialization](), [data-structure-separation](), [data-transmission](), [data-validation](), [database](), [elasticsearch](), [encoding-json](), [go-json-types](), [go-language-serialization](), [go-language-validation](), [go-type-mapping](), [json](), [json-best-practices](), [json-go-mapping](), [json-marshaling](), [json-unmarshaling](), [json-validation](), [passing-serialized-data](), [rest-apis](), [schema-less-data-format](), [sensitive-data](), [serialization](), [serialization-mistakes](), [serialization-protocols]() ### AI overview This article explains JSON and serialization fundamentals, then examines common mistakes. It recommends serializing data at program boundaries and using separate data structures for API, business, and storage layers to avoid inefficiency, coupling, and accidental exposure of sensitive data. ### Source excerpt Introduction Everybody knows JSON, it's a simple serialization format and the default format for REST APIs. Like many other topics, there are fine points you should know in order to work with JSON more effectively and avoid common mistakes. In this article we'll explore some big picture aspects and some low level details of using JSON. Serialization Before diving into JSON, I'd like to take a look at serialization in general and discuss common mistakes I've seen my customers make. ## Apollo Connectors Integrate GraphQL APIs with REST APIs DevFeed: [Apollo Connectors Integrate GraphQL APIs with REST APIs]() Original publisher: [Read original article]() Author: Dylan Anthony Published: 2024-10-09T08:31:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [REST API](), [Programming]() Tags: [announcement](), [apollo-connectors](), [declarative](), [graphql](), [observability](), [opentelemetry](), [rest-apis](), [schema]() ### AI overview Apollo Connectors let developers connect GraphQL fields to HTTP APIs using declarative syntax in schema files. GraphOS Router can communicate directly with the APIs without an intermediate subgraph service. ### Source excerpt 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 directly to the API, no subgraph needed. ## Parsing: the merit of strictly typed JSON DevFeed: [Parsing: the merit of strictly typed JSON]() Original publisher: [Read original article]() Author: Max Duval Published: 2024-07-26T16:05:58Z Content type: tutorial Language: en Sources: [Guardian]() Topics: [JSON](), [TypeScript](), [JavaScript](), [Parsing](), [Programming]() Tags: [javascript](), [json](), [parsing](), [rest-apis](), [runtime-errors](), [typescript]() ### AI overview This tutorial explains how loosely typed JSON.parse results can undermine TypeScript's static analysis. It recommends precisely describing and validating the shape of changing JSON responses so API or data-shape errors can be detected and handled more helpfully before they cause runtime failures. ### Source excerpt Dealing with content that keeps changing can lead to bugs on users' devices that are hard to reproduce. By precisely describing the shape of the content using types and ensuring it matches, exceptions can be avoided and users shown helpful messages when errors occur. This post will illustrate how this can be achieved with standard web technologies. The programming language of the web is JavaScript (JS), but its lack of static typing is the top pain point raised from the 2023 State of JS survey. We rely on TypeScript (TS) to get a strong structural type analysis of our code, as mentioned in our article on standardisation. Static typing helps prevent runtime errors on our users' machines. However, to ensure that no TypeError ever appears, we need to avoid the loose 'any' type, which is an escape hatch designed to opt-out of TS' static analysis. JavaScript Object Notation (JSON) is widely used as a data exchange format for REST APIs. Its syntax is compatible with JS, with only a subset of the language's primitives: objects, arrays, strings, numbers and nulls. Simple objects can be turned into a string with JSON.stringify and turned back into an object with JSON.parse, making it an adequate choice for many uses. We use it for powering our comments, new live blog updates, football match scores, weather, most read and other features of the website and Apps. Continue reading... ## Delivering personalized travel experiences with GraphQL DevFeed: [Delivering personalized travel experiences with GraphQL]() Original publisher: [Read original article]() Author: Tushar Bhushan Published: 2023-07-14T12:47:41Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [GraphOS](), [Microservice](), [data]() Tags: [apis](), [apollo-federation](), [architectures](), [dependencies](), [fragmentation](), [graphos](), [graphql](), [recommendations](), [rest-apis](), [services](), [state]() ### AI overview This article explains how Apollo GraphOS and Apollo Federation can provide a unified view of a traveler's data while preserving microservice architectures. It contrasts this federated approach with REST-based aggregation, where clients make multiple requests and manage data dependencies and business logic. ### Source excerpt This post is a part of our "How to build connected travel apps with Apollo GraphOS" series. Also in this series: - Ship products faster with SDUI - Mitigate scraping and bot attacks with GraphOS - Seamlessly integrate with partners to enhance the travel experience In the ever-evolving travel industry, companies are recognizing the value of delivering personalized experiences to their customers. ## The Democratisation of Artificial Intelligence with ChatGPT DevFeed: [The Democratisation of Artificial Intelligence with ChatGPT]() Original publisher: [Read original article]() Author: Juanky Soriano Published: 2023-04-13T16:26:47Z Content type: opinion Language: en Sources: [Novoda]() Topics: [Artificial Intelligence](), [ChatGPT](), [AI Development](), [MLOps](), [DevOps]() Tags: [ai](), [automate](), [chatgpt](), [developers](), [devops](), [engineering](), [mlops](), [rest-apis]() ### AI overview This opinion article argues that ChatGPT and other GPT models have made artificial intelligence more accessible to businesses and developers. It describes how reduced complexity and readily available training resources and development tools can help organizations create AI solutions, optimize processes, and pursue business value. It also discusses implications for MLOps and DevOps. ### Source excerpt AI is more accessible than it's ever been. How can businesses leverage AI solutions to unlock value that was previously out of their reach? The post The Democratisation of Artificial Intelligence with ChatGPT appeared first on Novoda. ## Generated GraphQL Schemas and Schema Design DevFeed: [Generated GraphQL Schemas and Schema Design]() Original publisher: [Read original article]() Author: Shane Myrick Published: 2022-09-01T09:00:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [schema design](), [API]() Tags: [api](), [apis](), [backend](), [graphql](), [rest-apis](), [schema](), [schema-design](), [sql](), [tooling]() ### AI overview This article explains how GraphQL schemas define the types and operations available through an API. It distinguishes generated schemas from schema-first and code-only approaches, and introduces trade-offs involved in designing schemas for client needs. ### Source excerpt GraphQL is a type-safe language for APIs. A common misunderstanding is that GraphQL is another complete query language, like SQL, which allows you to search, filter, and select all the objects in a database. Instead, GraphQL should be thought of as a way to specify the types of data available and the specific operations users can perform over an API. ## REST APIs for every Temporal Workflow in one line of code DevFeed: [REST APIs for every Temporal Workflow in one line of code]() Original publisher: [Read original article]() Author: Valeri Karpov Published: 2022-02-28T07:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [REST API](), [Express](), [client](), [Code]() Tags: [apis](), [client](), [code](), [express](), [how-to](), [integration](), [rest](), [rest-apis]() ### AI overview This tutorial shows how to create REST APIs for Temporal Workflows using the temporal-rest middleware with ExpressJS. It demonstrates endpoints for starting Workflows, sending Signals, and executing Queries, including JSON request bodies and query parameters. ### Source excerpt Learn how to create a REST API for Temporal Workflows in just one line of code using temporal-rest and ExpressJS, simplifying your workflow integration. ## RetailMeNot GraphQL Federation DevFeed: [RetailMeNot GraphQL Federation]() Original publisher: [Read original article]() Author: Kartik Kumar Gujarati Published: 2021-10-08T15:01:45Z Content type: article Language: en Sources: [RetailMeNot]() Topics: [GraphQL](), [Back end](), [Graphs](), [Android](), [iOS]() Tags: [android](), [browser](), [engineering](), [extension](), [graphql](), [graphql-federation](), [ios](), [mobile](), [rest-api](), [rest-apis](), [retailmenot](), [web](), [ziff-davis]() ### AI overview This article describes how RetailMeNot addressed REST API versioning, over-fetching, and under-fetching by adopting GraphQL and transitioning from a GraphQL monolith toward GraphQL Federation. It covers the company's application and backend rebuild across Android, iOS, web, and browser extension experiences. ### Source excerpt Did you ever have to maintain multiple versions of a REST API because the change you needed to make would break existing clients? Does your native app have to call multiple REST endpoints to get all the data it needs? This blog post is about how we addressed these common problems using GraphQL and our transition to GraphQL Federation at RetailMeNot. RetailMeNot, part of Ziff Media, Inc, makes everyday life more affordable for shoppers. We are a leading savings destination providing online and in-store coupons and cashback offers to our users. Today, we serve millions of monthly active users from our desktop, mobile web, native (iOS & Android) apps, and browser extension (Deal Finder™) experiences. For the last 10 years, RetailMeNot's engineering teams have built several highly performant, scalable, and efficient systems to bring savings data to our users through our experiences. And like many companies, RetailMeNot used REST APIs to serve the data. However, as the company and the systems grew, we started to experience problems like versioning, over-fetching, and under-fetching with REST APIs. For more details on the classic problems that arise from REST services and how GraphQL solves them, see this blog post. For an introduction to GraphQL, see this blog post. How it started: A Monolithic Graph In 2019, we took a step back to rethink where we are headed in terms of our tech stack and how to best serve future experiences. We decided to rewrite our native Android and iOS apps and the backend that supports them. In addition to this, we also built a brand new browser extension (Deal Finder™) and re-wrote several parts of our core website. As we started to rebuild our native apps, we wanted to solve the above problems we faced with REST APIs. GraphQL seemed like a great solution for this. Enter GraphQL. In our first iteration with GraphQL, we built a GraphQL monolith. Monolith Graph The GraphQL Monolith at RetailMeNot was a single GraphQL Server used by our Native Andro ## Monitoring REST APIs with Custom JDK Flight Recorder Events DevFeed: [Monitoring REST APIs with Custom JDK Flight Recorder Events]() Original publisher: [Read original article]() Published: 2020-01-29T14:30:00Z Content type: tutorial Language: en Sources: [Gunnar Morling]() Topics: [JDK Flight Recorder](), [Monitoring](), [REST API](), [Java](), [Grafana](), [Prometheus]() Tags: [grafana](), [java](), [jdk-flight-recorder](), [jvm](), [monitoring](), [prometheus](), [rest](), [rest-apis]() ### AI overview This tutorial explains how custom JDK Flight Recorder events can monitor a REST API, including tracking request counts and identifying long-running requests. It also describes using the JFR Event Streaming API to export live events for monitoring and alerting with Prometheus and Grafana. ### Source excerpt Table of Contents Custom Flight Recorder Events Creating JFR Recordings Event Settings JFR Event Streaming MicroProfile Metrics Summary and Related Work The JDK Flight Recorder (JFR) is an invaluable tool for gaining deep insights into the performance characteristics of Java applications. Open-sourced in JDK 11, JFR provides a low-overhead framework for collecting events from Java applications, the JVM and the operating system. In this blog post we're going to explore how custom, application-specific JFR events can be used to monitor a REST API, allowing to track request counts, identify long-running requests and more. We'll also discuss how the JFR Event Streaming API new in Java 14 can be used to export live events, making them available for monitoring and alerting via tools such as Prometheus and Grafana. ## Easy and performant GraphQL over REST DevFeed: [Easy and performant GraphQL over REST]() Original publisher: [Read original article]() Author: Martijn Walraven Published: 2018-06-19T22:44:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [apollo-server](), [GraphQL](), [Caching](), [JavaScript](), [HTTP](), [Authorization](), [Error Handling](), [JSON]() Tags: [apis](), [apollo](), [authorization](), [backend](), [batching](), [caching](), [error-handling](), [graphql](), [http](), [javascript](), [json](), [rest](), [rest-apis]() ### AI overview This article introduces data sources in Apollo Server 2.0, describing them as classes for fetching and caching data from REST endpoints. It explains built-in support for caching, deduplication, error handling, HTTP requests, query parameters, JSON parsing, authorization, and GraphQL execution context. ### Source excerpt Last Friday, we published a first release candidate of Apollo Server 2.0, a 100% open source JavaScript GraphQL server that bakes in the best practices we've learned working with hundreds of teams running GraphQL in production. This post introduces data sources, one of its new features. In our experience, the right way to deploy GraphQL is as a layer between your apps and your existing APIs and services. ## Caching GraphQL results in your CDN DevFeed: [Caching GraphQL results in your CDN]() Original publisher: [Read original article]() Author: Sashko Stubailo Published: 2018-04-06T21:05:00Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Caching](), [HTTP](), [API]() Tags: [akamai](), [announcement](), [api](), [caching](), [cdn](), [cloudflare](), [graphql](), [http](), [optimization](), [rest-apis]() ### AI overview This tutorial explains how to cache GraphQL API results in a CDN. It describes using edge caching for infrequently changing public data, improving load times and reducing server load, while noting that caching is less useful for frequently changing or private data. ### Source excerpt At first glance, it might seem like GraphQL is so different from REST and other HTTP API technologies that you have to rethink all of your infrastructure from scratch. But it turns out that it's not hard to add GraphQL to your existing setup and start getting the benefits you want right away, without having to rebuild anything you already have. - You can keep your existing backends and business logic, since you can put GraphQL over REST APIs. [Next page]()