# rate-limiting

Rate limiting is a computing and networking technique that controls how many operations or requests can be performed within a given time to prevent system overload and mitigate denial-of-service attacks.

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

## 7 Ways AI Agents Fail in Production (and How to Catch Each One)

DevFeed: [7 Ways AI Agents Fail in Production (and How to Catch Each One)](<https://devfeed.tech/articles/7-ways-ai-agents-fail-in-production-and-how-to-catch-each-one-146247.md>)

Original publisher: [Read original article](<https://machinelearningmastery.com/7-ways-ai-agents-fail-in-production-and-how-to-catch-each-one/>)

Author: Nahla Davies

Published: 2026-11-20T11:00:00Z

Content type: article

Language: en

Sources: [MachineLearningMastery.com](<https://devfeed.tech/sources/machinelearningmastery-com.md>)

Topics: [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [ReAct agent Python](<https://devfeed.tech/topics/react-agent-python.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>), [Exception handling](<https://devfeed.tech/topics/exception-handling.md>), [long-running](<https://devfeed.tech/topics/long-running.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [agent-evaluation](<https://devfeed.tech/tags/agent-evaluation.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [fail](<https://devfeed.tech/tags/fail.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [production](<https://devfeed.tech/tags/production.md>)

### AI overview

A green tool response does not prove an agent completed its task; verify outcomes in resulting state and external records. The excerpt proposes seven regression checks: strictly validate tool arguments; compare extracted fields and source versions with confirmed ground truth; test whether injected document instructions are proposed and ensure they never execute; deny unauthorized cross-tenant or unapproved actions and assert stored data stays unchanged; retry with a stable operation ID and deduplicate matching requests; restart from persistent checkpoints and assert completion only when an authorized receipt exists; and stop repeated actions when progress stalls, using separate limits for calls, time, spend, and graph execution. Correlate run events under one ID, distinguish proposed, denied, waiting, and complete states, and pair each failing fixture with a passing control. The excerpt notes limits: confidence scores and citations do not establish correctness, in-memory checkpoints are lost on restart, and a timeout may leave an action's outcome unknown.

### Source excerpt

Three events that look alike need separate names.

## Best Rate Limiting and Quota Tools for Agent Fleets

DevFeed: [Best Rate Limiting and Quota Tools for Agent Fleets](<https://devfeed.tech/articles/best-rate-limiting-and-quota-tools-for-agent-fleets-146955.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/best-rate-limiting-quota-tools>)

Author: Swytchcode Team

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

Content type: comparison

Language: en

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

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>)

Tags: [agent-fleets](<https://devfeed.tech/tags/agent-fleets.md>), [api](<https://devfeed.tech/tags/api.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [quota](<https://devfeed.tech/tags/quota.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Agent fleets need a shared counter to stay within a provider quota: per-process token buckets cannot see calls from other workers. The article compares shared-counter options: Kong can use Redis, while its local policy only approximates a fleet limit; Tyk's shared multi-node behavior depends on licensed components. Unkey shares customer limits across keys, with regional counts that may run high. Upstash Ratelimit uses Redis over HTTP for short-lived workers. Envoy delegates global decisions to an external rate-limit service, typically backed by Redis, which adds operational work. Treblle provides monitoring and alerts but does not throttle traffic. A Redis limiter built in-house offers control but requires atomic operations and ownership of edge cases. These tools address quota pooling, while safe retries are separate: the article says Swytchcode retries rate-limited calls with backoff and automatically retries POST or PATCH only when an idempotency key is set.

### Source excerpt

Most api rate limiting tools protect one process. Agent fleets share one provider quota, and that's a different problem.

## Doing More by Storing Less: Speeding Up Real-Time Machine Learning

DevFeed: [Doing More by Storing Less: Speeding Up Real-Time Machine Learning](<https://devfeed.tech/articles/doing-more-by-storing-less-speeding-up-real-time-machine-learning-144308.md>)

Original publisher: [Read original article](<https://medium.com/feedzaitech/doing-more-by-storing-less-speeding-up-real-time-machine-learning-23639ae00e22?source=rss----e11168e7fe6b---4>)

Author: Augusto Peres

Published: 2026-11-19T15:40:42Z

Content type: article

Language: en

Sources: [Feedzai](<https://devfeed.tech/sources/feedzai.md>)

Topics: [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [aggregate](<https://devfeed.tech/tags/aggregate.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [counts](<https://devfeed.tech/tags/counts.md>), [database](<https://devfeed.tech/tags/database.md>), [detection](<https://devfeed.tech/tags/detection.md>), [event](<https://devfeed.tech/tags/event.md>), [financial-applications](<https://devfeed.tech/tags/financial-applications.md>), [fraud-detection](<https://devfeed.tech/tags/fraud-detection.md>), [heavy-hitter](<https://devfeed.tech/tags/heavy-hitter.md>), [inference](<https://devfeed.tech/tags/inference.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [latency](<https://devfeed.tech/tags/latency.md>), [machine-learning](<https://devfeed.tech/tags/machine-learning.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [storage](<https://devfeed.tech/tags/storage.md>)

### AI overview

Feedzai's event filtering reduces costly read-modify-write database cycles for high-volume entities while aiming to preserve useful feature profiles. Below a chosen per-entity write-rate threshold, every event is stored; above it, events are randomly included with probability set by the threshold divided by the estimated arrival rate. Kept events are weighted by the inverse of that probability to compensate counts and sums for discarded updates. The system can estimate arrival rates from filtered persisted statistics, updating and scaling those estimates through the same sampling process rather than tracking every entity's rate in memory; the article describes this as self-correcting. It says the approach fits power-law transaction volumes and reports that model accuracy did not decline under heavy filtering, with small gains in some cases attributed to training noise. The excerpt provides no quantitative performance results.

### Source excerpt

Modern fraud detection systems rely heavily on tracking behavior over time. For example: How much money has a person spent this month? Or, how many purchases have they made in the last week? Any event-streaming system worth its salt tracks hundreds of such metrics. Every time a new transaction even arrives, these are retrieved from a database, updated, and then written back to persistent storage. This process is known as the read-modify-write cycle, and its final write stage is a major source of latency, database contention, and infrastructure cost. But here is the catch: In many financial applications, a small set of heavy-hitter entities triggers most of these cycles and accounts for a disproportionate number of transactions. Statistically, the more events we process for any entity, the less information each individual event adds to their overall profile. Thus, here at Feedzai we developed a process and system that automatically stops writing every single event for large financial entities, saving significant compute without losing downstream ML accuracy. A friendly introduction to feature profiles Before we go any deeper into discarding events, we briefly explain what feature profiles are. Essentially, feature profiles aggregate events over a period of time. Two common examples are: Counts: How many times have we seen an entity doing something? e.g., the number of transactions for a specific debit card in the last month. Sums: The running total of a quantity associated with an event, e.g., the total spend of a user in the last week. In a real-time fraud detection system, when a single event arrives, the feature profiles for its associated entity must be retrieved from persistent storage, (e.g., a relational database or key-value store). Then, the profiles must be updated with the information on the new event. Next, the updated profiles are sent to a Machine Learning inference service for classification (e.g., fraud or not fraud) and written back to persistent sto

## CVE-2026-127960 - Denial of service through folded HTTP response headers

DevFeed: [CVE-2026-127960 - Denial of service through folded HTTP response headers](<https://devfeed.tech/articles/cve-2026-127960-denial-of-service-through-folded-http-response-headers-143726.md>)

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

Author: cvefeed.io

Published: 2026-11-19T14:44:15Z

Content type: news

Language: en

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

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [HTTP](<https://devfeed.tech/topics/http.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [application](<https://devfeed.tech/tags/application.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cpu-time](<https://devfeed.tech/tags/cpu-time.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-127960](<https://devfeed.tech/tags/cve-2026-127960.md>), [denial-of-service](<https://devfeed.tech/tags/denial-of-service.md>), [headers](<https://devfeed.tech/tags/headers.md>), [http](<https://devfeed.tech/tags/http.md>), [performance](<https://devfeed.tech/tags/performance.md>), [php](<https://devfeed.tech/tags/php.md>), [request](<https://devfeed.tech/tags/request.md>), [response](<https://devfeed.tech/tags/response.md>), [server](<https://devfeed.tech/tags/server.md>), [stream](<https://devfeed.tech/tags/stream.md>), [url](<https://devfeed.tech/tags/url.md>), [workers](<https://devfeed.tech/tags/workers.md>), [wrapper](<https://devfeed.tech/tags/wrapper.md>)

### AI overview

PHP's HTTP stream wrapper parses folded response headers by repeatedly allocating a new string and copying the accumulated value for each continuation line. Many short lines can therefore consume disproportionate CPU. An attacker who controls a response fetched through PHP stream functions, by inducing a request to a chosen URL or influencing a server the application already contacts, can keep workers busy; repeated or concurrent requests can cause denial of service. Affected ranges are PHP 8.2.28 to before 8.2.36, 8.3.18 to before 8.3.37, 8.4.5 to before 8.4.28, and 8.5.x to before 8.5.13.

### Source excerpt

CVE ID :CVE-2026-127960 Published : Nov. 19, 2026, 2:44 p.m. | 38 minutes ago Description :Denial of service through folded HTTP response headers. The HTTP stream wrapper joins each continuation line of a folded response header to the accumulated value by allocating a new string and copying the whole value, so a response with many short continuation lines takes disproportionate CPU time to parse. An attacker who controls an HTTP or HTTPS response fetched through file_get_contents(), fopen() or other stream functions, by making the application request a chosen URL or by influencing a server it already contacts, can keep PHP workers busy. Repeated or concurrent requests can cause a denial of service. This issue affects PHP versions from 8.2.28 before 8.2.36, from 8.3.18 before 8.3.37, from 8.4.5 before 8.4.28 and 8.5.* before 8.5.13. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Cap-and-Track: Optimizing LLM Inference Request Dispatch Across Shifting Capacity

DevFeed: [Cap-and-Track: Optimizing LLM Inference Request Dispatch Across Shifting Capacity](<https://devfeed.tech/articles/cap-and-track-optimizing-llm-inference-request-dispatch-across-shifting-capacity-143577.md>)

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

Author: Benjamin Novotny, Doug Szeto, Chang Wang, Shicheng Chen, George Zhihua Yuan, Bob Kamma, Michael Ge, John Xin Zhou, Andrea Olgiati

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

Content type: article

Language: en

Sources: [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [backpressure](<https://devfeed.tech/topics/backpressure.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [async](<https://devfeed.tech/topics/async.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [abstract](<https://devfeed.tech/tags/abstract.md>), [admission](<https://devfeed.tech/tags/admission.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [backend](<https://devfeed.tech/tags/backend.md>), [batches](<https://devfeed.tech/tags/batches.md>), [can](<https://devfeed.tech/tags/can.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [change](<https://devfeed.tech/tags/change.md>), [classifier](<https://devfeed.tech/tags/classifier.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [design](<https://devfeed.tech/tags/design.md>), [dispatch](<https://devfeed.tech/tags/dispatch.md>), [dispatcher](<https://devfeed.tech/tags/dispatcher.md>), [inference](<https://devfeed.tech/tags/inference.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-inference](<https://devfeed.tech/tags/llm-inference.md>), [optimizing](<https://devfeed.tech/tags/optimizing.md>), [request](<https://devfeed.tech/tags/request.md>)

### AI overview

Cap-and-Track dispatches asynchronous LLM inference using backend refusals as signals of current capacity. Cap rejects work before it incurs a long wait; durable priority queues hold excess and refused requests for retry. Track probes upward and backs off using those refusals, avoiding output-length prediction and a fixed fleet-wide rate. In a same-traffic production A/B, the system served a classifier with 43% fewer H100s than its queued, fixed-rate predecessor, though lower-priority work waited longer during backfill peaks. In steady-capacity engine replay, it achieved within 1% of a fixed rate tuned above capacity, with about one-quarter its refusal share. The authors also recommend keeping engine queues only long enough to fill batches, maintaining stateful dispatch, and sizing fleets according to tolerable waits for low-priority work.

### Source excerpt

arXiv:2611.24891v1 Announce Type: new Abstract: A fixed dispatch rate for LLM inference becomes stale as serving fleets resize and request sizes change. Generative output length is unknown at admission, and shared provider pools can lose capacity. We present Cap-and-Track, a design for asynchronous inference across provider capacity and internal GPUs. Meta's traffic shaper implements Cap-and-Track for post and live-video understanding. Refusals signal the backend's current admission ceiling. Durable priority queues hold excess work outside execution, including refused requests for retry. Cap is a fail-fast admission check at the saturated resource that refuses work before a long wait. Using only those refusals, the Track dispatcher probes upward and backs off. It follows the ceiling without output-length prediction or a fleet-level rate to retune. In a concurrent same-traffic production A/B, the shaper ran per-replica Cap plus Track. It served a classifier on 43% fewer H100s than its queued, fixed-rate precursor, though lower-priority work waited longer at backfill peaks. In steady-capacity real-engine replay, Track ran within 1% of the goodput of a fixed rate tuned above measured capacity, with about a quarter of that rate's refusal share. The shaper carries more than 300 million online requests and hundreds of terabytes of media a day. During a backfill, it handled 1.1 billion requests in its busiest 24 hours. Lessons include keeping queues inside inference engines just long enough to fill batches, steering dispatch by capacity refusals alone, keeping dispatch stateful, and sizing fleets by how long low-priority work can wait.

## How Airbnb uses cost per task to operate coding agents on Amazon Bedrock

DevFeed: [How Airbnb uses cost per task to operate coding agents on Amazon Bedrock](<https://devfeed.tech/articles/how-airbnb-uses-cost-per-task-to-operate-coding-agents-on-amazon-bedrock-141280.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/how-airbnb-uses-cost-per-task-to-operate-coding-agents-on-amazon-bedrock/>)

Author: Alan Yao

Published: 2026-11-18T21:48:19Z

Content type: article

Language: en

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

Topics: [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [airbnb](<https://devfeed.tech/tags/airbnb.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [cost](<https://devfeed.tech/tags/cost.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [evals](<https://devfeed.tech/tags/evals.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [latency](<https://devfeed.tech/tags/latency.md>), [model-selection](<https://devfeed.tech/tags/model-selection.md>), [observability](<https://devfeed.tech/tags/observability.md>), [production](<https://devfeed.tech/tags/production.md>), [quotas](<https://devfeed.tech/tags/quotas.md>), [spending](<https://devfeed.tech/tags/spending.md>), [tasks](<https://devfeed.tech/tags/tasks.md>)

### AI overview

Airbnb combines task-based evaluations with Amazon Bedrock production metrics to select and revisit coding-agent models. It scores models and reasoning-effort settings on representative engineering tasks, pricing all uncached input, cache reads, cache writes, and output tokens across a task; these results guide defaults and effort ceilings. Production can diverge: one model scored better at similar eval cost, but its users later spent several times more because requests cost about three times as much and users sent about three times as many requests. A newer model later scored higher at roughly one sixth the task cost, and heavy users' spend fell to about a seventh with similar request volume. For operations, Airbnb tracks latency, token counts, derived output speed, throttles, and estimated quota usage. Quota admission reserves uncached input, cache writes, and max_tokens, so lowering an oversized max_tokens can improve admission headroom without changing final quota consumption for unchanged output. Gateway records, IAM tags, inference profiles, and invocation logs support aggregate spend attribution; logs require access controls and retention settings.

### Source excerpt

Airbnb runs evals on real engineering tasks and uses Amazon Bedrock observability to choose models for its coding agents and control production costs. This post shows how cost per task guides model selection, why production spending can differ from eval results, and how to monitor latency, manage quotas, and attribute spend.

## How we raised Databricks cluster rate limits by 7.5x

DevFeed: [How we raised Databricks cluster rate limits by 7.5x](<https://devfeed.tech/articles/how-we-raised-databricks-cluster-rate-limits-by-7-5-139643.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/how-we-raised-databricks-cluster-rate-limits-75>)

Author: Heqing Ya; Tan Zhang; Ankit Batra; Abhishek Rai

Published: 2026-11-18T02:30:31Z

Content type: article

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [added](<https://devfeed.tech/tags/added.md>), [after](<https://devfeed.tech/tags/after.md>), [aggregate](<https://devfeed.tech/tags/aggregate.md>), [all](<https://devfeed.tech/tags/all.md>), [allows](<https://devfeed.tech/tags/allows.md>), [also](<https://devfeed.tech/tags/also.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [compute](<https://devfeed.tech/tags/compute.md>), [compute-platform](<https://devfeed.tech/tags/compute-platform.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [limits](<https://devfeed.tech/tags/limits.md>), [platform](<https://devfeed.tech/tags/platform.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

Databricks raised default cluster-creation request-rate limits 7.5x by adding adaptive concurrency control for the longer provisioning workflows behind each API call. Each active workflow holds a slot through VM provisioning and dependency waits; health signals such as provisioning latency and thread-pool saturation guide the slot limit. When capacity falls, accepted requests queue and start more slowly; as conditions recover, concurrency increases cautiously. The fixed API rate limit remains a guardrail for exceptionally high traffic. This separates capacity management from request-rate enforcement, but a successful API response does not promise an immediate launch or fixed completion time. Queues need bounded size and wait times, and retries need backoff and attempt limits; concurrency limits cannot restore an unavailable dependency. The reported rollout raised default limits 7.5x, reduced cluster-creation rate-limit errors by more than 99.99% in the stated scope, and removed over a hundred customer-specific overrides in scope. Since the increase, few customers have hit the higher limits and no new manual overrides have been added.

### Source excerpt

As part of the Compute Platform team at Databricks, we turn cloud infrastructure...

## Why the Holidays are Gaming's Biggest Season and Its Riskiest

DevFeed: [Why the Holidays are Gaming's Biggest Season and Its Riskiest](<https://devfeed.tech/articles/why-the-holidays-are-gaming-s-biggest-season-and-its-riskiest-143979.md>)

Original publisher: [Read original article](<https://www.fastly.com/blog/why-holidays-are-gamings-biggest-season-and-riskiest/>)

Author: Ashley Hurwitz

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

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

Topics: [observability in gaming](<https://devfeed.tech/topics/observability-in-gaming.md>), [observability](<https://devfeed.tech/topics/observability.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>)

Tags: [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [apis](<https://devfeed.tech/tags/apis.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bot-detection](<https://devfeed.tech/tags/bot-detection.md>), [bot-protection](<https://devfeed.tech/tags/bot-protection.md>), [bots](<https://devfeed.tech/tags/bots.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [credential-stuffing](<https://devfeed.tech/tags/credential-stuffing.md>), [ddos](<https://devfeed.tech/tags/ddos.md>), [edge](<https://devfeed.tech/tags/edge.md>), [edge-cloud](<https://devfeed.tech/tags/edge-cloud.md>), [fastly](<https://devfeed.tech/tags/fastly.md>), [fraud](<https://devfeed.tech/tags/fraud.md>), [fraud-prevention](<https://devfeed.tech/tags/fraud-prevention.md>), [gaming](<https://devfeed.tech/tags/gaming.md>), [holidays](<https://devfeed.tech/tags/holidays.md>), [industry-insights](<https://devfeed.tech/tags/industry-insights.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

Holiday gaming traffic surges can conceal credential stuffing, account takeover, gift card fraud, or DDoS activity, while capacity failures and attacks may look alike. The excerpt says attackers target gaming APIs as well as web portals, and that peak volumes make threats harder to distinguish. It recommends absorbing surges with edge load balancing, correlating real-time logs with availability and login signals, rate limiting requests before they reach origin, and using automated bot detection and edge WAF rules. These controls need to distinguish players from bots: overly rigid rules can block legitimate logins or registrations. The described goal is to keep the platform available and catch attacks without slowing or locking out players.

### Source excerpt

Holiday traffic surges in gaming hide the attacks riding along with them. Learn how to protect capacity and catch credential stuffing without slowing down players.

## What Chrome Extensions Can and Cannot Do with Manifest V3

DevFeed: [What Chrome Extensions Can and Cannot Do with Manifest V3](<https://devfeed.tech/articles/what-chrome-extensions-can-and-cannot-do-with-manifest-v3-142013.md>)

Original publisher: [Read original article](<https://jsdev.space/chrome-extension-manifest/>)

Author: Anton Liberant

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

Sources: [JavaScript Development](<https://devfeed.tech/sources/javascript-development.md>)

Topics: [Chrome extension](<https://devfeed.tech/topics/chrome-extension.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [health check](<https://devfeed.tech/topics/health-check.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [certificates](<https://devfeed.tech/tags/certificates.md>), [chrome-extensions](<https://devfeed.tech/tags/chrome-extensions.md>), [http](<https://devfeed.tech/tags/http.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [manifest-v3](<https://devfeed.tech/tags/manifest-v3.md>), [websites](<https://devfeed.tech/tags/websites.md>)

### AI overview

Manifest V3 can support a useful browser monitor: `webRequest` observes main-frame status codes, server redirects, and approximate time to first response byte, while `webNavigation` helps identify client redirects and single-page app route changes. Coverage is incomplete: cached or prerendered pages, site service workers, and browser event ordering can leave gaps, so missing data should not be presented as a fresh HTTP result. Chrome 144's certificate-data option may require an experimental flag; reliable expiry checks may need a backend, with hostname and network protections and explicit user initiation. RDAP can provide registration expiry over HTTPS where supported, but coverage and disclosed dates vary; cache results and use a Public Suffix List library to find registered domains. MV3 workers can stop after inactivity, so persist state, register listeners at startup, and use alarms; alarms do not run while the device sleeps. Availability checks should be bounded and cookie-free, distinguish HTTP errors from network failures, filter noisy errors, and limit retries. Broad host permissions enable arbitrary-site monitoring; optional host permissions suit user-selected sites.

### Source excerpt

Learn how Chrome extensions can inspect HTTP responses, track redirects, check SSL certificates, and monitor websites under Manifest V3 limitations.

## Cloud keys leaked in Docker Hub images are stolen within seconds

DevFeed: [Cloud keys leaked in Docker Hub images are stolen within seconds](<https://devfeed.tech/articles/cloud-keys-leaked-in-docker-hub-images-are-stolen-within-seconds-138535.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/cloud-keys-leaked-in-docker-hub-images-are-stolen-within-seconds/>)

Author: Bill Toulas

Published: 2026-11-17T21:27:17Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [token jacking](<https://devfeed.tech/topics/token-jacking.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [anthropic-api](<https://devfeed.tech/tags/anthropic-api.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [automated](<https://devfeed.tech/tags/automated.md>), [aws](<https://devfeed.tech/tags/aws.md>), [business-email-compromise](<https://devfeed.tech/tags/business-email-compromise.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-hub](<https://devfeed.tech/tags/docker-hub.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [honeypot](<https://devfeed.tech/tags/honeypot.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [key](<https://devfeed.tech/tags/key.md>), [keys](<https://devfeed.tech/tags/keys.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [public](<https://devfeed.tech/tags/public.md>), [published](<https://devfeed.tech/tags/published.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

In a four-month experiment, researchers published 300 honeypot images across eight public container registries and found exposed credentials could be exploited within seconds. On Docker Hub, the fastest planted AWS key use came 7.86 seconds after publication; the median first call was 51.19 seconds, and all 100 AWS keys were used within 15 minutes. The keys received more than 140,000 API calls from 5,000 unique IP addresses, while exposed OpenAI and Anthropic keys were used to exhaust test-account balances. Monitoring rarely detected containers being run, suggesting scanners usually extracted secrets by inspecting image layers or querying registry APIs. The researchers recommend scanning images for secrets before publication and restricting or rate-limiting access to Docker Hub's feed of recently updated images. In an August check, they found no changes to platform defenses.

### Source excerpt

Credentials and access secrets exposed in public Docker Hub images are being extracted and exploited by attackers within as little as eight seconds of publication. [...]

## Securely exposing Amazon Bedrock AgentCore Runtime

DevFeed: [Securely exposing Amazon Bedrock AgentCore Runtime](<https://devfeed.tech/articles/securely-exposing-amazon-bedrock-agentcore-runtime-140906.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/securely-exposing-amazon-bedrock-agentcore-runtime/>)

Author: Meriem SMACHE

Published: 2026-11-17T20:31:30Z

Content type: article

Language: en

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

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [agentcore-runtime](<https://devfeed.tech/tags/agentcore-runtime.md>), [agentic-workflow](<https://devfeed.tech/tags/agentic-workflow.md>), [agentic-workloads](<https://devfeed.tech/tags/agentic-workloads.md>), [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-bedrock-guardrails](<https://devfeed.tech/tags/amazon-bedrock-guardrails.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [data-governance](<https://devfeed.tech/tags/data-governance.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [microvm](<https://devfeed.tech/tags/microvm.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [session](<https://devfeed.tech/tags/session.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AgentCore Runtime's per-session microVM isolation does not control who reaches it or preserve user identity across the ingress path, so the document presents two layered access patterns. Amazon API Gateway validates the Cognito JWT at the edge and again through AgentCore Identity, binds sessions to users, and forwards the original token through a proxy Lambda and VPC endpoint. This suits teams with existing API Gateway and VPC controls, though long-running calls may exceed API Gateway timeouts. AgentCore Gateway validates the JWT, applies Cedar policies and Guardrails, binds identity claims for unattended work, and exchanges them for a machine token that Runtime requires; its managed entry point and native rate limiting reduce custom infrastructure. Both patterns call for WAF, least-privilege authorization, identity propagation, and audit logging. The document says both CDK samples are starting points, not production-ready deployments.

### Source excerpt

Amazon Bedrock AgentCore Runtime delivers a secure serverless environment to deploy AI agents and tools at scale. When you start talking to your agent, the runtime launches a dedicated isolated session that runs in its own dedicated microVM with a completely sandboxed CPU, memory, and filesystem allocation. This provides strict data governance, helps to prevent [...]

## Where the Savings Go: The Limits of Hiding Cross-Tenant Cache Hits in LLM Serving

DevFeed: [Where the Savings Go: The Limits of Hiding Cross-Tenant Cache Hits in LLM Serving](<https://devfeed.tech/articles/where-the-savings-go-the-limits-of-hiding-cross-tenant-cache-hits-in-llm-serving-139296.md>)

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

Author: Bowen Sun, Chaowei Xiao

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

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [LLM security](<https://devfeed.tech/topics/llm-security.md>), [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [vllm](<https://devfeed.tech/topics/vllm.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [channel](<https://devfeed.tech/tags/channel.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [inference](<https://devfeed.tech/tags/inference.md>), [llm-serving](<https://devfeed.tech/tags/llm-serving.md>), [prefill](<https://devfeed.tech/tags/prefill.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [random](<https://devfeed.tech/tags/random.md>), [request](<https://devfeed.tech/tags/request.md>), [reuse](<https://devfeed.tech/tags/reuse.md>), [sglang](<https://devfeed.tech/tags/sglang.md>), [share](<https://devfeed.tech/tags/share.md>), [trace](<https://devfeed.tech/tags/trace.md>), [vllm](<https://devfeed.tech/tags/vllm.md>)

### AI overview

Sharing an LLM prefix cache can leak whether another tenant used a text through saved computation that speeds later queued requests. In step-based schedulers that keep working while requests wait, the saved time shifts every queued request earlier. A rate-limited attacker can bracket a probe with two groups of one-token listeners and compare their completion steps. In a replayed production trace on one vLLM instance at up to half capacity, one probe detected cached texts of 256 tokens or more with advantage at least 0.98. Hiding only the hit request still allowed detection with one probe on vLLM and SGLang; random delays had to reach roughly ten times the shift or more to reduce advantage to 0.1. The abstract also bounds a tenant's gain from content written by k other accounts by order k times the permitted leakage: with zero leakage, only the provider retains the savings. Exact hiding is possible in principle on one instance, but pause-or-hold mechanisms under saturated prefill must pad every step that might hold a hit, with cost growing over time rather than with hits.

### Source excerpt

arXiv:2611.20291v1 Announce Type: new Abstract: LLM serving engines cache prompt prefixes; a cache hit skips computation and returns faster, so a shared cache reveals whether others have sent a given text. Per-account salting closes this channel but forgoes cross-tenant reuse and isolates only whole accounts, even where access is redistributed or trust domains are subdivided below them. Defenses that share globally but hide hits promise reuse without relying on account boundaries. Hiding a hit requires everything tenants observe afterwards to be distributed as if it had missed. The defenses we examine target the hit-miss gap; we instead follow where the saved time goes. Step-based schedulers that never idle while work waits pass it in full to every request queued behind the hit, shifting each earlier by the same amount. An attacker within ordinary rate limits brackets a probe with two groups of listeners that each return one token, sends them in one short burst, and counts in how many steps they finish. Replaying a production trace on one vLLM instance at up to half capacity, a single probe detects cached texts of 256 tokens or more with advantage at least 0.98. Hiding only the hit request falls to one probe on vLLM and SGLang; random delays must reach about ten times the shift or more to cut the advantage to 0.1; narrowing what is shared gives no guarantee against this inference. Since any observable tenant benefit is also a signal, we prove that a rate-limited tenant's gain from content written by k other accounts is at most of order k times the leakage allowed, whatever the provider does with identities; at zero leakage, only the provider keeps the savings. Exact hiding is attainable in principle on one instance, but mechanisms that only pause or hold work know skipped work's duration only approximately, so under saturated prefill they must pad every step that may hold a hit, at a price that grows with time rather than with hits.

## CVE-2026-104840 - OpenCTI: No rate limiting on authentication endpoint allows credential brute-forcing

DevFeed: [CVE-2026-104840 - OpenCTI: No rate limiting on authentication endpoint allows credential brute-forcing](<https://devfeed.tech/articles/cve-2026-104840-opencti-no-rate-limiting-on-authentication-endpoint-allows-credential-brute-forcing-136266.md>)

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

Author: CVEFEED.io; github.com

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

Content type: article

Language: en

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

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [account](<https://devfeed.tech/topics/account.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [citeum](<https://devfeed.tech/tags/citeum.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-104840](<https://devfeed.tech/tags/cve-2026-104840.md>), [cyber-threat-intelligence](<https://devfeed.tech/tags/cyber-threat-intelligence.md>), [express](<https://devfeed.tech/tags/express.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [global](<https://devfeed.tech/tags/global.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [login](<https://devfeed.tech/tags/login.md>), [make](<https://devfeed.tech/tags/make.md>), [network](<https://devfeed.tech/tags/network.md>), [opencti](<https://devfeed.tech/tags/opencti.md>), [opencti-platform](<https://devfeed.tech/tags/opencti-platform.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [threat-intelligence](<https://devfeed.tech/tags/threat-intelligence.md>), [token](<https://devfeed.tech/tags/token.md>), [user](<https://devfeed.tech/tags/user.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Before OpenCTI 7.260428.0, the GraphQL token mutation used for primary login lacked an endpoint-specific rate limit. The global Express limiter allowed up to 10,000 requests per second, enabling unauthenticated remote attackers to guess passwords against a chosen account at network speed. A recovered credential could expose that account's threat-intelligence data and permitted operations. The issue is fixed in version 7.260428.0.

### Source excerpt

CVE ID :CVE-2026-104840 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.260428.0, the token GraphQL mutation used for primary login has no endpoint-specific rate limit, while the global Express limiter defaults to permitting 10,000 requests in a one-second window. An unauthenticated remote attacker can make password guesses at network speed against a chosen user account and, if a credential is recovered, access the account's threat-intelligence data and permitted operations. This issue is fixed in version 7.260428.0. Severity: 9.2 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## 40 Kubernetes Interview Questions That Expose Weak Senior Engineers

DevFeed: [40 Kubernetes Interview Questions That Expose Weak Senior Engineers](<https://devfeed.tech/articles/40-kubernetes-interview-questions-that-expose-weak-senior-engineers-136234.md>)

Original publisher: [Read original article](<https://blog.devops.dev/40-kubernetes-interview-questions-that-expose-weak-senior-engineers-f183baad39fb?source=rss----33f8b2d9a328---4>)

Author: Devrim Ozcay | Founder, ProdRescue

Published: 2026-11-16T13:26:05Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [health check](<https://devfeed.tech/topics/health-check.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>)

Tags: [advanced](<https://devfeed.tech/tags/advanced.md>), [affinity](<https://devfeed.tech/tags/affinity.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [devops](<https://devfeed.tech/tags/devops.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [docker](<https://devfeed.tech/tags/docker.md>), [failure](<https://devfeed.tech/tags/failure.md>), [interview](<https://devfeed.tech/tags/interview.md>), [interview-questions](<https://devfeed.tech/tags/interview-questions.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-cluster](<https://devfeed.tech/tags/kubernetes-cluster.md>), [latency](<https://devfeed.tech/tags/latency.md>), [load-balancing](<https://devfeed.tech/tags/load-balancing.md>), [memory](<https://devfeed.tech/tags/memory.md>), [networking](<https://devfeed.tech/tags/networking.md>), [persistent-volume](<https://devfeed.tech/tags/persistent-volume.md>), [production](<https://devfeed.tech/tags/production.md>), [programming](<https://devfeed.tech/tags/programming.md>), [questions](<https://devfeed.tech/tags/questions.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scheduling](<https://devfeed.tech/tags/scheduling.md>), [staff](<https://devfeed.tech/tags/staff.md>)

### AI overview

The article argues that senior Kubernetes troubleshooting requires tracing how scheduling, networking, application lifecycle, resources, and dependencies interact. It explains practical failure patterns and diagnostics: a Pending Pod may lack an eligible node despite spare aggregate CPU; CPU limits can throttle latency-sensitive work; premature readiness can route traffic to unprepared instances; and autoscaling can worsen overload by increasing pressure on a saturated dependency. It recommends checking scheduling events and requests, probe behavior, EndpointSlices, DNS and conntrack metrics, resource throttling, traces, and downstream capacity. Other sections cover safe rollouts and shutdown, database connection budgets, stateful workload recovery, security boundaries, incident response, and tradeoffs in multi-zone, multi-region, and multi-tenant designs. The text presents hypothetical interview scenarios and diagnostic approaches, not evidence of a specific incident or a complete Kubernetes reference.

### Source excerpt

Advanced Kubernetes troubleshooting, distributed systems, networking, autoscaling, and production reliability for Senior and Staff Engineers. A Kubernetes cluster with 180 nodes had plenty of available CPU. Every deployment reported success, and the control plane appeared healthy. Yet customers were experiencing intermittent 503 errors, and the API's p99 latency had climbed from 180 milliseconds to almost nine seconds. The infrastructure team increased the number of replicas. The application team increased connection pool sizes. Someone suggested moving the workloads to larger nodes because the existing cluster was obviously struggling. The situation became worse. The problem was that newly created Pods were passing readiness checks before their applications could serve real traffic. Every additional replica introduced another temporarily unhealthy endpoint into the load-balancing path. Autoscaling was increasing the number of requests routed toward instances that were technically running but operationally useless. This is why Kubernetes interviews become considerably harder at the Staff level. Knowing which command describes a Pod is useful, but it does not demonstrate an understanding of how scheduling, network routing, application lifecycle, resource allocation, and distributed dependencies interact during failure. The following 40 questions focus on those interactions. The scenarios are hypothetical, but the failure mechanisms and diagnostic approaches are grounded in Kubernetes and production engineering behavior. Part I -- Kubernetes Scheduling and Resource Management1. A Pod is Pending even though the cluster has available CPU and memory. Why? A candidate who immediately recommends adding nodes is missing several possibilities. Kubernetes scheduling evaluates requested resources alongside node selectors, affinity rules, taints, tolerations, topology constraints, persistent-volume placement, and other scheduling restrictions. Aggregate cluster capacity is irrel

## Your Retry Logic Might Be the Reason Your System Won't Recover

DevFeed: [Your Retry Logic Might Be the Reason Your System Won't Recover](<https://devfeed.tech/articles/your-retry-logic-might-be-the-reason-your-system-won-t-recover-135524.md>)

Original publisher: [Read original article](<https://hackernoon.com/your-retry-logic-might-be-the-reason-your-system-wont-recover?source=rss>)

Author: Gangadharan Venkataraman

Published: 2026-11-16T08:57:14Z

Content type: article

Language: en

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

Topics: [retry](<https://devfeed.tech/topics/retry.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [amplify](<https://devfeed.tech/tags/amplify.md>), [backpressure](<https://devfeed.tech/tags/backpressure.md>), [cascading-failures](<https://devfeed.tech/tags/cascading-failures.md>), [circuit](<https://devfeed.tech/tags/circuit.md>), [circuit-breaker](<https://devfeed.tech/tags/circuit-breaker.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [failures](<https://devfeed.tech/tags/failures.md>), [jitter](<https://devfeed.tech/tags/jitter.md>), [llm-inference-costs](<https://devfeed.tech/tags/llm-inference-costs.md>), [load-shedding](<https://devfeed.tech/tags/load-shedding.md>), [nested-retries](<https://devfeed.tech/tags/nested-retries.md>), [recover](<https://devfeed.tech/tags/recover.md>), [reliable-distributed-systems](<https://devfeed.tech/tags/reliable-distributed-systems.md>), [retry](<https://devfeed.tech/tags/retry.md>), [retry-amplification](<https://devfeed.tech/tags/retry-amplification.md>), [retry-storms](<https://devfeed.tech/tags/retry-storms.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

Retries can turn a temporary dependency slowdown into self-sustaining overload: synchronized clients multiply traffic beyond service capacity, and recovery of the original dependency may not be enough to restore service. The article recommends limiting retries to a fixed share of total traffic, using exponential backoff with jitter, opening circuit breakers after repeated failures, and dropping work that cannot meet its deadline. For AI agents, retries can also multiply model calls and token costs; framework retries may combine with a model's own attempts, creating more retries than configuration alone suggests. The excerpt explains this mechanism and remedies but offers no comparative measurements of their effectiveness.

### Source excerpt

Learn how retry storms amplify failures in distributed systems and AI agents, and how retry budgets, backoff, jitter, and circuit breakers help.

## Tor Updates DoS Defenses Again as Relay Attacks Continue

DevFeed: [Tor Updates DoS Defenses Again as Relay Attacks Continue](<https://devfeed.tech/articles/tor-updates-dos-defenses-again-as-relay-attacks-continue-134876.md>)

Original publisher: [Read original article](<https://www.securityweek.com/tor-updates-dos-defenses-again-as-relay-attacks-continue/>)

Author: Eduard Kovacs

Published: 2026-11-16T08:55:32Z

Content type: news

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [tor](<https://devfeed.tech/topics/tor.md>), [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [patches](<https://devfeed.tech/topics/patches.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [cyber resiliency](<https://devfeed.tech/topics/cyber-resiliency.md>)

Tags: [ddos](<https://devfeed.tech/tags/ddos.md>), [denial-of-service](<https://devfeed.tech/tags/denial-of-service.md>), [dos](<https://devfeed.tech/tags/dos.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [patch](<https://devfeed.tech/tags/patch.md>), [relay](<https://devfeed.tech/tags/relay.md>), [security-fixes](<https://devfeed.tech/tags/security-fixes.md>), [tor](<https://devfeed.tech/tags/tor.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

Tor 0.4.9.17 patches several security issues, including one affecting how relays' built-in DoS protections handle IPv6, in response to an ongoing attack flooding relays with client circuits. The Tor Project urged relay operators to update and said further defenses were under consideration. The excerpt notes that the disruption continued after the update: one operator reported a relay becoming unresponsive and losing HSDir status shortly after installation, with the attack ceasing when that status was lost. That operator said the release did not adequately protect HSDir relays and that the attacker changed techniques; these are operator claims, not a warning issued by Tor.

### Source excerpt

Tor 0.4.9.17 patches several security issues, including one related to how built-in DoS protections deal with IPv6. The post Tor Updates DoS Defenses Again as Relay Attacks Continue appeared first on SecurityWeek.

## Rate Limit Information from Anthropic API Response Headers Using ChatResponseMetadata in Spring AI

DevFeed: [Rate Limit Information from Anthropic API Response Headers Using ChatResponseMetadata in Spring AI](<https://devfeed.tech/articles/rate-limit-information-from-anthropic-api-response-headers-using-chatresponsemetadata-in-spring-ai-134252.md>)

Original publisher: [Read original article](<https://www.baeldung.com/spring-ai-anthropic-rate-limit>)

Author: Olayemi Michael

Published: 2026-11-14T14:14:40Z

Content type: tutorial

Language: en

Sources: [Baeldung](<https://devfeed.tech/sources/baeldung.md>)

Topics: [Spring AI](<https://devfeed.tech/topics/spring-ai.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Spring MVC](<https://devfeed.tech/topics/spring-mvc.md>)

Tags: [anthropic](<https://devfeed.tech/tags/anthropic.md>), [anthropic-api](<https://devfeed.tech/tags/anthropic-api.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-anthropic-spring-ai-chatclient](<https://devfeed.tech/tags/artificial-intelligence-anthropic-spring-ai-chatclient.md>), [controller](<https://devfeed.tech/tags/controller.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [github](<https://devfeed.tech/tags/github.md>), [java](<https://devfeed.tech/tags/java.md>), [limits](<https://devfeed.tech/tags/limits.md>), [maven](<https://devfeed.tech/tags/maven.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [spring-ai](<https://devfeed.tech/tags/spring-ai.md>), [spring-ai-chatclient](<https://devfeed.tech/tags/spring-ai-chatclient.md>)

### AI overview

The excerpt shows how a Spring AI application can return Anthropic rate-limit and token-usage data alongside generated text. Configure the Anthropic starter and API key, call the model through ChatClient, then read ChatResponseMetadata.getRateLimit() for request and token limits, remaining amounts, and reset duration; getUsage() supplies prompt and completion token counts. A controller can place these fields, the model name, and response text in a Java record returned from an endpoint. The sample response reports 10,000 requests allowed and 9,999 remaining, plus a token budget and usage counts. The values are those reported in the example; the excerpt does not compare providers.

### Source excerpt

Learn how to access rate limit metadata returned by Anthropic through Spring AI. The post Rate Limit Information from Anthropic API Response Headers Using ChatResponseMetadata in Spring AI first appeared on Baeldung.

## Securing FastAPI Applications: JWT Authentication and Rate Limiting with Redis

DevFeed: [Securing FastAPI Applications: JWT Authentication and Rate Limiting with Redis](<https://devfeed.tech/articles/securing-fastapi-applications-jwt-authentication-and-rate-limiting-with-redis-134136.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/securing-fastapi-applications-jwt-authentication-and-rate-limiting-with-redis/>)

Author: Christian chimeremeze ezenwa

Published: 2026-11-14T13:51:10Z

Content type: tutorial

Language: en

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

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [FastAPI](<https://devfeed.tech/topics/fastapi.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [fastapi](<https://devfeed.tech/tags/fastapi.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [redis](<https://devfeed.tech/tags/redis.md>)

### AI overview

The excerpt describes a FastAPI design that combines JWT authentication with Redis-backed revocation and rate limiting. FastAPI uses asynchronous Redis as shared state so token blacklists and request counts stay synchronized across server instances; python-jose signs and verifies JWTs, passlib[bcrypt] hashes passwords, and slowapi limits requests by client IP, returning 429 when a limit is exceeded. Protected routes reject missing, invalid, expired, or blacklisted tokens with 401. The described login stores a token in Redis with a TTL matching its expiration, while the sample credential check is hardcoded. The text says production deployment would need token refresh, per-user limits, highly available Redis, and secure secret management. It outlines conceptual validation scenarios rather than reporting test results.

### Source excerpt

null Continue reading Securing FastAPI Applications: JWT Authentication and Rate Limiting with Redis on SitePoint.

## New in n8n: Public API rate limits that keep every team on your instance running

DevFeed: [New in n8n: Public API rate limits that keep every team on your instance running](<https://devfeed.tech/articles/new-in-n8n-public-api-rate-limits-that-keep-every-team-on-your-instance-running-133392.md>)

Original publisher: [Read original article](<https://blog.n8n.io/new-in-n8n-public-api-rate-limits-that-keep-every-team-on-your-instance-running/>)

Author: Andrea Saez

Published: 2026-11-13T09:29:35Z

Content type: release

Language: en

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

Topics: [n8n](<https://devfeed.tech/topics/n8n.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [API keys](<https://devfeed.tech/topics/api-keys.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [automation](<https://devfeed.tech/tags/automation.md>), [batching](<https://devfeed.tech/tags/batching.md>), [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [configure](<https://devfeed.tech/tags/configure.md>), [controls](<https://devfeed.tech/tags/controls.md>), [counts](<https://devfeed.tech/tags/counts.md>), [headers](<https://devfeed.tech/tags/headers.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [limits](<https://devfeed.tech/tags/limits.md>), [n8n](<https://devfeed.tech/tags/n8n.md>), [new-on-n8n](<https://devfeed.tech/tags/new-on-n8n.md>), [public](<https://devfeed.tech/tags/public.md>), [retries](<https://devfeed.tech/tags/retries.md>), [retry](<https://devfeed.tech/tags/retry.md>), [safe](<https://devfeed.tech/tags/safe.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

Since n8n 2.47.0, admins can enable per-API-key public API rate limits on any plan, in Cloud or self-hosted deployments. Separate read and write limits can apply globally and per endpoint; 429 responses include retry and remaining-limit headers. Limits are off by default, and settings-page or API changes apply immediately. Self-hosted environment variables override those settings and require a restart. In multi-main setups, Redis shares each key's count across mains. For workflows calling their own instance API, use batching in the n8n or HTTP Request node: both send one request per item and fail on 429, while Retry On Fail may retry within the same limit window. Idempotency keys, available since 2.45.0, make POST retries safer: after success, n8n returns the stored response for the same key and body for 12 hours. Every key on an instance shares the configured limits; separate instances are needed for different integration headroom.

### Source excerpt

Cap public API requests per API key in n8n, with 429 headers that tell clients when to retry and idempotency keys for safe retries.

## OverServe: Resource Amplification Attacks on SaaS Agents via Tool--Prompt Co-Design

DevFeed: [OverServe: Resource Amplification Attacks on SaaS Agents via Tool--Prompt Co-Design](<https://devfeed.tech/articles/overserve-resource-amplification-attacks-on-saas-agents-via-tool-prompt-co-design-131696.md>)

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

Author: Ruiheng Yu, Oteo Mamo, Siyu Gan, Weikuan Yu, Mulong Luo

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

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [ai-assisted attacks](<https://devfeed.tech/topics/ai-assisted-attacks.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [prompt](<https://devfeed.tech/topics/prompt.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Use Cases for Every Cloud Service Model](<https://devfeed.tech/topics/use-cases-for-every-cloud-service-model.md>), [API Business Models](<https://devfeed.tech/topics/api-business-models.md>), [Nemotron](<https://devfeed.tech/topics/nemotron.md>), [qwen](<https://devfeed.tech/topics/qwen.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-framework](<https://devfeed.tech/tags/agent-framework.md>), [agents](<https://devfeed.tech/tags/agents.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [api](<https://devfeed.tech/tags/api.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [co-design](<https://devfeed.tech/tags/co-design.md>), [completion](<https://devfeed.tech/tags/completion.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [deepseek](<https://devfeed.tech/tags/deepseek.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [execution](<https://devfeed.tech/tags/execution.md>), [framework](<https://devfeed.tech/tags/framework.md>), [language-models](<https://devfeed.tech/tags/language-models.md>), [large-language-models](<https://devfeed.tech/tags/large-language-models.md>), [large-language-models-llms](<https://devfeed.tech/tags/large-language-models-llms.md>), [prompt](<https://devfeed.tech/tags/prompt.md>), [resource](<https://devfeed.tech/tags/resource.md>), [saas](<https://devfeed.tech/tags/saas.md>), [tool](<https://devfeed.tech/tags/tool.md>)

### AI overview

OverServe is a framework for amplifying resource use by SaaS agents through co-designed MCP status tools and prompts. The tools return accurate status and end normally, while prompts can lead an agent to keep checking an unfinished condition after its original business task is complete. The authors report that tested tool specifications triggered no alerts in the evaluated MCP scanners. On selected tasks from nine benchmarks, Qwen, Nemotron, DeepSeek, and Sonnet runs passed the original task checks; the maximum reported API request amplification was 93.88x while preserving the task goal and collateral checks.

### Source excerpt

arXiv:2611.14808v1 Announce Type: cross Abstract: Advances in large language models (LLMs) are enabling software-as-a-service (SaaS) providers to automate longer business workflows with agents. In subscription-based SaaS deployments, model and tool calls consume provider resources without additional customer payments. Because the agent autonomously decides when to stop, a malicious tenant can send a prompt to the agent, exploiting its completion decisions to extend execution and waste provider resources. In this paper, we present OverServe, a multi-agent framework for constructing such attacks against SaaS agents. OverServe co-designs Model Context Protocol (MCP) status tools and completion-confirmation prompts for the attacker. Each tool call returns accurate status and terminates normally, yet the agent may repeatedly check an unfinished condition to satisfy the prompt. This consumes the SaaS provider's resources even after the original business task is completed. OverServe constructs service-specific tool--prompt pairs and uses separate tool and prompt reviews to guide candidate pair selection. Tested tool specifications trigger no alerts in the evaluated MCP scanners. We evaluate Qwen, Nemotron, DeepSeek, and Sonnet on selected tasks from nine benchmarks. All OverServe runs pass the original task checks. OverServe can reach a maximal amplification of API requests by $93.88\times$ while preserving the original task goal and collateral checks.

## Building a self-service LLM gateway with Amazon Bedrock and LiteLLM

DevFeed: [Building a self-service LLM gateway with Amazon Bedrock and LiteLLM](<https://devfeed.tech/articles/building-a-self-service-llm-gateway-with-amazon-bedrock-and-litellm-130770.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/building-a-self-service-llm-gateway-with-amazon-bedrock-and-litellm/>)

Author: Sitaraman Vijay Krishna

Published: 2026-11-12T18:41:12Z

Content type: tutorial

Language: en

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

Topics: [litellm](<https://devfeed.tech/topics/litellm.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [internal developer portal](<https://devfeed.tech/topics/internal-developer-portal.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [controls](<https://devfeed.tech/tags/controls.md>), [cost](<https://devfeed.tech/tags/cost.md>), [developers](<https://devfeed.tech/tags/developers.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [litellm](<https://devfeed.tech/tags/litellm.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-gateway](<https://devfeed.tech/tags/llm-gateway.md>), [self-service](<https://devfeed.tech/tags/self-service.md>), [service](<https://devfeed.tech/tags/service.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The article presents a self-service LLM gateway pattern that puts Amazon Bedrock behind LiteLLM's OpenAI-compatible API on AWS Fargate. Developers use a single base URL and per-user keys; LiteLLM manages key budgets and rate limits, PostgreSQL stores key and spend state, Valkey provides caching and distributed rate limiting, and Bedrock inference profiles provide model-level quota isolation and routing. Langfuse captures prompt-level traces while CloudWatch tracks operational metrics; prompt logging requires suitable redaction, retention, and access controls. Key implementation requirements include LiteLLM Enterprise for SSO-based self-service key issuance, explicit per-model token pricing for budget enforcement, PostgreSQL for persistent state, and IAM permissions for both inference-profile and underlying model resources. The authors recommend long request timeouts for extended thinking, retrying throttled requests on the same model, and separating automation traffic. The post offers illustrative snippets rather than a complete deployable stack, and its examples use Claude models.

### Source excerpt

Build a self-service LLM gateway with LiteLLM on AWS Fargate that puts Amazon Bedrock foundation models behind an OpenAI-compatible API. Developers get instant access through a single API key, while platform teams gain per-user cost controls, quota isolation, and observability.

## CVE-2026-127131 - SOGo before 5.12.13 Missing Rate Limiting on TOTP Verification

DevFeed: [CVE-2026-127131 - SOGo before 5.12.13 Missing Rate Limiting on TOTP Verification](<https://devfeed.tech/articles/cve-2026-127131-sogo-before-5-12-13-missing-rate-limiting-on-totp-verification-130526.md>)

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

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-12T16:19:07Z

Content type: news

Language: en

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

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [alinto](<https://devfeed.tech/tags/alinto.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [brute-force](<https://devfeed.tech/tags/brute-force.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-127131](<https://devfeed.tech/tags/cve-2026-127131.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [sogo](<https://devfeed.tech/tags/sogo.md>), [totp](<https://devfeed.tech/tags/totp.md>), [two-factor-authentication](<https://devfeed.tech/tags/two-factor-authentication.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

SOGo versions before 5.12.13 are described as vulnerable to brute-force attempts against web-login TOTP verification when an attacker already has the victim's password. Repeated incorrect codes sent to POST /SOGo/connect do not increment the failed-login counter, and SOGoMaximumFailedLoginCount does not apply to these attempts, so the description says guessing can continue without lockout across 30-second code windows and bypass two-factor authentication.

### Source excerpt

CVE ID :CVE-2026-127131 Published : Nov. 12, 2026, 4:19 p.m. | 1 hour, 4 minutes ago Description :SOGo before 5.12.13 contains a missing rate limiting vulnerability in its web login TOTP verification that allows attackers who already possess a victim's password to brute-force the second-factor code without triggering any lockout. Attackers can send repeated POST requests to /SOGo/connect with wrong verification codes at high speed since failed TOTP attempts never increment the failed-login counter and SOGoMaximumFailedLoginCount does not apply, enabling indefinite guessing across 30-second code windows to bypass two-factor authentication. Severity: 9.1 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## How Intuit migrated from Apache Hive Metastore to AWS Glue Data Catalog

DevFeed: [How Intuit migrated from Apache Hive Metastore to AWS Glue Data Catalog](<https://devfeed.tech/articles/how-intuit-migrated-from-apache-hive-metastore-to-aws-glue-data-catalog-129561.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/how-intuit-migrated-from-apache-hive-metastore-to-aws-glue-data-catalog/>)

Author: Srinivasan Krishnasamy

Published: 2026-11-11T15:43:26Z

Content type: article

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [AWS Glue](<https://devfeed.tech/topics/aws-glue.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [etl](<https://devfeed.tech/topics/etl.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [Apache Flink](<https://devfeed.tech/topics/apache-flink.md>), [Amazon MSK](<https://devfeed.tech/topics/amazon-msk.md>), [data lake](<https://devfeed.tech/topics/data-lake.md>), [AWS Lake Formation](<https://devfeed.tech/topics/aws-lake-formation.md>), [Apache Spark](<https://devfeed.tech/topics/spark.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-services](<https://devfeed.tech/tags/ai-services.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [apache-hive](<https://devfeed.tech/tags/apache-hive.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-glue](<https://devfeed.tech/tags/aws-glue.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [data](<https://devfeed.tech/tags/data.md>), [data-catalog](<https://devfeed.tech/tags/data-catalog.md>), [data-discovery](<https://devfeed.tech/tags/data-discovery.md>), [hive](<https://devfeed.tech/tags/hive.md>), [integration](<https://devfeed.tech/tags/integration.md>), [intuit](<https://devfeed.tech/tags/intuit.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>)

### AI overview

Intuit migrated databases, tables, and partitions from Apache Hive Metastore (HMS) to AWS Glue Data Catalog (GDC) using a phased approach: a one-time migration, ongoing synchronization in both directions, hourly parity checks, and targeted repair syncs. A DynamoDB source-of-truth flag per table prevents sync loops. HMS changes flow through Debezium CDC and Kafka, with partition events batched over 10-second windows; GDC changes use EventBridge, Lambda, Kafka, and Flink to order events before applying them to HMS. Before migrating, Intuit recommends auditing unused objects, estimating and load-testing Glue API quotas, batching writes, and using retries with backoff to manage throttling. The migration covered databases, tables, and partitions for S3-backed data; column statistics, privileges, roles, functions, and transactions were out of scope. GDC also does not support database or table renames.

### Source excerpt

How Intuit migrated its data catalog from Apache Hive Metastore to AWS Glue Data Catalog on its journey to an open, secure lakehouse. This post covers the challenges, the phased bidirectional-sync solution, and the benefits: reduced operational overhead, improved data discovery, and tighter integration with AWS analytics services.

## API Gateway vs Load Balancer: Do You Need Both?

DevFeed: [API Gateway vs Load Balancer: Do You Need Both?](<https://devfeed.tech/articles/api-gateway-vs-load-balancer-do-you-need-both-129367.md>)

Original publisher: [Read original article](<https://blog.levelupcoding.com/p/api-gateway-vs-load-balancer>)

Author: Nikki Siapno

Published: 2026-11-11T11:49:28Z

Content type: comparison

Language: en

Sources: [Level Up Coding System Design Newsletter](<https://devfeed.tech/sources/level-up-coding-system-design-newsletter.md>)

Topics: [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [API](<https://devfeed.tech/topics/api.md>), [health check](<https://devfeed.tech/topics/health-check.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [API Governance](<https://devfeed.tech/topics/api-governance.md>), [API keys](<https://devfeed.tech/topics/api-keys.md>)

Tags: [algorithms](<https://devfeed.tech/tags/algorithms.md>), [api](<https://devfeed.tech/tags/api.md>), [api-gateway](<https://devfeed.tech/tags/api-gateway.md>), [api-management](<https://devfeed.tech/tags/api-management.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [application-load-balancer](<https://devfeed.tech/tags/application-load-balancer.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [backend](<https://devfeed.tech/tags/backend.md>), [backends](<https://devfeed.tech/tags/backends.md>), [balancing](<https://devfeed.tech/tags/balancing.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [e-commerce](<https://devfeed.tech/tags/e-commerce.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>)

### AI overview

A load balancer distributes traffic among healthy backend instances; an API gateway manages client access through policies such as authentication, quotas, transformations, and API versioning, then routes requests to services. Their features can overlap: AWS Application Load Balancer supports some authentication and URL rewriting, while Kong offers balancing and health checks. Choose a load balancer for server distribution or Layer 4 non-HTTP traffic, a gateway for centralized API policies, and both when those jobs are distinct or multiple self-hosted gateways need balancing. A single product may cover both at the required scale. Gateways do not replace services' own authorization checks.

### Source excerpt

Modern API gateways can load balance. Modern load balancers can handle authentication. So why use both?

[Next page](<https://devfeed.tech/topics/rate-limiting.md?cursor=WyIyMDI2LTExLTExVDExOjQ5OjI4KzAwOjAwIiwgIjU3ZjE0OTc1LWMyNTMtNDZiOC1iMmYwLTBjMWRmYjM1NDI1MSJd>)