# GraphQL

GraphQL is an open-source query language for APIs and a server-side runtime that uses strongly typed schemas.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## CVE-2026-77367 - Daptin: Unauthenticated SQL Injection via the \`sort\` query parameter on every entity list endpoint

DevFeed: [CVE-2026-77367 - Daptin: Unauthenticated SQL Injection via the \`sort\` query parameter on every entity list endpoint](<https://devfeed.tech/articles/cve-2026-77367-daptin-unauthenticated-sql-injection-via-the-sort-query-parameter-on-every-entity-list-endpoint-143947.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-77367>)

Author: CVEFEED.io; github.com

Published: 2026-11-19T17:18:59Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [SQL](<https://devfeed.tech/topics/sql.md>), [sql-database](<https://devfeed.tech/topics/sql-database.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [can](<https://devfeed.tech/tags/can.md>), [cms](<https://devfeed.tech/tags/cms.md>), [column](<https://devfeed.tech/tags/column.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-77367](<https://devfeed.tech/tags/cve-2026-77367.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [daptin](<https://devfeed.tech/tags/daptin.md>), [error](<https://devfeed.tech/tags/error.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [headless](<https://devfeed.tech/tags/headless.md>), [identifier](<https://devfeed.tech/tags/identifier.md>), [list](<https://devfeed.tech/tags/list.md>), [schema](<https://devfeed.tech/tags/schema.md>), [sort](<https://devfeed.tech/tags/sort.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-injection](<https://devfeed.tech/tags/sql-injection.md>)

### AI overview

Before Daptin 0.12.30, the generic GET /api/{entity} list endpoint accepts unvalidated, attacker-controlled `sort` values. In PaginatedFindAllWithoutFilters, those values are used to construct SELECT and ORDER BY identifiers without checking them against the table schema; an embedded quote can break out of the quoted identifier and alter SQL parsing. The excerpt says unauthenticated attackers may extract unauthorized table data through blind or error-based behavior, or repeatedly trigger query failures. The issue is fixed in version 0.12.30.

### Source excerpt

CVE ID :CVE-2026-77367 Published : Nov. 19, 2026, 5:18 p.m. | 26 minutes ago Description :Daptin is a GraphQL/JSON-API headless CMS. Prior to 0.12.30, the generic GET /api/{entity} list endpoint accepts attacker-controlled sort values in PaginatedFindAllWithoutFilters in server/resource/resource_findallpaginated.go without validating the requested column against the table schema. The code uses those values for SELECT and ORDER BY identifier construction, so an embedded identifier quote can terminate the quoted identifier and make the remainder parse as SQL, allowing an unauthenticated attacker to extract unauthorized table data through blind or error-based behavior or repeatedly trigger query failures. This issue is fixed in version 0.12.30. Severity: 9.4 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Autonomous Multi-modal Agents for ITOps Observability

DevFeed: [Autonomous Multi-modal Agents for ITOps Observability](<https://devfeed.tech/articles/autonomous-multi-modal-agents-for-itops-observability-137520.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.19982>)

Author: Gunjan Siddharth, Sanjana Garai, Utsav Shekhar, Prakhar Jain, Sarvam Maheshwari, Balaji Ganesan, Avirup Saha, Seema Nagar, Pratik Mishra, Felix George, Suranjana Samanta, Harshit Kumar, Mudit Verma, P

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>)

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [hierarchical agent systems](<https://devfeed.tech/topics/hierarchical-agent-systems.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [agent orchestration](<https://devfeed.tech/topics/agent-orchestration.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-ma](<https://devfeed.tech/tags/cs-ma.md>), [defects](<https://devfeed.tech/tags/defects.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [itops](<https://devfeed.tech/tags/itops.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [llm](<https://devfeed.tech/tags/llm.md>), [mapping](<https://devfeed.tech/tags/mapping.md>), [multi-agent](<https://devfeed.tech/tags/multi-agent.md>), [natural-language](<https://devfeed.tech/tags/natural-language.md>), [observability](<https://devfeed.tech/tags/observability.md>), [operations](<https://devfeed.tech/tags/operations.md>), [routing](<https://devfeed.tech/tags/routing.md>), [schema](<https://devfeed.tech/tags/schema.md>), [serving](<https://devfeed.tech/tags/serving.md>), [studio](<https://devfeed.tech/tags/studio.md>), [system](<https://devfeed.tech/tags/system.md>), [systems](<https://devfeed.tech/tags/systems.md>), [tool](<https://devfeed.tech/tags/tool.md>)

### AI overview

ITOps Observability Studio coordinates specialized LLM agents to connect observability tools and automate workflows, including natural-language-to-GraphQL queries, schema generation and mapping, trace data lifecycle management, and visualization. Its three-tier design supports inter-agent communication and unified tool integration, with analytics tracing agent model and tool calls. Agents are evaluated separately using gold answers where available and model judging for schema mapping and chart quality. The abstract reports strong query generation on a public benchmark and routing with a current open model, and success in most data lifecycle scenarios. It also says evaluation exposed defects arising from interactions among prompts, parsers, and serving stacks, along with fixes; no numerical results are given.

### Source excerpt

arXiv:2611.19982v1 Announce Type: new Abstract: ITOps observability products must integrate data from different tools and systems. We present ITOps Observability Studio, a multi-modal multi-agent system that orchestrates observability workflows through collaborative AI agents. Its three-tier architecture features inter-agent communication, specialized LLM-powered agents for data access, schema operations and visualization, and unified tool integration. The system supports natural language to GraphQL translation, GraphQL schema generation, schema mapping, trace data lifecycle management and multi-tool workflows for reliability engineering. Its agents are instrumented with agent analytics, so that their model and tool calls can be traced. We evaluate each agent on its own benchmark, scored against gold answers where they exist and by a model judge for schema mapping and chart quality. Query generation on a public benchmark and routing work well with a current open model, and the data lifecycle management agent solves most of its scenarios. The evaluation exposed defects that only appear when prompts, parsers and serving stacks are tested together, and we report them together with their fixes.

## CVE-2026-120697 - Wiki.js: Stored XSS via Vue Slot Directives in Page Content

DevFeed: [CVE-2026-120697 - Wiki.js: Stored XSS via Vue Slot Directives in Page Content](<https://devfeed.tech/articles/cve-2026-120697-wiki-js-stored-xss-via-vue-slot-directives-in-page-content-136268.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-120697>)

Author: CVEFEED.io; github.com

Published: 2026-11-16T22:18:14Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [XSS](<https://devfeed.tech/topics/xss.md>), [Vue.js](<https://devfeed.tech/topics/vue.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [Wiki](<https://devfeed.tech/topics/wiki.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cve-2026-120697](<https://devfeed.tech/tags/cve-2026-120697.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [requarks](<https://devfeed.tech/tags/requarks.md>), [version](<https://devfeed.tech/tags/version.md>), [vue](<https://devfeed.tech/tags/vue.md>), [wiki-js](<https://devfeed.tech/tags/wiki-js.md>), [xss](<https://devfeed.tech/tags/xss.md>)

### AI overview

Before Wiki.js 2.5.315, an authenticated user with write:pages could store JavaScript expressions in the v-slot:tabs or v-slot:content attributes of page HTML. The sanitizer allowed these Vue directives, and the rendered HTML was later compiled by the Vue 2 runtime compiler, causing the expressions to run in the Wiki.js origin when another user viewed the page. The author did not need write:scripts or administrative permissions. Malicious code could act with the viewer's browser session, including performing privileged GraphQL operations if a privileged user opened the page. The issue is fixed in version 2.5.315.

### Source excerpt

CVE ID :CVE-2026-120697 Published : Nov. 16, 2026, 10:18 p.m. | 36 minutes ago Description :Wiki.js is an open source wiki app built on Node.js. Prior to 2.5.315, an authenticated user with write:pages can store JavaScript expressions in the v-slot:tabs or v-slot:content attributes of page HTML because server/modules/rendering/html-security/renderer.js adds those executable Vue directives to DOMPurify's allowlist. The sanitized output is inserted as rendered page HTML and later compiled by the Vue 2 runtime compiler, so the expressions execute in the Wiki.js origin when another user views the page even when the author lacks write:scripts and administrative permissions. The script runs with the viewer's browser session and can read same-origin data, modify displayed content, present phishing content, or perform actions available to that viewer, including privileged GraphQL operations when a privileged user opens the page. This issue is fixed in version 2.5.315. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-76823 - OpenCTI: Elasticsearch credentials disclosed to connector tokens through logsWorkerConfig

DevFeed: [CVE-2026-76823 - OpenCTI: Elasticsearch credentials disclosed to connector tokens through logsWorkerConfig](<https://devfeed.tech/articles/cve-2026-76823-opencti-elasticsearch-credentials-disclosed-to-connector-tokens-through-logsworkerconfig-136285.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-76823>)

Author: CVEFEED.io; github.com

Published: 2026-11-16T21:17:31Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [audit](<https://devfeed.tech/tags/audit.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [bearer-token](<https://devfeed.tech/tags/bearer-token.md>), [capability](<https://devfeed.tech/tags/capability.md>), [citeum](<https://devfeed.tech/tags/citeum.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-76823](<https://devfeed.tech/tags/cve-2026-76823.md>), [delete](<https://devfeed.tech/tags/delete.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [history](<https://devfeed.tech/tags/history.md>), [impact](<https://devfeed.tech/tags/impact.md>), [index](<https://devfeed.tech/tags/index.md>), [opencti](<https://devfeed.tech/tags/opencti.md>), [opencti-platform](<https://devfeed.tech/tags/opencti-platform.md>), [published](<https://devfeed.tech/tags/published.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Before OpenCTI 7.260706.0, the logsWorkerConfig GraphQL query uses the broad CONNECTORAPI capability and exposes Elasticsearch connection details, including credentials, to anyone holding a connector API bearer token. If those credentials are valid and Elasticsearch is reachable, a caller may read, modify, or delete OpenCTI indices and audit history outside application-layer controls; impact depends on credential privileges and network reachability. The issue is fixed in version 7.260706.0.

### Source excerpt

CVE ID :CVE-2026-76823 Published : Nov. 16, 2026, 9:17 p.m. | 1 hour, 37 minutes ago Description :OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260706.0, the logsWorkerConfig GraphQL query is authorized with the broad CONNECTORAPI capability and returns Elasticsearch connection details including elasticsearch_username, elasticsearch_password, elasticsearch_api_key, the URL, index, proxy, and TLS-verification setting. A holder of any connector API bearer token can retrieve this credential material. If the returned credentials are valid and Elasticsearch is reachable, the caller can directly read, modify, or delete OpenCTI indices and audit history outside application-layer role, marking, organization, and audit controls, with the practical impact bounded by the credentials' privileges and network reachability. This issue is fixed in version 7.260706.0. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Samyama-SDG: A Declarative GraphQL @count and Regex/Ontology Synthetic Data Compiler with $O(1)$-Memory Referential Integrity and Causal Ground Truth

DevFeed: [Samyama-SDG: A Declarative GraphQL @count and Regex/Ontology Synthetic Data Compiler with $O(1)$-Memory Referential Integrity and Causal Ground Truth](<https://devfeed.tech/articles/samyama-sdg-a-declarative-graphql-count-and-regex-ontology-synthetic-data-compiler-with-o-1-memory-referential-integrity-and-causal-ground-truth-125669.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.11295>)

Author: Madhulatha Mandarapu, Sandeep Kunkunuru

Published: 2026-11-10T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>)

Topics: [Compiler](<https://devfeed.tech/topics/compiler.md>), [Ground truth / benchmark quality](<https://devfeed.tech/topics/ground-truth-benchmark-quality.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>), [schema design](<https://devfeed.tech/topics/schema-design.md>)

Tags: [000](<https://devfeed.tech/tags/000.md>), [2](<https://devfeed.tech/tags/2.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [after](<https://devfeed.tech/tags/after.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [based](<https://devfeed.tech/tags/based.md>), [binder](<https://devfeed.tech/tags/binder.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [cs-db](<https://devfeed.tech/tags/cs-db.md>), [data](<https://devfeed.tech/tags/data.md>), [declarative](<https://devfeed.tech/tags/declarative.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [integrity](<https://devfeed.tech/tags/integrity.md>), [memory](<https://devfeed.tech/tags/memory.md>), [ontology](<https://devfeed.tech/tags/ontology.md>), [referential-integrity](<https://devfeed.tech/tags/referential-integrity.md>), [regex](<https://devfeed.tech/tags/regex.md>), [synthetic](<https://devfeed.tech/tags/synthetic.md>), [synthetic-data](<https://devfeed.tech/tags/synthetic-data.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Samyama-SDG (sdg-rs) combines declarative data generation with ontology-bound causal simulation. It compiles GraphQL schemas and an Attribute Data Dictionary into a dependency DAG; seekable SplitMix64 values and index-bijective primary keys let it resolve uniform or Zipfian foreign keys and multi-hop temporal constraints without storing parent-key pools, using O(1) memory. A second layer adds fault propagation and machine-scorable ground truth. Across three schemas, the abstract reports generation rates of 5.80-7.76 million rows per second at one million records, and 31.4-35.1 MiB memory at five million records. It reports zero conformance errors across 1.15 million foreign keys and 900,000 temporal constraints.

### Source excerpt

arXiv:2611.11295v1 Announce Type: new Abstract: Synthetic data generators face a divide between declarative relational mockets and domain causal simulators. Declarative generators specify entities, regexes, and foreign keys via schemas, but buffer parent primary-key pools in RAM ($O(N)$ memory) and lack ontology bindings or causal ground truth. Conversely, domain simulators emit realistic streams and ground-truth labels, but require thousands of lines of procedural code per domain. We present Samyama-SDG (sdg-rs), a Rust synthetic data compiler unifying declarative schema compilation with ontology-bound causal simulation. At Layer 1, Samyama-SDG compiles Cardinality-Extended GraphQL schemas (@count, @pk, @ontology, @regex, @dist, @fk, @after) and an Attribute Data Dictionary into a topologically sorted DAG. Combining stateless counter-based seekable PRNGs (SplitMix64 over $(\text{seed}, \text{entity}, \text{row}, \text{field})$) with index-bijective primary keys $f_{\text{PK}}(s, E, i)$ lets child tables resolve uniform or Zipfian foreign keys and multi-hop @after constraints in $O(1)$ memory without buffering parent tables. At Layer 2, causal processes layer fault propagation and machine-scorable ground truth (ground_truth.jsonl) over the same seekable PRNG and samyama-ontologies binder. Across three schemas, Samyama-SDG generates $1{,}000{,}000$ records in $128.79\text{ ms}$--$172.43\text{ ms}$ ($5.80\text{M}$--$7.76\text{M}$ rows/s) and $5{,}000{,}000$ records in $676.12\text{ ms}$--$808.56\text{ ms}$ at flat $31.4\text{ MiB}$--$35.1\text{ MiB}$ memory, with $0$ conformance errors across $1{,}150{,}000$ foreign keys and $900{,}000$ temporal constraints.

## When GraphQL earns its place in an enterprise application, and when it doesn't

DevFeed: [When GraphQL earns its place in an enterprise application, and when it doesn't](<https://devfeed.tech/articles/when-graphql-earns-its-place-in-an-enterprise-application-and-when-it-doesn-t-102104.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4240424/when-graphql-earns-its-place-in-an-enterprise-application-and-when-it-doesnt.html>)

Author: Vaishnavi Khosla

Published: 2026-10-27T09:00:00Z

Content type: article

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [back-end](<https://devfeed.tech/tags/back-end.md>), [backend](<https://devfeed.tech/tags/backend.md>), [backend-development](<https://devfeed.tech/tags/backend-development.md>), [connected-data](<https://devfeed.tech/tags/connected-data.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [costs](<https://devfeed.tech/tags/costs.md>), [data](<https://devfeed.tech/tags/data.md>), [data-management](<https://devfeed.tech/tags/data-management.md>), [data-management-development-approaches-development-tools-software-development](<https://devfeed.tech/tags/data-management-development-approaches-development-tools-software-development.md>), [development-approaches](<https://devfeed.tech/tags/development-approaches.md>), [development-tools](<https://devfeed.tech/tags/development-tools.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [fields](<https://devfeed.tech/tags/fields.md>), [front-end](<https://devfeed.tech/tags/front-end.md>), [governance](<https://devfeed.tech/tags/governance.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [it](<https://devfeed.tech/tags/it.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [query](<https://devfeed.tech/tags/query.md>), [rest](<https://devfeed.tech/tags/rest.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [screen](<https://devfeed.tech/tags/screen.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

GraphQL is most useful when screens need different slices of highly interconnected data: a client can request related objects in one query, reducing sequential REST calls and the need to build new tailored endpoints as screens change. The author's access-governance example has this pattern, while noting the benefit is fewer endpoints and queries rather than a quantified time saving. The tradeoffs are harder caching, potentially expensive deep or broad queries, and authorization checks at object and field level. The text recommends query depth and cost limits, pagination, and keeping authorization rules in shared business logic rather than resolvers. Adoption depends on varied client needs, data interdependence, schema ownership, and centralized authorization; a read-heavy screen is suggested as a trial when answers are mixed. REST remains the author's choice for command operations such as credential rotation, which benefit from focused authorization, logging, and retries.

### Source excerpt

The value of GraphQL emerges for a specific type of enterprise screen, one that brings together highly interdependent data across multiple sources. In all other cases, there is a price to pay, which is bound to come out after you have already made the decision. I build internal access-governance applications, with React front ends that talk to both REST and GraphQL back ends. Using the two side by side has shown me where each earns its keep and where each gets in the way. The article is divided into three sections. The first section covers areas in which GraphQL eliminates round trips and front-end work. The second section highlights the underestimated costs involved. Finally, there are a few questions you can ask yourself before implementing the GraphQL approach. GraphQL helps most on screens built from connected data Imagine the details screen for one client. On this screen, you see the client, his/her accounts, permissions for these accounts, owners of these accounts and some related objects for each. Data is highly interrelated, and your screen requires some portion of each layer at once. There are two scenarios for working with REST API. In the first scenario, the front end makes several requests - first for the client, then for his accounts and then for permissions of each of those accounts. Each request in the chain waits for the preceding request to be finished. Another scenario is when the back end creates a specific endpoint in the desired format. The first one becomes very inefficient whenever the network has some issues. The second one works well as long as the information that is to appear on the next screen appears in the same format as before, but then you get many endpoints nobody cares about maintaining. With the help of GraphQL, it becomes possible to change the decision-maker of the shape. The client asks for the query with the specific fields and receives the response in the specific format. This is how it is described in the GraphQL documentatio

## Authorization Differential Testing in Salesforce

DevFeed: [Authorization Differential Testing in Salesforce](<https://devfeed.tech/articles/authorization-differential-testing-in-salesforce-100765.md>)

Original publisher: [Read original article](<https://www.netspi.com/blog/technical-blog/cloud-pentesting/authorization-differential-testing-in-salesforce/>)

Author: Aussan Saad-Ali

Published: 2026-10-26T19:17:06Z

Content type: tutorial

Language: en

Sources: [NetSPI](<https://devfeed.tech/sources/netspi.md>)

Topics: [Authorization](<https://devfeed.tech/topics/authorization.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Hacking](<https://devfeed.tech/topics/hacking.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [cloud-pentesting](<https://devfeed.tech/tags/cloud-pentesting.md>), [custom](<https://devfeed.tech/tags/custom.md>), [differential-testing](<https://devfeed.tech/tags/differential-testing.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [hidden](<https://devfeed.tech/tags/hidden.md>), [identity](<https://devfeed.tech/tags/identity.md>), [salesforce](<https://devfeed.tech/tags/salesforce.md>), [testing](<https://devfeed.tech/tags/testing.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

Authorization Differential Testing compares the same user, record, field, and operation across Salesforce UI API, GraphQL, and custom paths to find inconsistent access enforcement. UI API and GraphQL honor the caller's record, object, and field access in the described tests; custom Apex can differ. `with sharing` enforces record sharing but does not by itself enforce object permissions or field-level security for system-mode database operations. Apex classes at API v66 or earlier default to system mode, while v67 or later default to user context, so an org may contain both behaviors. The excerpt recommends recording each class's API version, sharing declaration, and query or DML mode; testing restricted users and site guests separately against native APIs and reachable Apex methods; and repeating checks after permission changes, API upgrades, or site migrations. Developers can select user mode explicitly or use `Security.stripInaccessible()` when inaccessible fields should be removed.

### Source excerpt

NetSPI Salesforce expert Aussan explores how holding identity steady across UI API, GraphQL, and custom @AuraEnabled Apex methods reveals hidden authorization gaps. The post Authorization Differential Testing in Salesforce appeared first on NetSPI.

## Deprecating the GraphQL API: timeline and migration paths

DevFeed: [Deprecating the GraphQL API: timeline and migration paths](<https://devfeed.tech/articles/deprecating-the-graphql-api-timeline-and-migration-paths-101230.md>)

Original publisher: [Read original article](<https://weaviate.io/blog/graphql-api-deprecation>)

Author: Dirk Kulawiak; Ivan Despot

Published: 2026-10-26T00:00:00Z

Content type: release

Language: en

Sources: [Weaviate Blog](<https://devfeed.tech/sources/weaviate-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [API](<https://devfeed.tech/topics/api.md>), [client library](<https://devfeed.tech/topics/client-library.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [migration](<https://devfeed.tech/tags/migration.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>)

### AI overview

Weaviate deprecated its GraphQL API on October 26, 2026, but existing clusters continue working for now. Weaviate Cloud disables GraphQL on December 1, 2026 for clusters with no use in the prior 30 days, and on all remaining clusters by May 1, 2027. Self-hosted versions released before that date retain GraphQL; the first minor release afterward disables it by default, with removal planned later but undated. Current Python, TypeScript, Java and C# clients use gRPC; Go users are directed to the v6 client. Browser and edge applications can use the TypeScript web client with gRPC-Web, while the Preview REST Search API provides JSON search and aggregation but covers only a subset of GraphQL features. Migration steps are to find GraphQL calls, choose a replacement, convert queries using the guide, and test with GraphQL disabled. Self-hosted users can set `DISABLE_GRAPHQL=true`; Cloud customers can ask support to disable it on a test cluster.

### Source excerpt

Weaviate's GraphQL API is deprecated as of October 26, 2026. See the timeline for Weaviate Cloud and self-hosted, who is affected, and how to migrate.

## Why your schema shouldn't mirror your database (and what to do instead)

DevFeed: [Why your schema shouldn't mirror your database (and what to do instead)](<https://devfeed.tech/articles/why-your-schema-shouldn-t-mirror-your-database-and-what-to-do-instead-90039.md>)

Original publisher: [Read original article](<https://www.red-gate.com/simple-talk/databases/why-your-schema-shouldnt-mirror-your-database-and-what-to-do-instead/>)

Author: Nick Harrison

Published: 2026-10-19T12:00:00Z

Content type: tutorial

Language: en

Sources: [Simple Talk](<https://devfeed.tech/sources/simple-talk.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>), [schema design](<https://devfeed.tech/topics/schema-design.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [database-administration](<https://devfeed.tech/tags/database-administration.md>), [database-schema](<https://devfeed.tech/tags/database-schema.md>), [databases](<https://devfeed.tech/tags/databases.md>), [featured](<https://devfeed.tech/tags/featured.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [semantic-layer](<https://devfeed.tech/tags/semantic-layer.md>)

### AI overview

The guide explains how GraphQL can serve as a semantic layer between API consumers and fragmented backend systems. It recommends designing schemas around stable business concepts and relationships rather than mirroring database structures, so consumers can keep a consistent interface as systems change.

### Source excerpt

One customer, five different database records. Learn how GraphQL's schema can act as a semantic layer -- hiding system complexity behind the language your business actually speaks.... The post Why your schema shouldn't mirror your database (and what to do instead) appeared first on Simple Talk.

## Weaviate security release - Medium severity fix for a cross-collection vector disclosure in nearObject (CVE pending assignment)

DevFeed: [Weaviate security release - Medium severity fix for a cross-collection vector disclosure in nearObject (CVE pending assignment)](<https://devfeed.tech/articles/weaviate-security-release-medium-severity-fix-for-a-cross-collection-vector-disclosure-in-nearobject-cve-pending-assignment-87687.md>)

Original publisher: [Read original article](<https://weaviate.io/blog/weaviate-security-release-nearobject-2026>)

Author: Harneet Singh

Published: 2026-10-15T00:00:00Z

Content type: release

Language: en

Sources: [Weaviate Blog](<https://devfeed.tech/sources/weaviate-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [authorization](<https://devfeed.tech/tags/authorization.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-score](<https://devfeed.tech/tags/cvss-score.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [release](<https://devfeed.tech/tags/release.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Weaviate v1.39.3 fixes an authorization flaw in the GraphQL nearObject operator. A user with access to one collection could use a beacon pointing to an object in another collection to infer that object's vector from search distances, even without permission to read the target collection. The issue affects versions before v1.39.3; Weaviate recommends upgrading and reviewing collection permissions. The CVE assignment is pending, and the article reports no indication of exploitation.

### Source excerpt

Weaviate v1.39.3 fixes a medium-severity authorization issue in the nearObject GraphQL operator.

## TanStack Query vs SWR: How to Choose in Next.js App Router

DevFeed: [TanStack Query vs SWR: How to Choose in Next.js App Router](<https://devfeed.tech/articles/tanstack-query-vs-swr-how-to-choose-in-next-js-app-router-85995.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/tanstack-query-vs-swr-nextjs-app-router/>)

Author: SitePoint Team

Published: 2026-10-13T15:44:38Z

Content type: comparison

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Nextra](<https://devfeed.tech/topics/nextra.md>), [cache-invalidation](<https://devfeed.tech/topics/cache-invalidation.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>)

Tags: [guide](<https://devfeed.tech/tags/guide.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [query](<https://devfeed.tech/tags/query.md>), [react](<https://devfeed.tech/tags/react.md>), [tanstack](<https://devfeed.tech/tags/tanstack.md>), [vs](<https://devfeed.tech/tags/vs.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

A scenario-based comparison of TanStack Query and SWR for Next.js App Router projects. It explains when Server Components can handle initial data directly and demonstrates client-side patterns for filtered queries, cache invalidation, optimistic updates, and provider setup. The guide recommends SWR for simpler read-heavy cases and TanStack Query when applications need more structured mutations, cache control, or debugging tools.

### Source excerpt

A scenario-based guide for React developers comparing TanStack Query and SWR in Next.js App Router, with equivalent Client Component patterns for filtered queries, cache invalidation, and optimistic updates. Continue reading TanStack Query vs SWR: How to Choose in Next.js App Router on SitePoint.

## Introducing GraphOS Router 3.0

DevFeed: [Introducing GraphOS Router 3.0](<https://devfeed.tech/articles/introducing-graphos-router-3-0-66629.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/introducing-graphos-router-3-0>)

Author: Matthew Ratzke

Published: 2026-10-07T11:31:00Z

Content type: release

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphOS](<https://devfeed.tech/topics/graphos.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [apollo-connectors](<https://devfeed.tech/tags/apollo-connectors.md>), [backpressure](<https://devfeed.tech/tags/backpressure.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [graphos](<https://devfeed.tech/tags/graphos.md>), [preview](<https://devfeed.tech/tags/preview.md>), [query](<https://devfeed.tech/tags/query.md>)

### AI overview

GraphOS Router 3.0 is available in Preview with changes to query planning, deployment, request processing, resilience, and GraphQL specification support. The release adds packaged persisted queries, native circuit breaking, and planned distributed rate limiting, alongside a redesigned request pipeline and performance improvements.

### Source excerpt

GraphOS Router 3.0 brings faster query planning, greater deployment control, native circuit breaking, and more. Try it in Preview today.

## Introducing GraphOS Factory

DevFeed: [Introducing GraphOS Factory](<https://devfeed.tech/articles/introducing-graphos-factory-66628.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/introducing-graphos-factory>)

Author: David Walter

Published: 2026-10-07T11:30:50Z

Content type: release

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphOS](<https://devfeed.tech/topics/graphos.md>), [Apollo Connectors](<https://devfeed.tech/topics/apollo-connectors.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [apollo-connectors](<https://devfeed.tech/tags/apollo-connectors.md>), [codex](<https://devfeed.tech/tags/codex.md>), [graphos](<https://devfeed.tech/tags/graphos.md>), [graphql](<https://devfeed.tech/tags/graphql.md>)

### AI overview

GraphOS Factory is an Apollo agent skill that helps engineers turn REST APIs into Apollo Connectors subgraphs through an iterative process. It records design decisions, source materials, and agent findings in Git, then validates changes with composition checks, Connector unit tests, and mocked end-to-end Router runs. The skill is available in preview.

### Source excerpt

GraphOS Factory turns a REST API into a GraphQL subgraph using Apollo Connectors. Learn what GraphOS Factory does, how it works, and how to get started.

## Apollo Connectors v0.4 is Generally Available

DevFeed: [Apollo Connectors v0.4 is Generally Available](<https://devfeed.tech/articles/apollo-connectors-v0-4-is-generally-available-66622.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/apollo-connectors-v0-4-is-generally-available>)

Author: Ben Newman

Published: 2026-10-07T11:30:47Z

Content type: release

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [Apollo Connectors](<https://devfeed.tech/topics/apollo-connectors.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Apollo Federation](<https://devfeed.tech/topics/apollo-federation.md>), [GraphOS](<https://devfeed.tech/topics/graphos.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [apis](<https://devfeed.tech/tags/apis.md>), [apollo-connectors](<https://devfeed.tech/tags/apollo-connectors.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

Apollo Connectors v0.4 is generally available, adding schema support for abstract GraphQL types, inline transformations, virtual connectors without HTTP requests, and a unified mapping grammar. The release also expands static analysis and provides migration guidance for a literal-versus-field-lookup behavior change. The article describes how these capabilities support building and maintaining typed GraphQL integrations for REST and HTTP APIs.

### Source excerpt

Apollo Connectors v0.4 is now generally available. Connect REST and HTTP APIs to GraphQL with no resolver code. See what's new in Apollo Connectors v0.4.

## Introducing Apollo's Next Generation Query Planner

DevFeed: [Introducing Apollo's Next Generation Query Planner](<https://devfeed.tech/articles/introducing-apollo-s-next-generation-query-planner-66624.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/apollos-next-generation-query-planner>)

Author: Taylor Ninesling

Published: 2026-10-07T11:30:00Z

Content type: release

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphOS](<https://devfeed.tech/topics/graphos.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [future of software](<https://devfeed.tech/topics/future-of-software.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [apollo](<https://devfeed.tech/tags/apollo.md>), [beam](<https://devfeed.tech/tags/beam.md>), [bfs](<https://devfeed.tech/tags/bfs.md>), [breadth-first-search](<https://devfeed.tech/tags/breadth-first-search.md>), [depth-first-search](<https://devfeed.tech/tags/depth-first-search.md>), [dfs](<https://devfeed.tech/tags/dfs.md>), [graphos](<https://devfeed.tech/tags/graphos.md>), [graphs](<https://devfeed.tech/tags/graphs.md>), [planner](<https://devfeed.tech/tags/planner.md>), [query-planner](<https://devfeed.tech/tags/query-planner.md>)

### AI overview

Apollo introduces an opt-in incremental query planner for GraphOS Router 3.0. It uses depth-first search, in-place plan mutation, BULB search, and configurable fuel and beam width to bound planning effort and memory. In tests on 200,000 operations across complex customer graphs, it planned each in under two seconds, with up to 300x speedup on the slowest operations and 97% less memory than the existing planner. The article notes that plans can differ and some large operations may produce less optimal plans.

### Source excerpt

GraphOS Router 3.0 introduces new query planner: up to 300x faster planning and 97% less memory on the most complex graphs.

## New fields for SecurityAdvisory GraphQL API

DevFeed: [New fields for SecurityAdvisory GraphQL API](<https://devfeed.tech/articles/new-fields-for-securityadvisory-graphql-api-71381.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-10-02-new-fields-for-securityadvisory-graphql-api>)

Author: Allison

Published: 2026-10-02T13:18:00Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [GitHub API](<https://devfeed.tech/topics/github-api.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [cve](<https://devfeed.tech/tags/cve.md>), [database](<https://devfeed.tech/tags/database.md>), [epss](<https://devfeed.tech/tags/epss.md>), [github](<https://devfeed.tech/tags/github.md>), [github-advisory-database](<https://devfeed.tech/tags/github-advisory-database.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [nvd](<https://devfeed.tech/tags/nvd.md>), [queries](<https://devfeed.tech/tags/queries.md>), [query](<https://devfeed.tech/tags/query.md>), [security](<https://devfeed.tech/tags/security.md>), [triage](<https://devfeed.tech/tags/triage.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

The GitHub GraphQL API now exposes five additional fields on the SecurityAdvisory object and adds severity and withdrawal filters to securityAdvisories. The additive, read-only changes let integrations retrieve and narrow advisory data through GraphQL without falling back to the REST API.

### Source excerpt

You can now read more of the GitHub Advisory Database directly from the GraphQL API without falling back to the REST API. The SecurityAdvisory object gained five new fields: cveId:...

## Tracking Meals and Automating Shopping With an MCP Server

DevFeed: [Tracking Meals and Automating Shopping With an MCP Server](<https://devfeed.tech/articles/tracking-meals-and-automating-shopping-with-an-mcp-server-62187.md>)

Original publisher: [Read original article](<https://philipptheserver.com/posts/daily-meal-tracking-shopping-automation-mcp/>)

Author: Philipp Lehmann (philipp.lehmann@gruppe.ai)

Published: 2026-09-29T23:00:00Z

Content type: article

Language: en

Sources: [Philipp Lehmann](<https://devfeed.tech/sources/philipp-lehmann.md>)

Topics: [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Home Assistant](<https://devfeed.tech/topics/home-assistant.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [api-design](<https://devfeed.tech/tags/api-design.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automation](<https://devfeed.tech/tags/automation.md>), [claude-ai](<https://devfeed.tech/tags/claude-ai.md>), [data](<https://devfeed.tech/tags/data.md>), [fastapi](<https://devfeed.tech/tags/fastapi.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [python](<https://devfeed.tech/tags/python.md>)

### AI overview

The author describes a personal meal tracking and grocery shopping system built around an MCP server. A language model logs meals through the server, while a PWA displays and lets the user correct the results. The article discusses a FastAPI REST API and MCP server, shared use cases, Keycloak authentication, locally cached Open Food Facts lookups, and a rebuild that derives stock from an event journal.

### Source excerpt

An MCP server for meal tracking and grocery shopping automation: planned meals minus live stock, and why the v2 rebuild derives stock from an event journal.

## Apollo Mock: LLM-generated data for your Kotlin applications

DevFeed: [Apollo Mock: LLM-generated data for your Kotlin applications](<https://devfeed.tech/articles/apollo-mock-llm-generated-data-for-your-kotlin-applications-62149.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/apollo-mock-llm-generated-data-for-your-kotlin-applications>)

Author: Martin Bonnin

Published: 2026-09-29T11:30:54Z

Content type: release

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [apollo](<https://devfeed.tech/tags/apollo.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [llm](<https://devfeed.tech/tags/llm.md>), [mock](<https://devfeed.tech/tags/mock.md>)

### AI overview

Apollo Mock generates schema-matching fake entities as JSON from a GraphQL schema, then serves query responses through a small GraphQL server. The LLM runs only during generation, and regenerating after schema changes preserves existing entities and IDs while updating fields.

### Source excerpt

Building or testing a GraphQL client usually means dealing with data you don't control yet: a backend that isn't finished, a staging environment that's flaky or rate-limited, or a dataset that simply doesn't have the edge cases you need for a given test.

## Release Apache APISIX 3.19.0

DevFeed: [Release Apache APISIX 3.19.0](<https://devfeed.tech/articles/release-apache-apisix-3-19-0-60930.md>)

Original publisher: [Read original article](<https://apisix.apache.org/blog/2026/09/28/release-apache-apisix-3.19.0/>)

Author: Abhishek Choudhary

Published: 2026-09-28T00:00:00Z

Content type: release

Language: en

Sources: [Apache APISIX Blog](<https://devfeed.tech/sources/apache-apisix-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Continuous Delivery (CD)](<https://devfeed.tech/topics/continuous-delivery.md>), [canary release](<https://devfeed.tech/topics/canary-release.md>)

Tags: [graphql](<https://devfeed.tech/tags/graphql.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [release](<https://devfeed.tech/tags/release.md>), [tls](<https://devfeed.tech/tags/tls.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

### AI overview

Apache APISIX 3.19.0 adds native WebSocket frame processing, TLS passthrough for stream routes, OpenAPI-to-MCP conversion, upstream slow start, and GraphQL query-cost rate limiting. The release also changes certificate verification and OpenID Connect introspection behavior and includes migration guidance for affected deployments.

### Source excerpt

Apache APISIX 3.19.0 was released on Sep 28, 2026. This release adds native WebSocket processing, TLS stream passthrough, OpenAPI-to-MCP conversion, upstream slow start, GraphQL cost-based rate limiting, and important upgrade considerations.

## How Shopify built a continual learning loop with PyTorch and vLLM

DevFeed: [How Shopify built a continual learning loop with PyTorch and vLLM](<https://devfeed.tech/articles/how-shopify-built-a-continual-learning-loop-with-pytorch-and-vllm-58070.md>)

Original publisher: [Read original article](<https://pytorch.org/blog/how-shopify-built-a-continual-learning-loop-with-pytorch-and-vllm/>)

Author: Cody Mazza-Anthony, Sr. Staff Machine Learning Engineer, @cmazzaanthony & Andrew McNamara, VP Machine Learning, @drewch

Published: 2026-09-22T13:45:18Z

Content type: article

Language: en

Sources: [PyTorch](<https://devfeed.tech/sources/blog-pytorch.md>)

Topics: [Learning](<https://devfeed.tech/topics/learning.md>), [PyTorch](<https://devfeed.tech/topics/pytorch.md>), [vllm](<https://devfeed.tech/topics/vllm.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Frontier Model](<https://devfeed.tech/topics/frontier-model.md>), [Requirements](<https://devfeed.tech/topics/requirements.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Latency](<https://devfeed.tech/topics/latency.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [blog](<https://devfeed.tech/tags/blog.md>), [case-studies](<https://devfeed.tech/tags/case-studies.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [continual-learning](<https://devfeed.tech/tags/continual-learning.md>), [costs](<https://devfeed.tech/tags/costs.md>), [evals](<https://devfeed.tech/tags/evals.md>), [frontier-model](<https://devfeed.tech/tags/frontier-model.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [latency](<https://devfeed.tech/tags/latency.md>), [production](<https://devfeed.tech/tags/production.md>), [pytorch](<https://devfeed.tech/tags/pytorch.md>), [quality](<https://devfeed.tech/tags/quality.md>), [vllm](<https://devfeed.tech/tags/vllm.md>)

### AI overview

This case study explains how Shopify built a continual learning loop for its GraphQL agent using PyTorch and vLLM. The loop uses production failures, quality rubrics, and evaluation data to improve model behavior, while the article reports higher quality, lower latency, and a 96% reduction in serving costs.

### Source excerpt

TL;DR: This case study explores how Shopify compresses production failures into model weights every day, beats frontier-model quality, and cuts serving costs 96% by building a continual learning loop with...

## How Comcast scaled analytics 80x while cutting costs 38% with GraphQL and Amazon S3 Tables

DevFeed: [How Comcast scaled analytics 80x while cutting costs 38% with GraphQL and Amazon S3 Tables](<https://devfeed.tech/articles/how-comcast-scaled-analytics-80x-while-cutting-costs-38-with-graphql-and-amazon-s3-tables-57671.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/how-comcast-scaled-analytics-80x-while-cutting-costs-38-with-graphql-and-amazon-s3-tables/>)

Author: Bimal Gajjar

Published: 2026-09-21T19:16:02Z

Content type: article

Language: en

Sources: [AWS Storage Blog](<https://devfeed.tech/sources/aws-storage-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Amazon S3 Tables](<https://devfeed.tech/topics/amazon-s3-tables.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [data-processing](<https://devfeed.tech/topics/data-processing.md>), [etl](<https://devfeed.tech/topics/etl.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [amazon-s3-tables](<https://devfeed.tech/tags/amazon-s3-tables.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [aws-cloud-storage](<https://devfeed.tech/tags/aws-cloud-storage.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [costs](<https://devfeed.tech/tags/costs.md>), [data-processing](<https://devfeed.tech/tags/data-processing.md>), [etl](<https://devfeed.tech/tags/etl.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [latency](<https://devfeed.tech/tags/latency.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

A Comcast reliability analytics team redesigned its data-access layer with GraphQL and Amazon S3 Tables. The architecture supports substantially higher concurrent request volumes, lowers costs and query latency, and serves multiple data products through a unified schema and simplified ETL pipeline.

### Source excerpt

Customer Story | Amazon S3 Tables - Learn how Comcast redesigned their analytics layer with GraphQL and Amazon S3 Tables, scaling to 80x higher concurrent request volumes while cutting costs by 38% and reducing query latency by 28%. Comcast is building America's largest and most intelligent broadband network with a simple purpose: connect everyone, everywhere [...]

## Siemba brings continuous IDOR testing to production APIs

DevFeed: [Siemba brings continuous IDOR testing to production APIs](<https://devfeed.tech/articles/siemba-brings-continuous-idor-testing-to-production-apis-55814.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/09/21/siemba-idor-automated-testing/>)

Author: Industry News

Published: 2026-09-21T09:39:44Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Security](<https://devfeed.tech/topics/security.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [Postman](<https://devfeed.tech/topics/postman.md>), [Swagger](<https://devfeed.tech/topics/swagger.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>)

Tags: [api-security](<https://devfeed.tech/tags/api-security.md>), [api-vulnerabilities](<https://devfeed.tech/tags/api-vulnerabilities.md>), [apis](<https://devfeed.tech/tags/apis.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [idor](<https://devfeed.tech/tags/idor.md>), [industry-news](<https://devfeed.tech/tags/industry-news.md>), [insecure-direct-object-reference](<https://devfeed.tech/tags/insecure-direct-object-reference.md>), [openapi](<https://devfeed.tech/tags/openapi.md>), [postman](<https://devfeed.tech/tags/postman.md>), [security-testing](<https://devfeed.tech/tags/security-testing.md>), [swagger](<https://devfeed.tech/tags/swagger.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Siemba announced continuous automated testing for insecure direct object reference vulnerabilities in production REST, GraphQL, and SOAP APIs. The platform uses API definitions or collections, authenticated sessions, and response analysis to test identifier-bearing endpoints without requiring source code.

### Source excerpt

Siemba has announced automated testing for insecure direct object reference (IDOR) as part of its API Security Testing capability, which tests REST, GraphQL and SOAP APIs for the vulnerability classes most likely to expose customer data. A 200-endpoint API collection can be tested for IDOR in under an hour. The same coverage has typically taken a human tester days or weeks, working endpoint by endpoint, and produced a written report days after that. Siemba compresses ... More -> The post Siemba brings continuous IDOR testing to production APIs appeared first on Help Net Security.

## EP226: API Concepts Every Software Engineer Should Know

DevFeed: [EP226: API Concepts Every Software Engineer Should Know](<https://devfeed.tech/articles/ep226-api-concepts-every-software-engineer-should-know-55417.md>)

Original publisher: [Read original article](<https://blog.bytebytego.com/p/ep226-api-concepts-every-software>)

Author: ByteByteGo

Published: 2026-09-19T15:31:06Z

Content type: article

Language: en

Sources: [ByteByteGo](<https://devfeed.tech/sources/bytebytego.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [API keys](<https://devfeed.tech/topics/api-keys.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [observability](<https://devfeed.tech/topics/observability.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [caching](<https://devfeed.tech/tags/caching.md>), [e2e](<https://devfeed.tech/tags/e2e.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [grpc](<https://devfeed.tech/tags/grpc.md>), [http](<https://devfeed.tech/tags/http.md>), [json](<https://devfeed.tech/tags/json.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [observability](<https://devfeed.tech/tags/observability.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineer](<https://devfeed.tech/tags/software-engineer.md>)

### AI overview

A system design newsletter explains API design fundamentals, including HTTP methods and status codes, request and response structure, REST, GraphQL, gRPC, webhooks, WebSockets, pagination, versioning, compatibility, authentication, reliability, caching, documentation, observability, and contract testing.

### Source excerpt

Sending a request and reading JSON is one thing. Designing an API that other people can rely on is something where things get complicated.

## Creating Query Components with Apollo

DevFeed: [Creating Query Components with Apollo](<https://devfeed.tech/articles/creating-query-components-with-apollo-27371.md>)

Original publisher: [Read original article](<http://engineering.khanacademy.org/posts/creating-query-components-with-apollo.htm>)

Author: Khan Academy

Published: 2017-06-12T22:00:00Z

Content type: article

Language: en

Sources: [Khan Academy](<https://devfeed.tech/sources/khan-academy.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [apollo-client](<https://devfeed.tech/topics/apollo-client.md>), [React](<https://devfeed.tech/topics/react.md>)

Tags: [apollo](<https://devfeed.tech/tags/apollo.md>), [component](<https://devfeed.tech/tags/component.md>), [components](<https://devfeed.tech/tags/components.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [news](<https://devfeed.tech/tags/news.md>), [query](<https://devfeed.tech/tags/query.md>), [web-frontend](<https://devfeed.tech/tags/web-frontend.md>)

### AI overview

The article presents "Query Components" as a way to separate Apollo and GraphQL query handling from React presentation. Its SchoolsQuery component wraps the query, maps loading, empty, and error states plus school results into props, and passes them to a presentation component through a function-as-children callback. This leaves the presentation focused on rendering and lets the same query support different layouts. The example filters schools by postal code and uses Flow types; a similar wrapper can trigger mutations. The author says the pattern has been useful but is still being evaluated for scale, and suggests it could also work with REST APIs.

### Source excerpt

By Brian Genisio Here at Khan Academy, we've been using GraphQL in several projects with great success. GraphQL ... Read more

[Next page](<https://devfeed.tech/topics/graphql.md?cursor=WyIyMDI2LTA5LTE2VDA5OjQ5OjUzLjE3Mzg0NiswMDowMCIsICI0MDRkMjFkNC0wYjdmLTRkMmQtYjI1OS00M2U3YzlkOGQxMmUiXQ%3D%3D>)