# middleware

Middleware is software that enables system components to communicate and manage data, often serving as an intermediate layer between operating systems and applications.

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

## Edge Computing for IoT-Enabled Smart Cities: A Review of Middleware, Explainable AI, and User Behavior Analytics

DevFeed: [Edge Computing for IoT-Enabled Smart Cities: A Review of Middleware, Explainable AI, and User Behavior Analytics](<https://devfeed.tech/articles/edge-computing-for-iot-enabled-smart-cities-a-review-of-middleware-explainable-ai-and-user-behavior-analytics-142170.md>)

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

Author: Alexandros Gazis, George Vavouras, Nikos E. Mastorakis, Kleanthi Santamouri, Nikolaos Pournaras, Stylianos Pappas

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

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Internet of things](<https://devfeed.tech/topics/iot.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [Big data infrastructure](<https://devfeed.tech/topics/big-data-infrastructure.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [ai](<https://devfeed.tech/tags/ai.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [application](<https://devfeed.tech/tags/application.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [behavior-analytics](<https://devfeed.tech/tags/behavior-analytics.md>), [behavioral-analytics](<https://devfeed.tech/tags/behavioral-analytics.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [case-studies](<https://devfeed.tech/tags/case-studies.md>), [cities](<https://devfeed.tech/tags/cities.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [computing](<https://devfeed.tech/tags/computing.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [edge](<https://devfeed.tech/tags/edge.md>), [edge-computing](<https://devfeed.tech/tags/edge-computing.md>), [explainable-ai](<https://devfeed.tech/tags/explainable-ai.md>), [iot](<https://devfeed.tech/tags/iot.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [review](<https://devfeed.tech/tags/review.md>), [smart-cities](<https://devfeed.tech/tags/smart-cities.md>)

### AI overview

The review maps user-behavior analytics in smart cities across five application domains, including EV charging, energy demand, environmental exposure, and crowd safety. It proposes X-EdgeCity Middleware, an XAI-EdgeSOA framework combining IoT sensing, edge preprocessing, fog coordination, event-driven communication, cloud analytics, explainability, privacy-by-design, and benchmark logging. The aim is to support energy-sensitive and mission-critical urban services where latency, reliability, explainability, and accountability matter. The supplied text is an abstract and does not provide detailed comparisons of case studies or framework performance.

### Source excerpt

arXiv:2611.23310v1 Announce Type: new Abstract: This review looks at cloud-IoT edge middleware for analyzing user behavior in smart cities, with a particular focus on linking behavioral analytics to energy-aware and mission-critical urban services. The topic sits at the crossroads of smart-city platforms, IoT sensing, edge/fog/cloud computing, service-oriented architectures, machine learning, explainable AI, privacy-aware governance, and energy-critical applications such as EV charging, energy demand, environmental exposure, crowd safety, and the operational resilience of urban infrastructure. As such, this paper maps out the main categories of user-behavior data, examines five application domains, compares several case studies, and puts forward a new XAI-EdgeSOA Middleware Framework called X-EdgeCity Middleware. This framework brings together IoT sensing, edge preprocessing, fog coordination, event-driven communication, cloud analytics, XAI explanations, privacy-by-design, and benchmark logging. The goal is to support not just general smart-city applications, but also energy-sensitive or mission-critical services, where latency, reliability, explainability, and accountability have a direct impact on urban safety and continuity of operations.

## Agent fleets drag the messaging layer from afterthought to AI's coordination core

DevFeed: [Agent fleets drag the messaging layer from afterthought to AI's coordination core](<https://devfeed.tech/articles/agent-fleets-drag-the-messaging-layer-from-afterthought-to-ai-s-coordination-core-132510.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/13/data-center-telemetry-runs-nats-graduates-from-cncf-kubeconna/>)

Author: Ryan Stevens

Published: 2026-11-13T17:23:02Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [agent-fleets](<https://devfeed.tech/tags/agent-fleets.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-factory](<https://devfeed.tech/tags/ai-factory.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [andrew-connolly](<https://devfeed.tech/tags/andrew-connolly.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [cloud-native-computing-foundation](<https://devfeed.tech/tags/cloud-native-computing-foundation.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [cloudnativecon](<https://devfeed.tech/tags/cloudnativecon.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [cube-event-coverage](<https://devfeed.tech/tags/cube-event-coverage.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [developer-platforms](<https://devfeed.tech/tags/developer-platforms.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [gpu-infrastructure](<https://devfeed.tech/tags/gpu-infrastructure.md>), [infra](<https://devfeed.tech/tags/infra.md>), [john-furrier](<https://devfeed.tech/tags/john-furrier.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [kubecon-plus-cloudnativecon-na-2026](<https://devfeed.tech/tags/kubecon-plus-cloudnativecon-na-2026.md>), [kubeconna](<https://devfeed.tech/tags/kubeconna.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [rebecca-knight](<https://devfeed.tech/tags/rebecca-knight.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [thecube](<https://devfeed.tech/tags/thecube.md>), [waldemar-quevedo](<https://devfeed.tech/tags/waldemar-quevedo.md>)

### AI overview

NATS is being used to coordinate machine-to-machine traffic as short-lived AI workloads and agent fleets increase connection churn. Its topic-based messaging and super-cluster gateways route traffic across data centers, regions, availability zones and clouds. The article also cites uses for power and cooling telemetry and Nvidia's AI factory event bus. JetStream persistence and the key-value store can preserve state for agent handoffs. These examples and capabilities are attributed to NATS maintainers; the excerpt does not provide performance comparisons or independent evaluation.

### Source excerpt

Data center telemetry, sandboxed AI workloads and fleets of agents are pushing more machine-to-machine traffic through infrastructure than ever before, exposing the limits of messaging systems built for steadier demand. That shift is drawing attention to the Neural Autonomic Transport System, an open-source messaging system that lets applications and services exchange messages by topic. Created [...] The post Agent fleets drag the messaging layer from afterthought to AI's coordination core appeared first on SiliconANGLE.

## From Isolated Protocols to Integrated Pipelines: Benchmarking IoT Communication in the MASA Living Lab

DevFeed: [From Isolated Protocols to Integrated Pipelines: Benchmarking IoT Communication in the MASA Living Lab](<https://devfeed.tech/articles/from-isolated-protocols-to-integrated-pipelines-benchmarking-iot-communication-in-the-masa-living-lab-131581.md>)

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

Author: Antonio Solida, Enrico Rossini, Marcello Pietri, Marco Picone, Carlo Augusto Grazia

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

Content type: news

Language: en

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

Topics: [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [Internet of things](<https://devfeed.tech/topics/iot.md>), [protocols](<https://devfeed.tech/topics/protocols.md>), [Serialization protocols](<https://devfeed.tech/topics/serialization-protocols.md>), [Data transmission](<https://devfeed.tech/topics/data-transmission.md>), [middleware](<https://devfeed.tech/topics/middleware.md>)

Tags: [benchmarking](<https://devfeed.tech/tags/benchmarking.md>), [communication](<https://devfeed.tech/tags/communication.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [iot](<https://devfeed.tech/tags/iot.md>), [jitter](<https://devfeed.tech/tags/jitter.md>), [latency](<https://devfeed.tech/tags/latency.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [protocols](<https://devfeed.tech/tags/protocols.md>), [throughput](<https://devfeed.tech/tags/throughput.md>), [transport](<https://devfeed.tech/tags/transport.md>)

### AI overview

The MASA living-lab benchmark finds that isolated component costs do not reliably predict integrated IoT pipeline performance. It evaluates local processing overhead, end-to-end latency, jitter, throughput, and delivery reliability across combinations of transport, messaging, serialization, and compression. Serialization or compression differences of tens of microseconds can coexist with end-to-end latency differences of several milliseconds, with middleware buffering and transport behavior substantially affecting timing. The authors conclude that stacks should be assessed as integrated pipelines under representative loads, with selection guided by application needs such as network conditions, communication patterns, and reliability requirements.

### Source excerpt

arXiv:2611.15595v1 Announce Type: new Abstract: The performance of real-time IoT communication systems depends not only on individual transport protocols, serialization formats, and data-processing stages, but also on how these components interact within the complete communication pipeline. Selecting an appropriate communication stack is therefore application-dependent and requires considering processing capabilities, network characteristics, communication patterns, and reliability requirements. This paper provides an experimental, evidence-based analysis of these interactions through a controlled benchmark of integrated communication pipelines deployed in the MASA living lab. We jointly evaluate local processing overhead, end-to-end latency, jitter, throughput, and delivery reliability across different combinations of transport, messaging, serialization, and compression mechanisms. Results show that component-level processing costs do not directly predict end-to-end performance. In particular, differences of only tens of microseconds in serialization or compression costs can coexist with several-millisecond differences in end-to-end latency, while middleware buffering and transport behavior substantially affect timing performance. The results demonstrate that communication-stack components should be evaluated as integrated pipelines and under representative operating loads rather than ranked independently.

## Three Lincoln Laboratory technologies receive 2026 R&D 100 Awards

DevFeed: [Three Lincoln Laboratory technologies receive 2026 R&D 100 Awards](<https://devfeed.tech/articles/three-lincoln-laboratory-technologies-receive-2026-r-d-100-awards-131194.md>)

Original publisher: [Read original article](<https://news.mit.edu/2026/lincoln-laboratory-technologies-receive-rd-100-awards-1112>)

Author: Kylie Foy | MIT Lincoln Laboratory

Published: 2026-11-12T21:15:00Z

Content type: news

Language: en

Sources: [MIT AI News](<https://devfeed.tech/sources/mit-ai-news.md>)

Topics: [systems](<https://devfeed.tech/topics/systems.md>), [communications](<https://devfeed.tech/topics/communications.md>), [kasperskyos](<https://devfeed.tech/topics/kasperskyos.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>), [Decoding](<https://devfeed.tech/topics/decoding.md>), [Critical Infrastructure](<https://devfeed.tech/topics/critical-infrastructure.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [PWA](<https://devfeed.tech/topics/pwa.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [5g](<https://devfeed.tech/tags/5g.md>), [5g-interference](<https://devfeed.tech/tags/5g-interference.md>), [6g](<https://devfeed.tech/tags/6g.md>), [addition](<https://devfeed.tech/tags/addition.md>), [after](<https://devfeed.tech/tags/after.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-engine](<https://devfeed.tech/tags/ai-engine.md>), [air](<https://devfeed.tech/tags/air.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [awards](<https://devfeed.tech/tags/awards.md>), [awards-honors-and-fellowships](<https://devfeed.tech/tags/awards-honors-and-fellowships.md>), [binoy-kurien](<https://devfeed.tech/tags/binoy-kurien.md>), [computer-chips](<https://devfeed.tech/tags/computer-chips.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [dod](<https://devfeed.tech/tags/dod.md>), [invention](<https://devfeed.tech/tags/invention.md>), [juliana-furgala](<https://devfeed.tech/tags/juliana-furgala.md>), [laboratory](<https://devfeed.tech/tags/laboratory.md>), [lincoln-laboratory](<https://devfeed.tech/tags/lincoln-laboratory.md>), [magnetite](<https://devfeed.tech/tags/magnetite.md>), [melissa-choi](<https://devfeed.tech/tags/melissa-choi.md>), [military-inventions](<https://devfeed.tech/tags/military-inventions.md>), [military-technology-transfer](<https://devfeed.tech/tags/military-technology-transfer.md>), [mit-intellectual-property](<https://devfeed.tech/tags/mit-intellectual-property.md>), [mit-lincoln-lab](<https://devfeed.tech/tags/mit-lincoln-lab.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [platform](<https://devfeed.tech/tags/platform.md>), [quantum](<https://devfeed.tech/tags/quantum.md>), [quantum-computing](<https://devfeed.tech/tags/quantum-computing.md>), [quantum-enabled-computation-group](<https://devfeed.tech/tags/quantum-enabled-computation-group.md>), [quantum-microsystems](<https://devfeed.tech/tags/quantum-microsystems.md>), [r-d-100-awards](<https://devfeed.tech/tags/r-d-100-awards.md>), [rabindra-das](<https://devfeed.tech/tags/rabindra-das.md>), [satellites](<https://devfeed.tech/tags/satellites.md>), [secure-resilient-systems-and-technology-group](<https://devfeed.tech/tags/secure-resilient-systems-and-technology-group.md>), [system](<https://devfeed.tech/tags/system.md>), [tactical-edge-communications-group](<https://devfeed.tech/tags/tactical-edge-communications-group.md>), [technologies](<https://devfeed.tech/tags/technologies.md>), [u-s-armed-forces](<https://devfeed.tech/tags/u-s-armed-forces.md>)

### AI overview

Lincoln Laboratory's three 2026 R&D 100 Award technologies target embedded-system security, chip interconnection, and 5G interference. Magnetite builds on the formally verified seL4 microkernel, uses Rust services and least-privilege process isolation, and is being integrated into government space and flight platforms. The Quantum Microsystems platform links superconductor and semiconductor chips at wafer scale using AI-guided routing, custom lithographic wiring, and replaceable chiplets to reduce cabling and cryogenic wiring overhead; it is intended for transition to government and commercial foundries. A 5G canceler decodes standardized base-station transmissions, reconstructs interference including multipath distortion, and subtracts it per antenna channel. In tests with an over-the-air Nokia base-station signal, it restored a buried radar signal to within 2 dB of its original signal-to-noise ratio, preserving 89% of interference-free detection range. The Department of War is evaluating the algorithm.

### Source excerpt

A secure operating system, a quantum microsystem platform, and a 5G interference-canceling algorithm are named among the year's most significant innovations.

## WasmLens: Automatic Glass-Box Instrumentation for Composed WebAssembly Applications

DevFeed: [WasmLens: Automatic Glass-Box Instrumentation for Composed WebAssembly Applications](<https://devfeed.tech/articles/wasmlens-automatic-glass-box-instrumentation-for-composed-webassembly-applications-127272.md>)

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

Author: Michiel Van Kenhove, Ewout Verlinde, Jos\\'e Santos, Filip De Turck, Bruno Volckaert, Merlijn Sebrechts

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

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Wasm components](<https://devfeed.tech/topics/wasm-components.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [middleware](<https://devfeed.tech/topics/middleware.md>)

Tags: [binaries](<https://devfeed.tech/tags/binaries.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [composition](<https://devfeed.tech/tags/composition.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [graph](<https://devfeed.tech/tags/graph.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [latency](<https://devfeed.tech/tags/latency.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [observability](<https://devfeed.tech/tags/observability.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [traces](<https://devfeed.tech/tags/traces.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

WasmLens reconstructs end-to-end traces across black-box WebAssembly components by injecting middleware into composed binaries, using instrumentation points derived from the composition graph. Its per-component span-stack tracing design restores parent-child relationships across component boundaries without changing component interfaces or source code; the abstract says this design was adopted upstream. In the reported measurements, mean request latency rose from 238 μs to 454 μs across six boundaries. Increasing the expected crossings from six to eleven raised latency to 514 μs, adding 12 μs per crossing, of which 10.4 μs was attributed to instrumentation. The authors characterize this overhead as additive with composition depth.

### Source excerpt

arXiv:2611.12710v1 Announce Type: new Abstract: The WebAssembly Component Model enables language-independent composition of independently developed components, but complicates observability. Existing tracing support flattens execution hierarchy by attributing every span created inside a composition to a single host-level parent context, so execution across component boundaries cannot be reconstructed. The problem is amplified because components are typically deployed as black boxes whose internals cannot be modified or inspected by the system integrator. To address these limitations, we propose a revised wasi:otel/tracing design in which the runtime maintains a per-component span stack, restoring parent-child relationships across component boundaries without changing component interfaces or source code. This change has since been adopted upstream. Building on this design, we present WasmLens, an automatic instrumentation tool that derives instrumentation points from a composition graph and injects tracing middleware into already composed binaries, yielding end-to-end traces for black-box compositions with no developer configuration. This automatic instrumentation raises mean request latency from $238$ $\mu$s to $454$ $\mu$s across six component boundaries. Raising the expected number of boundary crossings from 6 to 11 further increases latency to $514$ $\mu$s, an incremental cost of $12$ $\mu$s per crossing, of which $10.4$ $\mu$s is attributable to instrumentation. These results show that instrumentation overhead is additive in composition depth rather than proportional to baseline execution time.

## Insert Middleware Before or After Existing Laravel Middleware

DevFeed: [Insert Middleware Before or After Existing Laravel Middleware](<https://devfeed.tech/articles/insert-middleware-before-or-after-existing-laravel-middleware-122129.md>)

Original publisher: [Read original article](<https://laravel-news.com/laravel-middleware-insert-before-after>)

Author: Paul Redmond

Published: 2026-11-06T05:19:34Z

Content type: tutorial

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [middleware](<https://devfeed.tech/topics/middleware.md>)

Tags: [array](<https://devfeed.tech/tags/array.md>), [client](<https://devfeed.tech/tags/client.md>), [insert](<https://devfeed.tech/tags/insert.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [laravel-tutorials](<https://devfeed.tech/tags/laravel-tutorials.md>), [locale](<https://devfeed.tech/tags/locale.md>), [middleware](<https://devfeed.tech/tags/middleware.md>)

### AI overview

Laravel 13.40 adds `insertBefore()` and `insertAfter()` for the global middleware stack, plus `insertBeforeInGroup()` and `insertAfterInGroup()` for named groups. Each places middleware beside a specified class while preserving the rest of the stack. This lets session-dependent locale middleware run after `StartSession` but before `SubstituteBindings`, and IP checks run after `TrustProxies` so `$request->ip()` reflects the client address. Previously, prepend/append could not meet those ordering needs; redefining a group could drift from framework changes or omit additions such as `auth.session`. The excerpt also says `replace()` and `replaceInGroup()` now accept arrays, including through `web()` and `api()` replacement arguments.

### Source excerpt

Laravel 13.40 adds insertBefore() and insertAfter() to place middleware next to built-in ones like TrustProxies and StartSession without redefining the stack. The post Insert Middleware Before or After Existing Laravel Middleware appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## The middle layer will make or break enterprise AI agents

DevFeed: [The middle layer will make or break enterprise AI agents](<https://devfeed.tech/articles/the-middle-layer-will-make-or-break-enterprise-ai-agents-112549.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4242744/the-middle-layer-will-make-or-break-enterprise-ai-agents.html>)

Author: Bob Venero

Published: 2026-11-02T09:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [API Economy](<https://devfeed.tech/topics/api-economy.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [AI Models](<https://devfeed.tech/topics/ai-models.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [apis](<https://devfeed.tech/tags/apis.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-enterprise-architecture](<https://devfeed.tech/tags/artificial-intelligence-enterprise-architecture.md>), [business](<https://devfeed.tech/tags/business.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [cios](<https://devfeed.tech/tags/cios.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [data](<https://devfeed.tech/tags/data.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [enterprise-architecture](<https://devfeed.tech/tags/enterprise-architecture.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [environment](<https://devfeed.tech/tags/environment.md>), [example](<https://devfeed.tech/tags/example.md>), [execution](<https://devfeed.tech/tags/execution.md>), [financial](<https://devfeed.tech/tags/financial.md>), [financial-data](<https://devfeed.tech/tags/financial-data.md>), [financial-services](<https://devfeed.tech/tags/financial-services.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-management](<https://devfeed.tech/tags/identity-management.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

The article argues that enterprise agents' value depends on the integration and engineering layer that connects model reasoning to reliable action across business systems. For precise calculations, it recommends deterministic code such as Python or Node.js, with the model interpreting the results. Agents also need dependable APIs or MCPs, accessible data, documented business logic, identity management and connections to systems of record. MCP adoption does not remove the need for API/MCP management. Organizations with point-to-point technical debt may need integration modernization; agents expose gaps that people have been bridging manually, while one-off fixes can add further complexity. Because agent behavior is probabilistic and can vary with context, enterprise use requires dedicated engineering for testing, monitoring, maintenance, observability and recovery. The excerpt identifies four capabilities for scaling: mature integration practices, dedicated software engineering teams, strong technical leadership and a culture comfortable with software, data and calculated risk. Leaders should also distinguish workflows suited to agents from those better handled by conventional or,א

### Source excerpt

The hype around AI agents and the models that power them is warranted. But while they can give organizations a real competitive advantage, in reality, how much value they deliver ultimately depends on something much less glamorous: the middleware and integrations that connect agents to systems across enterprise workflows. Enterprises have used AI in various forms for decades, but agents represent a significant shift in how we put AI to work and what we ask it to do. The first phase of AI largely focused on generating, summarizing, analyzing and recommending information. Agents go a step further by executing actions and this is where the middle layer often gets overlooked. Without the right APIs, MCPs, data streams, tools, deterministic logic, identity management and systems of record, agents and models essentially operate in a sandbox. As enterprises adopt agents into real-world workflows, the question CIOs need to ask isn't simply, "Which AI agent should we deploy next?" It's, "Can our enterprise faithfully support software action on our behalf?" The model is becoming the commodity layer After decades of leading a technology organization and countless implementations, I've seen firsthand how important it is to align technology with the business problems it is meant to solve. When it comes to AI agents, one of the biggest mistakes I see organizations make is setting unrealistic expectations for how a model will operate within their existing enterprise environment. AI agents and models are often touted for what they can accomplish, which naturally focuses attention on their reasoning and execution capabilities. But we cannot simply layer them onto existing workflows and expect them to make decisions or take consistent, repeatable action reliably. Financial services make for a great example of this. Think about an investing agent who evaluates companies using financial data. When they need it to calculate something precise, like a company's cash burn ratio or runway,

## Human--AI Interactions as First-Class Data: A Formal Interaction Model and Runtime for Explainable AI Collaboration

DevFeed: [Human--AI Interactions as First-Class Data: A Formal Interaction Model and Runtime for Explainable AI Collaboration](<https://devfeed.tech/articles/human-ai-interactions-as-first-class-data-a-formal-interaction-model-and-runtime-for-explainable-ai-collaboration-108254.md>)

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

Author: Michela Taufer, Kin Ng, Ian Lumsden, Aashish Pandey, Rajasi Gore, Angelina Ju, Sukanya Moudgalya, Ewa Deelman, Sai Swaminathan

Published: 2026-10-30T04:00:00Z

Content type: article

Language: en

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

Topics: [human computer interaction](<https://devfeed.tech/topics/human-computer-interaction.md>), [Human-AI evaluation](<https://devfeed.tech/topics/human-ai-evaluation.md>), [recording](<https://devfeed.tech/topics/recording.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [jupyterlab](<https://devfeed.tech/topics/jupyterlab.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistants](<https://devfeed.tech/tags/ai-assistants.md>), [ai-collaboration](<https://devfeed.tech/tags/ai-collaboration.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [behavioral-analysis](<https://devfeed.tech/tags/behavioral-analysis.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [context](<https://devfeed.tech/tags/context.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-hc](<https://devfeed.tech/tags/cs-hc.md>), [data](<https://devfeed.tech/tags/data.md>), [data-class](<https://devfeed.tech/tags/data-class.md>), [data-products](<https://devfeed.tech/tags/data-products.md>), [engagement](<https://devfeed.tech/tags/engagement.md>), [execution](<https://devfeed.tech/tags/execution.md>), [explainability](<https://devfeed.tech/tags/explainability.md>), [explainable-ai](<https://devfeed.tech/tags/explainable-ai.md>), [formal](<https://devfeed.tech/tags/formal.md>), [interaction](<https://devfeed.tech/tags/interaction.md>), [model](<https://devfeed.tech/tags/model.md>), [runtime](<https://devfeed.tech/tags/runtime.md>)

### AI overview

HAIDL represents human-AI interactions as structured data, recording computational context, requests and prompt payloads, responses, feedback, provenance, problem context, and model metadata. Its JupyterLab middleware, HAIDL-X, captures user-bot state, builds contextualized prompts, connects to AI providers, collects feedback, and stores interactions in a repository. A learning layer combines these records with notebook execution traces to derive reproducible measures such as engagement, performance, help-seeking, error-oriented use, and learning personas. The abstract presents this as a foundation for querying, replaying, and analyzing collaboration; it does not report evaluation results or compare providers.

### Source excerpt

arXiv:2610.40006v1 Announce Type: new Abstract: AI assistants are increasingly embedded in computational notebooks, scientific workflows, software engineering tools, and learning systems, yet human-AI interactions are often treated as transient prompt-response exchanges rather than durable data products, hindering reproducibility, explainability, replay, behavioral analysis, and adaptive AI support. We argue that these interactions form a new data class requiring formal representation and introduce the Human-AI Interaction Description Language (HAIDL), a formal interaction model with a Backus-Naur Form-inspired concrete syntax. HAIDL encodes each interaction as a structured object capturing computational context, user request, prompt payload, AI response, feedback, problem context, provenance, and model metadata. We integrate this vision into HAIDL-X, a middleware for JupyterLab that instantiates HAIDL by capturing user-bot state, building contextualized prompts, interfacing with AI providers, collecting feedback, and storing interactions in a repository. We add a learning layer over HAIDL that maps interaction objects and notebook execution traces into reproducible measures of user behavior, including engagement, performance, help-seeking, error-oriented use, and learning personas. HAIDL-X provides a foundation for treating human-AI collaboration as structured, queryable, replayable, analyzable data.

## CVE-2026-112362 - @fastify/express vulnerable to path-scoped middleware bypass via absolute-form request targets

DevFeed: [CVE-2026-112362 - @fastify/express vulnerable to path-scoped middleware bypass via absolute-form request targets](<https://devfeed.tech/articles/cve-2026-112362-fastify-express-vulnerable-to-path-scoped-middleware-bypass-via-absolute-form-request-targets-102067.md>)

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

Author: CVEFEED.io

Published: 2026-10-27T12:17:04Z

Content type: article

Language: en

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

Topics: [Fastify](<https://devfeed.tech/topics/fastify.md>), [Express](<https://devfeed.tech/topics/express.md>), [middleware](<https://devfeed.tech/topics/middleware.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [absolute](<https://devfeed.tech/tags/absolute.md>), [admin](<https://devfeed.tech/tags/admin.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-112362](<https://devfeed.tech/tags/cve-2026-112362.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [express](<https://devfeed.tech/tags/express.md>), [fastify](<https://devfeed.tech/tags/fastify.md>), [fastify-express](<https://devfeed.tech/tags/fastify-express.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [handler](<https://devfeed.tech/tags/handler.md>), [issue](<https://devfeed.tech/tags/issue.md>), [layer](<https://devfeed.tech/tags/layer.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [option](<https://devfeed.tech/tags/option.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [request](<https://devfeed.tech/tags/request.md>)

### AI overview

In @fastify/express 4.0.5-4.0.8, enabling Fastify's non-default ignoreDuplicateSlashes option can let an absolute-form request target reach a scoped route after slash normalization while bypassing the path-scoped Express middleware for that route. This may skip authentication, authorization, or rate limiting; the description says an unauthenticated attacker can exploit the condition. Upgrade to 4.0.9 or later. As a workaround, enforce authentication in a Fastify hook such as preHandler, or leave ignoreDuplicateSlashes at its default.

### Source excerpt

CVE ID :CVE-2026-112362 Published : Oct. 27, 2026, 12:17 p.m. | 28 minutes ago Description :@fastify/express is a Fastify plugin that runs Express middleware inside Fastify. In versions 4.0.5 through 4.0.8, when Fastify runs with the non-default ignoreDuplicateSlashes option enabled, the plugin matches path-scoped Express middleware against a URL whose duplicate-slash normalization has also collapsed the separator after an absolute-form request target's scheme, so Fastify's router resolves the request to the scoped path and runs the handler while the Express layer no longer sees that path. As a result, a request using an absolute-form target can reach a handler on a scoped route such as an admin path while the middleware for authentication, authorization, or rate limiting is skipped. An unauthenticated attacker needs only the non-default ignoreDuplicateSlashes option to be enabled. The issue is fixed in @fastify/express 4.0.9, and users should upgrade to 4.0.9 or later. As a workaround, enforce authentication in a Fastify hook such as preHandler that runs after the router resolves the request, or leave ignoreDuplicateSlashes at its default. Severity: 9.1 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Failure-Resilient and Verifiable Distributed Approximate Nearest-Neighbor Retrieval

DevFeed: [Failure-Resilient and Verifiable Distributed Approximate Nearest-Neighbor Retrieval](<https://devfeed.tech/articles/failure-resilient-and-verifiable-distributed-approximate-nearest-neighbor-retrieval-101621.md>)

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

Author: Abdullah Al-Mamun

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

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>)

Topics: [ann](<https://devfeed.tech/topics/ann.md>), [distributed algorithm](<https://devfeed.tech/topics/distributed-algorithm.md>), [trust](<https://devfeed.tech/topics/trust.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [information retrieval](<https://devfeed.tech/topics/information-retrieval.md>), [middleware](<https://devfeed.tech/topics/middleware.md>)

Tags: [000](<https://devfeed.tech/tags/000.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [ann](<https://devfeed.tech/tags/ann.md>), [applications](<https://devfeed.tech/tags/applications.md>), [approximate-nearest-neighbor](<https://devfeed.tech/tags/approximate-nearest-neighbor.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attack](<https://devfeed.tech/tags/attack.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [databases](<https://devfeed.tech/tags/databases.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [failure](<https://devfeed.tech/tags/failure.md>), [nearest-neighbor](<https://devfeed.tech/tags/nearest-neighbor.md>), [retrieval](<https://devfeed.tech/tags/retrieval.md>)

### AI overview

TrustANN adds query-level trust checks to distributed approximate nearest-neighbor retrieval without changing the underlying ANN algorithm. TrustBind checks authenticated, consistent evidence from independent replica failure domains; CoordShift prepares reusable coordination epochs asynchronously; and AvailGuard performs bounded recovery when replicas are unavailable, stale, or conflicting. A query is marked Trusted only when each relevant shard has sufficient independent evidence; otherwise it is returned as Unverified. In an AWS deployment using distributed FAISS HNSW, two-of-three replica verification reduced success of the tested Byzantine retrieval attack from 1.000 to 0.000, with a 9.36% increase in clean p95 latency. Trusted retrieval was maintained through 33% replica failures; when evidence was insufficient, TrustANN returned Unverified.

### Source excerpt

arXiv:2610.34608v1 Announce Type: new Abstract: Distributed vector databases increasingly support security-sensitive applications, yet existing systems primarily protect index integrity or replica availability rather than the trustworthiness of retrieved results. Consequently, a compromised replica can return a plausible but manipulated result that remains cryptographically valid, while conventional replication and Byzantine defenses do not directly establish whether the retrieved results are trustworthy. We present TrustANN, a middleware layer that provides query-level trust for distributed approximate nearest-neighbor (ANN) retrieval without modifying the underlying ANN algorithm. TrustANN introduces three complementary protocols: TrustBind, which verifies retrieval trust from authenticated, consistent, and failure-domain-independent replica evidence; CoordShift, which asynchronously constructs reusable coordination epochs outside the query critical path; and AvailGuard, which performs bounded recovery when replicas are unavailable, stale, or conflicting while preserving the trust criterion. Queries are marked Trusted only when sufficient independent evidence exists for every relevant shard; otherwise, TrustANN returns Unverified. On an AWS deployment using distributed FAISS HNSW, TrustANN reduces retrieval attack success rate from 1.000 to 0.000 under the tested Byzantine-retrieval attack with two-of-three replica verification. The verification layer increases clean p95 latency by only 9.36%. Under replica crashes, TrustANN maintains trusted retrieval through 33% failures and correctly returns Unverified when sufficient evidence is unavailable.

## Laravel Read Replicas: Prevent Stale Reads After a Write

DevFeed: [Laravel Read Replicas: Prevent Stale Reads After a Write](<https://devfeed.tech/articles/laravel-read-replicas-prevent-stale-reads-after-a-write-97626.md>)

Original publisher: [Read original article](<https://laravel-news.com/laravel-prevent-stale-database-reads>)

Author: Paul Redmond

Published: 2026-10-22T23:20:21Z

Content type: tutorial

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [read-replica](<https://devfeed.tech/topics/read-replica.md>), [Laravel](<https://devfeed.tech/topics/laravel.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [Eloquent ORM](<https://devfeed.tech/topics/eloquent.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [lag](<https://devfeed.tech/tags/lag.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [news](<https://devfeed.tech/tags/news.md>), [prevent](<https://devfeed.tech/tags/prevent.md>), [read-replicas](<https://devfeed.tech/tags/read-replicas.md>), [replica](<https://devfeed.tech/tags/replica.md>), [replica-lag](<https://devfeed.tech/tags/replica-lag.md>), [write](<https://devfeed.tech/tags/write.md>)

### AI overview

Laravel 13.38 adds `PreventStaleDatabaseReads` to address replica lag across separate requests: after a request modifies records, the middleware stores a session timestamp, then routes reads to the write server on subsequent requests for a configurable window (two seconds by default). Set the window to cover the longest lag seen in replica metrics; a shorter window can still expose stale data. This differs from the `sticky` connection option, which only keeps reads on the writer for the remainder of the same request. For code that needs fresh reads regardless of the user's recent writes, `DB::usingWritePdo()` routes all reads inside a callback to the writer, including relationship queries; the connection returns to its prior setting when the callback finishes or throws. Queries in a transaction already use the writer. The article also notes that middleware tests should avoid `RefreshDatabase`, whose transaction would make queries use the writer even without the middleware.

### Source excerpt

Laravel's PreventStaleDatabaseReads middleware keeps a user's reads on the write database after they save, so read replica lag doesn't show them old data. The post Laravel Read Replicas: Prevent Stale Reads After a Write appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## Routing Middleware now supports Python

DevFeed: [Routing Middleware now supports Python](<https://devfeed.tech/articles/routing-middleware-now-supports-python-92975.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/routing-middleware-now-supports-python>)

Author: Daniel Park

Published: 2026-10-21T16:36:23.454672Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [middleware](<https://devfeed.tech/topics/middleware.md>), [Python](<https://devfeed.tech/topics/python.md>), [ASGI](<https://devfeed.tech/topics/asgi.md>), [Django](<https://devfeed.tech/topics/django.md>), [FastAPI](<https://devfeed.tech/topics/fastapi.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [django](<https://devfeed.tech/tags/django.md>), [fastapi](<https://devfeed.tech/tags/fastapi.md>), [flask](<https://devfeed.tech/tags/flask.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [package](<https://devfeed.tech/tags/package.md>), [packages](<https://devfeed.tech/tags/packages.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [python](<https://devfeed.tech/tags/python.md>), [redirect](<https://devfeed.tech/tags/redirect.md>), [rewrite](<https://devfeed.tech/tags/rewrite.md>), [route](<https://devfeed.tech/tags/route.md>), [routing](<https://devfeed.tech/tags/routing.md>), [utilities](<https://devfeed.tech/tags/utilities.md>), [uv](<https://devfeed.tech/tags/uv.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Python routing middleware runs before the main app and can rewrite, redirect, or answer requests. Configure the `proxy` entrypoint in `vercel.toml` to point to an ASGI or WSGI app that runs separately, and put its imported packages in the `vercel.proxy` dependency group in `pyproject.toml` (for example, install `vercel-proxy` with `uv add --group vercel.proxy vercel-proxy`). The package includes a `Proxy` app for path-based routing; handlers can, for example, redirect a legacy blog path or continue an API request with an added header. Requests without a matching route continue to the main app unchanged.

### Source excerpt

You can now write routing middleware in Python for FastAPI, Flask, Django, and other Python frameworks. It runs before requests reach your app, and can rewrite, redirect, or answer them. To set it up, point the proxy entrypoint in vercel.toml at your proxy: Your middleware is an ASGI or WSGI app that runs separately from your main app, with only the packages in the vercel.proxy dependency group of your pyproject.toml. Add the packages your middleware imports to that group: The vercel-proxy package provides utilities for writing routing middleware on Vercel, including a Proxy app that routes requests by path: Requests that match no route continue to your app unchanged. For more information, see the Routing Middleware Python reference. Read more

## Build Your Own MCP Server or Buy an Execution Layer

DevFeed: [Build Your Own MCP Server or Buy an Execution Layer](<https://devfeed.tech/articles/build-your-own-mcp-server-or-buy-an-execution-layer-92495.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/build-vs-buy-mcp-server>)

Author: Swytchcode Team

Published: 2026-10-21T09:53:12.592027Z

Content type: comparison

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [build vs buy database solutions](<https://devfeed.tech/topics/build-vs-buy-database-solutions.md>), [Tech Debt](<https://devfeed.tech/topics/tech-debt.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [architecture-components](<https://devfeed.tech/topics/architecture-components.md>)

Tags: [agent-frameworks](<https://devfeed.tech/tags/agent-frameworks.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [argument](<https://devfeed.tech/tags/argument.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [auth](<https://devfeed.tech/tags/auth.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [custom](<https://devfeed.tech/tags/custom.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [execution](<https://devfeed.tech/tags/execution.md>), [governance](<https://devfeed.tech/tags/governance.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>)

### AI overview

The article argues that maintaining the governance layer beneath an MCP server--credential handling, safe retries, policy, audit logs, and adapting to API and framework changes--can become a continuing cost beyond the initial connector work. It says a hand-built server can suit one or two internal APIs used by a single agent without external compliance pressure or planned growth. A centrally maintained execution layer is presented as useful when providers, agent frameworks, or security requirements expand; it applies policy, credential injection, retries, and auditing across integrations. The article says custom REST integrations can be added from OpenAPI specs or Postman collections, and that migration from a hand-built server is easier when tool definitions are kept clean.

### Source excerpt

The real cost line isn't the connectors. It's the maintenance of the stitching layer underneath them, and that bill doesn't stop arriving after launch.

## Supabase Middleware: composable, reusable middleware for Web Fetch handlers

DevFeed: [Supabase Middleware: composable, reusable middleware for Web Fetch handlers](<https://devfeed.tech/articles/supabase-middleware-composable-reusable-middleware-for-web-fetch-handlers-88789.md>)

Original publisher: [Read original article](<https://supabase.com/blog/supabase-middleware>)

Author: Tomás Pozo; Katerina Skroumpelou

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

Content type: article

Language: en

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

Topics: [middleware](<https://devfeed.tech/topics/middleware.md>), [Supabase](<https://devfeed.tech/topics/supabase.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>)

Tags: [middleware](<https://devfeed.tech/tags/middleware.md>), [supabase](<https://devfeed.tech/tags/supabase.md>), [type-safe](<https://devfeed.tech/tags/type-safe.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Supabase introduces @supabase/middleware, a TypeScript library for composing reusable, type-safe middleware for Web Fetch handlers. Pipelines can run across fetch-compatible runtimes and integrate with frameworks through small bridge files. The article shows middleware for CORS, JWT claims, scoped Supabase clients, OAuth discovery for MCP servers, and custom request logic.

### Source excerpt

Type-safe, composable middleware for Web Fetch handlers. Write it once, use it on any fetch runtime or inside a framework.

## One SoC. Two worlds. Zero compromise: How Red Hat In-Vehicle Operating System and DXC AMBER come together in a mixed-criticality software-defined vehicle solution

DevFeed: [One SoC. Two worlds. Zero compromise: How Red Hat In-Vehicle Operating System and DXC AMBER come together in a mixed-criticality software-defined vehicle solution](<https://devfeed.tech/articles/one-soc-two-worlds-zero-compromise-how-red-hat-in-vehicle-operating-system-and-dxc-amber-come-together-in-a-mixed-criticality-software-defined-vehicle-solution-86669.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/one-soc-two-worlds-zero-compromise-how-red-hat-vehicle-operating-system-and-dxc-amber-come-together-mixed-criticality-software-defined-vehicle-solution>)

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

Content type: article

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [systems](<https://devfeed.tech/topics/systems.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Android](<https://devfeed.tech/topics/android.md>), [Operating system](<https://devfeed.tech/topics/operating-system.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [redhat](<https://devfeed.tech/topics/redhat.md>)

Tags: [adas](<https://devfeed.tech/tags/adas.md>), [android-automotive-os](<https://devfeed.tech/tags/android-automotive-os.md>), [automotive](<https://devfeed.tech/tags/automotive.md>), [automotive-industry](<https://devfeed.tech/tags/automotive-industry.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [linux](<https://devfeed.tech/tags/linux.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [platform](<https://devfeed.tech/tags/platform.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

Red Hat and DXC are demonstrating a software-defined vehicle platform that combines Android Automotive OS, AD/ADAS applications and an instrument cluster on one compute platform. The architecture uses a Type 1 hypervisor to isolate operating-system environments and containers to separate safety-related workloads within Red Hat In-Vehicle Operating System. The article also describes DXC AMBER middleware and the ASIL-B certification context for the Linux platform.

### Source excerpt

At ELIV 2026 in Baden-Baden, Red Hat and DXC are showcasing a software-defined vehicle (SDV) platform that brings together AD/ADAS and digital cockpit workloads on a single high-performance compute platform, with Red Hat In-Vehicle Operating System providing an ISO 26262 ASIL-B certified Linux foundation for the safety-relevant software domain.The automotive industry has been exploring ADAS and IVI convergence for years. In collaboration with DXC, we are showcasing a production-grade implementation, running Android Automotive OS, an ASIL-B instrument cluster and AD/ADAS applications side by si

## Skip sending request bodies to Routing Middleware

DevFeed: [Skip sending request bodies to Routing Middleware](<https://devfeed.tech/articles/skip-sending-request-bodies-to-routing-middleware-77475.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/skip-sending-request-bodies-to-routing-middleware>)

Author: Shohei Maeda

Published: 2026-10-08T16:05:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [request management](<https://devfeed.tech/topics/request-management.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [project release](<https://devfeed.tech/topics/project-release.md>)

Tags: [middleware](<https://devfeed.tech/tags/middleware.md>), [request](<https://devfeed.tech/tags/request.md>), [routing](<https://devfeed.tech/tags/routing.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel adds a `skipMiddlewareRequestBody` option to stop forwarding client request bodies to Routing Middleware. This can reduce Fast Origin Transfer usage and improve time to first byte for requests with large bodies, provided the middleware does not need to read the body. Vercel Functions and rewrite targets still receive it. The setting can be enabled in `vercel.json` or `vercel.ts`, and takes effect after redeployment.

### Source excerpt

You can now skip sending client request bodies to Routing Middleware with skipMiddlewareRequestBody. This reduces incoming Fast Origin Transfer usage for middleware invocations and can improve time to first byte, especially for requests with large bodies. Enable this option only if your Routing Middleware doesn't read request bodies. Vercel Functions and rewrite targets still receive the body, so you can read and process it there. Set skipMiddlewareRequestBody to true in your project's JSON configuration file, vercel.json: If you use a TypeScript configuration file, add the same setting to vercel.ts instead. This example assumes @vercel/config is installed: Redeploy your project for the change to take effect. The option defaults to false, so existing projects are unchanged unless you enable it. Read more in the skipMiddlewareRequestBody documentation. Read more

## Middleware: An Architecture Pattern Across Stacks and Frameworks

DevFeed: [Middleware: An Architecture Pattern Across Stacks and Frameworks](<https://devfeed.tech/articles/middleware-an-architecture-pattern-across-stacks-and-frameworks-66757.md>)

Original publisher: [Read original article](<https://hackernoon.com/middleware-an-architecture-pattern-across-stacks-and-frameworks?source=rss>)

Author: Alex Shevtsov

Published: 2026-10-07T12:30:02Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [middleware](<https://devfeed.tech/topics/middleware.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [api](<https://devfeed.tech/tags/api.md>), [api-design](<https://devfeed.tech/tags/api-design.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-pattern](<https://devfeed.tech/tags/architecture-pattern.md>), [article](<https://devfeed.tech/tags/article.md>), [async](<https://devfeed.tech/tags/async.md>), [class](<https://devfeed.tech/tags/class.md>), [client](<https://devfeed.tech/tags/client.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [design-patterns](<https://devfeed.tech/tags/design-patterns.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [pattern](<https://devfeed.tech/tags/pattern.md>), [programming](<https://devfeed.tech/tags/programming.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [web-development](<https://devfeed.tech/tags/web-development.md>)

### AI overview

This tutorial explains middleware as a reusable function pipeline used across frontend and backend frameworks. It compares implementations in Koa, FastAPI, and Redux, shows how middleware composes around a handler, and describes where the pattern fits, when a workflow is more appropriate, and design rules for middleware that passes results, stops early, and shares typed state.

### Source excerpt

Middleware as an architecture pattern: the same idea in Express, FastAPI and Redux, how it relates to Chain of Responsibility, and where it fits in your code.

## How to build a user dashboard with login and booking in Webflow

DevFeed: [How to build a user dashboard with login and booking in Webflow](<https://devfeed.tech/articles/how-to-build-a-user-dashboard-with-login-and-booking-in-webflow-59989.md>)

Original publisher: [Read original article](<https://webflowmarketingmain.com/blog/user-dashboard-login-booking-webflow>)

Author: Ismail Ajagbe

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

Content type: tutorial

Language: en

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

Topics: [Next.js](<https://devfeed.tech/topics/next-js.md>), [webflow](<https://devfeed.tech/topics/webflow.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [npm](<https://devfeed.tech/topics/npm.md>), [passwords](<https://devfeed.tech/topics/passwords.md>), [client](<https://devfeed.tech/topics/client.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [JSON](<https://devfeed.tech/topics/json.md>)

Tags: [client](<https://devfeed.tech/tags/client.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [guides](<https://devfeed.tech/tags/guides.md>), [http](<https://devfeed.tech/tags/http.md>), [json](<https://devfeed.tech/tags/json.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [password](<https://devfeed.tech/tags/password.md>), [webflow](<https://devfeed.tech/tags/webflow.md>)

### AI overview

A tutorial for building a Next.js login and booking dashboard mounted on a Webflow Cloud site. It explains shared signed-cookie identity checks, route handlers, deployment prerequisites, and the runtime compatibility constraint involving Next.js 15 and Webflow Cloud middleware.

### Source excerpt

Learn how to build a Next.js login and booking dashboard on Webflow Cloud.

## How to add user authentication for Webflow site visitors (Webflow Cloud)

DevFeed: [How to add user authentication for Webflow site visitors (Webflow Cloud)](<https://devfeed.tech/articles/how-to-add-user-authentication-for-webflow-site-visitors-webflow-cloud-59988.md>)

Original publisher: [Read original article](<https://webflowmarketingmain.com/blog/user-authentication-webflow-site-visitors>)

Author: Ismail Ajagbe

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

Content type: tutorial

Language: en

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

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [webflow](<https://devfeed.tech/topics/webflow.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [passwords](<https://devfeed.tech/topics/passwords.md>), [.env](<https://devfeed.tech/topics/dotenv.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [build](<https://devfeed.tech/tags/build.md>), [cloudflare-workers](<https://devfeed.tech/tags/cloudflare-workers.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [environment](<https://devfeed.tech/tags/environment.md>), [guides](<https://devfeed.tech/tags/guides.md>), [js](<https://devfeed.tech/tags/js.md>), [login](<https://devfeed.tech/tags/login.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [webflow](<https://devfeed.tech/tags/webflow.md>)

### AI overview

A tutorial for building a Webflow Cloud members area with Next.js middleware, HMAC-signed session cookies, protected mounted pages, and publicly accessible Designer content. It also covers credential storage, environment secrets, deployment constraints, and when to use an identity provider.

### Source excerpt

Learn how to build a members-area login on Webflow Cloud with a signed session cookie and Next.js middleware.

## How to add Firebase user authentication to a Webflow membership site

DevFeed: [How to add Firebase user authentication to a Webflow membership site](<https://devfeed.tech/articles/how-to-add-firebase-user-authentication-to-a-webflow-membership-site-59982.md>)

Original publisher: [Read original article](<https://webflowmarketingmain.com/blog/firebase-authentication-webflow-membership>)

Author: Ismail Ajagbe

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

Content type: tutorial

Language: en

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

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Firebase](<https://devfeed.tech/topics/firebase.md>), [webflow](<https://devfeed.tech/topics/webflow.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cloudflare-workers](<https://devfeed.tech/tags/cloudflare-workers.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [guides](<https://devfeed.tech/tags/guides.md>), [login](<https://devfeed.tech/tags/login.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [token](<https://devfeed.tech/tags/token.md>), [webflow](<https://devfeed.tech/tags/webflow.md>)

### AI overview

A tutorial on building a Firebase-authenticated members area on Webflow Cloud using Next.js and Cloudflare Workers. It covers browser sign-in, server-side ID-token verification, cookie-based sessions, and middleware-protected routes.

### Source excerpt

Learn how to build a Firebase-authenticated members area on Webflow Cloud with Next.js.

## Laravel AI SDK 1.0 Adds Classification and Tool Approvals

DevFeed: [Laravel AI SDK 1.0 Adds Classification and Tool Approvals](<https://devfeed.tech/articles/laravel-ai-sdk-1-0-adds-classification-and-tool-approvals-58963.md>)

Original publisher: [Read original article](<https://laravel-news.com/laravel-ai-sdk-1-0>)

Author: Eric L. Barnes

Published: 2026-09-23T14:46:41Z

Content type: release

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [vercel ai sdk](<https://devfeed.tech/topics/vercel-ai-sdk.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-sdk](<https://devfeed.tech/tags/ai-sdk.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [news](<https://devfeed.tech/tags/news.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [streaming](<https://devfeed.tech/tags/streaming.md>)

### AI overview

Laravel AI SDK 1.0 adds classification, support for Vercel Chat and AG-UI streaming protocols, approvable tool calls, conversation storage changes, and per-step agent middleware. The release includes breaking changes and supports Jev, TypeSafe, and OpenRouter for classification.

### Source excerpt

Laravel AI SDK 1.0 is out with Jev classification, Vercel Chat and AG-UI streaming, approvable tool calls, and per-step agent middleware. The post Laravel AI SDK 1.0 Adds Classification and Tool Approvals appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## Introducing Laravel AI SDK v1.0

DevFeed: [Introducing Laravel AI SDK v1.0](<https://devfeed.tech/articles/introducing-laravel-ai-sdk-v1-0-58463.md>)

Original publisher: [Read original article](<https://laravel.com/blog/introducing-laravel-ai-sdk-v1>)

Author: Pushpak Chhajed

Published: 2026-09-23T10:53:00Z

Content type: release

Language: en

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

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [API](<https://devfeed.tech/topics/api.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [chat](<https://devfeed.tech/tags/chat.md>), [classification](<https://devfeed.tech/tags/classification.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [tool](<https://devfeed.tech/tags/tool.md>), [v1](<https://devfeed.tech/tags/v1.md>)

### AI overview

Laravel AI SDK v1.0 provides a Laravel-native API for multiple AI providers and adds classification, support for text, image, audio, and embedding workflows, protocol integrations for streaming chat interfaces, and customizable agent middleware.

### Source excerpt

Laravel AI SDK v1.0 is here: one Laravel-native API for every provider, with conversation storage, streaming chat, agents, tool approvals, and Jev classification.

## Securing AI Agent Tool Execution with TypeScript AST Sandboxes

DevFeed: [Securing AI Agent Tool Execution with TypeScript AST Sandboxes](<https://devfeed.tech/articles/securing-ai-agent-tool-execution-with-typescript-ast-sandboxes-55838.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/securing-ai-agent-tool-execution-with-typescript-ast-sandboxes/>)

Author: SitePoint Team

Published: 2026-09-21T14:39:23Z

Content type: tutorial

Language: en

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

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [prompt injection](<https://devfeed.tech/topics/prompt-injection.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [Bash](<https://devfeed.tech/topics/bash.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [LangChain](<https://devfeed.tech/topics/langchain.md>), [vercel ai sdk](<https://devfeed.tech/topics/vercel-ai-sdk.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [bash](<https://devfeed.tech/tags/bash.md>), [langchain](<https://devfeed.tech/tags/langchain.md>), [llm-applications](<https://devfeed.tech/tags/llm-applications.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [programming](<https://devfeed.tech/tags/programming.md>), [prompt-injection](<https://devfeed.tech/tags/prompt-injection.md>), [securing-ai](<https://devfeed.tech/tags/securing-ai.md>), [sql](<https://devfeed.tech/tags/sql.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

An implementation-focused tutorial on securing AI agent tool execution. It explains why regex deny-lists can be bypassed and presents TypeScript AST-based middleware that parses agent-generated Bash and SQL, validates structural allowlists, and blocks unsafe operations before execution.

### Source excerpt

Build a TypeScript middleware that parses agent-generated bash and SQL into ASTs, blocking prompt-injection escapes and destructive operations before tool execution. Continue reading Securing AI Agent Tool Execution with TypeScript AST Sandboxes on SitePoint.

## Building Distributed Sliding-Window Rate Limiters in TypeScript and Redis

DevFeed: [Building Distributed Sliding-Window Rate Limiters in TypeScript and Redis](<https://devfeed.tech/articles/building-distributed-sliding-window-rate-limiters-in-typescript-and-redis-55537.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/distributed-sliding-window-rate-limiter-typescript-redis/>)

Author: SitePoint Team

Published: 2026-09-20T14:38:55Z

Content type: tutorial

Language: en

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

Topics: [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [Lua](<https://devfeed.tech/topics/lua.md>), [Express](<https://devfeed.tech/topics/express.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [k6](<https://devfeed.tech/topics/k6.md>)

Tags: [atomic](<https://devfeed.tech/tags/atomic.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [databases](<https://devfeed.tech/tags/databases.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [express](<https://devfeed.tech/tags/express.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [k6](<https://devfeed.tech/tags/k6.md>), [limit](<https://devfeed.tech/tags/limit.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [programming](<https://devfeed.tech/tags/programming.md>), [quotas](<https://devfeed.tech/tags/quotas.md>), [race-condition](<https://devfeed.tech/tags/race-condition.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [redis](<https://devfeed.tech/tags/redis.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

A practical guide to building a distributed sliding-window rate limiter with TypeScript and Redis. It uses sorted sets and an atomic Lua script to enforce RPM and TPM quotas under concurrency, integrates with Express and Hono middleware, generates rate-limit headers, and tests behavior with k6.

### Source excerpt

Implement an atomic sliding-window rate limiter in TypeScript with Redis sorted sets and Lua, enforcing dual RPM/TPM quotas with standard rate-limit headers. Continue reading Building Distributed Sliding-Window Rate Limiters in TypeScript and Redis on SitePoint.

[Next page](<https://devfeed.tech/topics/middleware.md?cursor=WyIyMDI2LTA5LTIwVDE0OjM4OjU1KzAwOjAwIiwgIjkzNjhmZDZlLTFkMWItNDk4Ny1iMDU5LTA5YzUyMGY3N2MxNiJd>)