# autoscaling

Computing infrastructure technique that automatically adjusts workload capacity or resources in response to demand.

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

## Your CPU limits aren't stopping noisy neighbors

DevFeed: [Your CPU limits aren't stopping noisy neighbors](<https://devfeed.tech/articles/your-cpu-limits-aren-t-stopping-noisy-neighbors-141936.md>)

Original publisher: [Read original article](<https://www.groundcover.com/blog/cpu-limits-arent-stopping-noisy-neighbors>)

Author: Anais Dotis

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

Content type: article

Language: en

Sources: [Ground Cover](<https://devfeed.tech/sources/ground-cover.md>)

Topics: [cgroups](<https://devfeed.tech/topics/cgroups.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Performance Testing](<https://devfeed.tech/topics/performance-testing.md>)

Tags: [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-infrastructure](<https://devfeed.tech/tags/autonomous-infrastructure.md>), [bin-packing](<https://devfeed.tech/tags/bin-packing.md>), [byoc](<https://devfeed.tech/tags/byoc.md>), [cfs](<https://devfeed.tech/tags/cfs.md>), [cgroup](<https://devfeed.tech/tags/cgroup.md>), [cgroups](<https://devfeed.tech/tags/cgroups.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [combined](<https://devfeed.tech/tags/combined.md>), [congestion-control](<https://devfeed.tech/tags/congestion-control.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cpu-time](<https://devfeed.tech/tags/cpu-time.md>), [groundcover](<https://devfeed.tech/tags/groundcover.md>), [latency](<https://devfeed.tech/tags/latency.md>), [limits](<https://devfeed.tech/tags/limits.md>), [memory](<https://devfeed.tech/tags/memory.md>), [nodes](<https://devfeed.tech/tags/nodes.md>), [oom](<https://devfeed.tech/tags/oom.md>)

### AI overview

Node-level contention explains why accurate per-workload sizing can still leave a cluster unstable: scheduling uses requests, while independently chosen P95 requests do not account for workloads peaking together. Under CPU contention, requests set proportional CPU weight; CPU limits impose quotas that can throttle a container even when other cores are idle. Memory has no proportional sharing: exceeding a limit can trigger an immediate OOM kill, while node pressure can lead to evictions or OOM kills. The post presents groundcover Autonomous Infrastructure as addressing this by using node-level CPU and memory history to identify overlapping peaks, adjust requests within operator-defined bounds, and apply changes to running Pods. It also says this requires high-resolution, per-container history linked to node and workload, and describes groundcover's eBPF sensor and BYOC storage as its collection approach.

### Source excerpt

This post explains what a noisy neighbor is, why CPU requests (not CPU limits) determine how CPU time is divided under contention, and why memory contention ends in OOM kills and evictions instead of added latency. It then explains why sizing each workload at a percentile of its own usage still overloads nodes, and how groundcover's Autonomous Infrastructure addresses that.

## Energy-Proportional Serverless Computing on SBC Clusters

DevFeed: [Energy-Proportional Serverless Computing on SBC Clusters](<https://devfeed.tech/articles/energy-proportional-serverless-computing-on-sbc-clusters-127812.md>)

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

Author: Yuliya Sasinskaya, Natalie Carl, Niklas Kowallik, David Bermbach

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

Content type: article

Language: en

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

Topics: [Sustainable Computing](<https://devfeed.tech/topics/sustainable-computing.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [function as a service](<https://devfeed.tech/topics/function-as-a-service.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>)

Tags: [clusters](<https://devfeed.tech/tags/clusters.md>), [computing](<https://devfeed.tech/tags/computing.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [energy](<https://devfeed.tech/tags/energy.md>), [sbc](<https://devfeed.tech/tags/sbc.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

A tinyFaaS platform for single-board computer clusters extends serverless scale-to-zero to physical nodes by including node power state in worker selection: idle workers are powered off and restarted under load. On a physical cluster, it reduced mean power draw by 39.6% for a bursty trace-based workload and 46.7% for a sparse workload. Median latency on the bursty workload showed no detectable change, but invocations arriving when all workers were off waited about a minute for a node to boot. Under continuous load, it behaved like an always-on cluster.

### Source excerpt

arXiv:2611.14026v1 Announce Type: new Abstract: Serverless computing promises to run code only on demand, yet the servers beneath it draw most of their power while idle, so energy consumption does not scale to zero with the workload. We show that the statelessness of serverless functions makes it possible to extend scale-to-zero from function instances to physical nodes, enabling energy proportionality. Our platform, built on tinyFaaS for clusters of single-board computers, treats node power state as part of worker selection, powering workers off when idle and back on under load. On a physical cluster, our approach reduces mean power draw by 39.6 % on a bursty, trace-based workload and by 46.7 % on a sparse one, without a detectable change in median latency on the bursty workload. The cost lands in the tail, where invocations that arrive while all workers are off wait about a minute for a node to boot. Under continuous load, the platform behaves like an always-on cluster.

## A Unified Queueing-Based Framework for Comparative Evaluation of Serverless Autoscaling Strategies under Bursty Workloads

DevFeed: [A Unified Queueing-Based Framework for Comparative Evaluation of Serverless Autoscaling Strategies under Bursty Workloads](<https://devfeed.tech/articles/a-unified-queueing-based-framework-for-comparative-evaluation-of-serverless-autoscaling-strategies-under-bursty-workloads-101637.md>)

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

Author: Zahra Zafarzade, Ehsan Ataie

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

Content type: news

Language: en

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

Topics: [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [queueing theory](<https://devfeed.tech/topics/queueing-theory.md>), [function as a service](<https://devfeed.tech/topics/function-as-a-service.md>), [Simulation](<https://devfeed.tech/topics/simulation.md>), [Latency](<https://devfeed.tech/topics/latency.md>)

Tags: [activation](<https://devfeed.tech/tags/activation.md>), [automatic](<https://devfeed.tech/tags/automatic.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [delay](<https://devfeed.tech/tags/delay.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [faas](<https://devfeed.tech/tags/faas.md>), [framework](<https://devfeed.tech/tags/framework.md>), [h2](<https://devfeed.tech/tags/h2.md>), [java](<https://devfeed.tech/tags/java.md>), [load](<https://devfeed.tech/tags/load.md>), [metric](<https://devfeed.tech/tags/metric.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [modeling](<https://devfeed.tech/tags/modeling.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [strategies](<https://devfeed.tech/tags/strategies.md>)

### AI overview

The study compares scale-per-request (SPR), concurrency-level scaling (CLS), and metric-based scaling (MBS) using a unified queueing model: analytical queueing networks combined with queueing Petri nets in Java Modeling Tools, evaluated under two-phase hyper-exponential arrivals. It tracks throughput, mean response time, system population, and power while modeling function-instance activation, concurrency limits, and queue buildup at saturation. The abstract reports a performance-stability trade-off: SPR has the lowest delay at moderate load but is fragile near capacity; CLS depends on concurrency tokens and is highly configuration-sensitive under bursty conditions; MBS provides the steadiest QoS across the tested workload range by limiting utilization and queue growth under critical load.

### Source excerpt

arXiv:2610.35564v1 Announce Type: new Abstract: Serverless computing platforms must preserve quality of service (QoS) while adapting to highly bursty and unpredictable workloads. To cope with workload fluctuations while satisfying QoS requirements and service-level agreements (SLAs), these platforms rely on automatic resource scaling. Commercial function-as-a-service (FaaS) platforms employ different autoscaling strategies to dynamically adjust the number of active function instances and the available processing capacity. In this work, three representative autoscaling strategies are modeled and compared: scale-per-request (SPR), concurrencylevel scaling (CLS), and metric-based scaling (MBS). To enable systematic evaluation independent of proprietary platform-specific implementations, we develop a unified modeling framework that combines analytical queueing network (QN) modeling with queueing Petri nets (QPN) implemented in Java Modeling Tools (JMT) to evaluate autoscaling behavior under two-phase hyper-exponential (H2) arrivals. Evaluation is conducted using four system-level metrics: throughput, mean response time, system population, and system power. The framework captures dynamic function instance (FI) activation, concurrency constraints, and queue buildup under saturation. Comparative analysis reveals a clear trade-off between peak performance and stability: SPR provides the lowest delay under moderate load but becomes fragile near capacity limits; CLS is governed by concurrency tokens and is highly sensitive to configuration under bursty conditions; whereas MBS provides the most stable QoS across the workload range by keeping utilization below a critical region and preventing explosive queue growth under critical load.

## Kubernetes Autoscaling: A Practical Guide to Controlling Cloud Costs

DevFeed: [Kubernetes Autoscaling: A Practical Guide to Controlling Cloud Costs](<https://devfeed.tech/articles/kubernetes-autoscaling-a-practical-guide-to-controlling-cloud-costs-88139.md>)

Original publisher: [Read original article](<https://www.urolime.com/blogs/kubernetes-autoscaling-a-practical-guide-to-controlling-cloud-costs/>)

Author: Urolime Technologies

Published: 2026-10-15T17:58:44Z

Content type: tutorial

Language: en

Sources: [Kubernetes Archives - Urolime Blogs](<https://devfeed.tech/sources/kubernetes-archives-urolime-blogs.md>)

Topics: [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [cloud-architecture](<https://devfeed.tech/tags/cloud-architecture.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cost-optimization](<https://devfeed.tech/tags/cost-optimization.md>), [costs](<https://devfeed.tech/tags/costs.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [finops](<https://devfeed.tech/tags/finops.md>), [guide](<https://devfeed.tech/tags/guide.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-autoscaling](<https://devfeed.tech/tags/kubernetes-autoscaling.md>), [kubernetes-consulting](<https://devfeed.tech/tags/kubernetes-consulting.md>), [scalability](<https://devfeed.tech/tags/scalability.md>)

### AI overview

A practical guide to controlling Kubernetes autoscaling costs. It explains horizontal Pod and node scaling, recommends rightsizing resources and selecting metrics that reflect actual demand, and discusses scaling limits, scale-to-zero tradeoffs, and cost visibility.

### Source excerpt

Cloud architecture is created in a way to be scalable. However, lack of controls leads to high scalability resulting in high cloud costs. With Kubernetes, autoscaling may help in making sure that the infrastructure is scaled in line with real demand. In case of increased load, more resources may be created, and, conversely, in case [...]

## CircleCI Makes Machine Runner Orchestrator Generally Available

DevFeed: [CircleCI Makes Machine Runner Orchestrator Generally Available](<https://devfeed.tech/articles/circleci-makes-machine-runner-orchestrator-generally-available-83966.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/circleci-machine-runner/>)

Author: Craig Risi

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

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [CircleCI](<https://devfeed.tech/topics/circleci.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [circleci](<https://devfeed.tech/tags/circleci.md>), [circleci-machine-runner](<https://devfeed.tech/tags/circleci-machine-runner.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [continuous-delivery](<https://devfeed.tech/tags/continuous-delivery.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [devops](<https://devfeed.tech/tags/devops.md>), [eks](<https://devfeed.tech/tags/eks.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [gke](<https://devfeed.tech/tags/gke.md>), [go](<https://devfeed.tech/tags/go.md>), [google-kubernetes-engine](<https://devfeed.tech/tags/google-kubernetes-engine.md>), [grpc](<https://devfeed.tech/tags/grpc.md>), [heap](<https://devfeed.tech/tags/heap.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-operator](<https://devfeed.tech/tags/kubernetes-operator.md>), [news](<https://devfeed.tech/tags/news.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [virtual-machines](<https://devfeed.tech/tags/virtual-machines.md>)

### AI overview

CircleCI's Machine Runner Orchestrator 1.0.0 is generally available, scaling self-hosted machine runner VMs with CI workload demand. It supports CPU, GPU, and ARM resource classes and Kubernetes environments including GKE, AKS, EKS, and KubeVirt. Existing preview installations require a migration that temporarily takes runners offline; the release also fixes two high-severity Go gRPC vulnerabilities.

### Source excerpt

CircleCI has made its Machine Runner Orchestrator 1.0.0 generally available, providing automated scaling of self-hosted machine runner virtual machines according to CI workload demand. By Craig Risi

## Maximize GPU Infrastructure Utilization with Better Workload Balancing

DevFeed: [Maximize GPU Infrastructure Utilization with Better Workload Balancing](<https://devfeed.tech/articles/maximize-gpu-infrastructure-utilization-with-better-workload-balancing-77997.md>)

Original publisher: [Read original article](<https://wf.coreweave.com/blog/maximize-gpu-infrastructure-utilization-with-better-workload-balancing>)

Author: CoreWeave

Published: 2026-10-02T14:12:41Z

Content type: article

Language: en

Sources: [Coreweave Blog Posts](<https://devfeed.tech/sources/coreweave-blog-posts.md>)

Topics: [AI Platform](<https://devfeed.tech/topics/ai-platform.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [GPU](<https://devfeed.tech/topics/gpu.md>), [wasmCloud](<https://devfeed.tech/topics/wasmcloud.md>)

Tags: [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [content-type](<https://devfeed.tech/tags/content-type.md>), [gpu-infrastructure](<https://devfeed.tech/tags/gpu-infrastructure.md>), [gpu-utilization](<https://devfeed.tech/tags/gpu-utilization.md>), [inference](<https://devfeed.tech/tags/inference.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [slurm](<https://devfeed.tech/tags/slurm.md>), [sunk](<https://devfeed.tech/tags/sunk.md>), [training](<https://devfeed.tech/tags/training.md>)

### AI overview

The article describes SUNK, CoreWeave's implementation of Slurm on Kubernetes, which lets AI teams run training and inference workloads on a shared cluster. It says this can improve GPU utilization, simplify resource allocation and scaling, and reduce the need to manage separate clusters.

### Source excerpt

See how SUNK layers Slurm and Kubernetes environments to boost GPU utilization, simplify scaling, and speed AI development by balancing training and inference workloads on a single cluster.

## On-demand GPU infrastructure startup GMI Cloud raises $263M to fuel global expansion

DevFeed: [On-demand GPU infrastructure startup GMI Cloud raises $263M to fuel global expansion](<https://devfeed.tech/articles/on-demand-gpu-infrastructure-startup-gmi-cloud-raises-263m-to-fuel-global-expansion-62525.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/09/30/on-demand-gpu-infrastructure-startup-gmi-cloud-raises-263m-to-fuel-global-expansion/>)

Author: Mike Wheatley

Published: 2026-09-30T13:00:57Z

Content type: news

Language: en

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

Topics: [baseten](<https://devfeed.tech/topics/baseten.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Deployment & Scaling](<https://devfeed.tech/topics/deployment-scaling.md>), [CUDA-X](<https://devfeed.tech/topics/cuda-x.md>)

Tags: [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-infrastructure-as-a-service](<https://devfeed.tech/tags/ai-infrastructure-as-a-service.md>), [ai-training](<https://devfeed.tech/tags/ai-training.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [alex-yeh](<https://devfeed.tech/tags/alex-yeh.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [coreweave](<https://devfeed.tech/tags/coreweave.md>), [credit-facility](<https://devfeed.tech/tags/credit-facility.md>), [data-centers](<https://devfeed.tech/tags/data-centers.md>), [fund-raise](<https://devfeed.tech/tags/fund-raise.md>), [funding](<https://devfeed.tech/tags/funding.md>), [gmi-cloud](<https://devfeed.tech/tags/gmi-cloud.md>), [gpu-infrastructure](<https://devfeed.tech/tags/gpu-infrastructure.md>), [gpus](<https://devfeed.tech/tags/gpus.md>), [gpus-on-demand](<https://devfeed.tech/tags/gpus-on-demand.md>), [infra](<https://devfeed.tech/tags/infra.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [nebius-group](<https://devfeed.tech/tags/nebius-group.md>), [neocloud](<https://devfeed.tech/tags/neocloud.md>), [news](<https://devfeed.tech/tags/news.md>), [series-b](<https://devfeed.tech/tags/series-b.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>), [top-story-5](<https://devfeed.tech/tags/top-story-5.md>)

### AI overview

GMI Cloud raised a $223 million Series B and secured a $440 million credit facility to expand its AI infrastructure business. Its Kubernetes-based Cluster Engine provisions GPU clusters for training and inference workloads, and the company highlights its data center presence in Asia-Pacific as an advantage for regional customers.

### Source excerpt

Taiwan-based neocloud GMI Cloud Inc. wants to capitalize on what it says is an "unprecedented" demand for artificial intelligence computing power after raising a massive $663 million in funding from two sources. The startup said today it has just closed on a $223 million Series B round of funding led by the robotics and AI-focused [...] The post On-demand GPU infrastructure startup GMI Cloud raises $263M to fuel global expansion appeared first on SiliconANGLE.

## Why Your Rules Engine Deserves Its Own Kubernetes Node Pool

DevFeed: [Why Your Rules Engine Deserves Its Own Kubernetes Node Pool](<https://devfeed.tech/articles/why-your-rules-engine-deserves-its-own-kubernetes-node-pool-60410.md>)

Original publisher: [Read original article](<https://hackernoon.com/why-your-rules-engine-deserves-its-own-kubernetes-node-pool?source=rss>)

Author: Himashi Meththasena

Published: 2026-09-26T15:15:01Z

Content type: article

Language: en

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

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>), [Open Policy Agent](<https://devfeed.tech/topics/open-policy-agent.md>), [Parsing](<https://devfeed.tech/topics/parsing.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [cloud-architecture](<https://devfeed.tech/tags/cloud-architecture.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [cpu-throttling](<https://devfeed.tech/tags/cpu-throttling.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-node-pools](<https://devfeed.tech/tags/kubernetes-node-pools.md>), [kubernetes-resource-management](<https://devfeed.tech/tags/kubernetes-resource-management.md>), [kubernetes-taints](<https://devfeed.tech/tags/kubernetes-taints.md>), [latency](<https://devfeed.tech/tags/latency.md>), [latency-sensitive-workloads](<https://devfeed.tech/tags/latency-sensitive-workloads.md>), [memory-pressure](<https://devfeed.tech/tags/memory-pressure.md>), [resource](<https://devfeed.tech/tags/resource.md>), [rules-engines](<https://devfeed.tech/tags/rules-engines.md>)

### AI overview

The article argues that production rules engines should receive dedicated Kubernetes node pools because CPU throttling, memory spikes, and shared-node contention can increase latency and expand the impact of failures. It recommends basing isolation decisions on measured contention and resource needs.

### Source excerpt

Dedicated Kubernetes node pools can isolate latency-sensitive rules engines, but the decision should be based on measured contention and resource needs.

## Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments

DevFeed: [Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments](<https://devfeed.tech/articles/stateless-mcp-removes-session-affinity-requirements-for-aws-server-deployments-59805.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/09/aws-stateless-mcp/>)

Author: Leela Kumili

Published: 2026-09-25T12:58:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [session affinity](<https://devfeed.tech/topics/session-affinity.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [Server](<https://devfeed.tech/topics/server.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [retry](<https://devfeed.tech/topics/retry.md>), [Security](<https://devfeed.tech/topics/security.md>), [context](<https://devfeed.tech/topics/context.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-architecture](<https://devfeed.tech/tags/ai-architecture.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-stateless-mcp](<https://devfeed.tech/tags/aws-stateless-mcp.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [development](<https://devfeed.tech/tags/development.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [load-balancing](<https://devfeed.tech/tags/load-balancing.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [retries](<https://devfeed.tech/tags/retries.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [servers](<https://devfeed.tech/tags/servers.md>), [session-affinity](<https://devfeed.tech/tags/session-affinity.md>), [w3c](<https://devfeed.tech/tags/w3c.md>)

### AI overview

AWS explains that the latest Model Context Protocol specification removes protocol-level sessions, sticky-session requirements, and session storage for remote MCP servers. This enables independent request routing and simpler horizontal scaling, while shifting application state, retries, observability, and idempotency responsibilities to other layers.

### Source excerpt

AWS details how the latest Model Context Protocol specification removes protocol-level sessions, sticky-session requirements, and session storage for remote MCP servers. The change enables independent request routing and simpler horizontal scaling while shifting application state, retries, observability, and idempotency concerns to other layers. By Leela Kumili

## Cloud Cost Optimization Strategies for 2026 to Reduce Spend

DevFeed: [Cloud Cost Optimization Strategies for 2026 to Reduce Spend](<https://devfeed.tech/articles/cloud-cost-optimization-strategies-for-2026-to-reduce-spend-59432.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/cloud-cost-optimization-strategies>)

Author: Kelsey Rosen

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

Content type: article

Language: en

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

Topics: [Cloud](<https://devfeed.tech/topics/cloud.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-cost-optimization](<https://devfeed.tech/tags/cloud-cost-optimization.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [engineering-and-devops](<https://devfeed.tech/tags/engineering-and-devops.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [manage](<https://devfeed.tech/tags/manage.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

This practical guide explains how platform engineering and DevOps teams can optimize cloud spending while preserving workload reliability. It covers spend allocation, visibility, Kubernetes rightsizing, autoscaling, idle-resource shutdowns, commitment discounts, anomaly alerts, and ongoing governance. It also notes that cloud cost practices increasingly apply to AI spending.

### Source excerpt

Learn how to allocate cloud spend, rightsize Kubernetes safely, stop idle resources, manage commitments, and prevent cost spikes without risking reliability. | Blog

## Comparison of Cluster Autoscaler and KEDA MachineSet Autoscaling on Red Hat OpenShift

DevFeed: [Comparison of Cluster Autoscaler and KEDA MachineSet Autoscaling on Red Hat OpenShift](<https://devfeed.tech/articles/comparison-of-cluster-autoscaler-and-keda-machineset-autoscaling-on-red-hat-openshift-57456.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/09/21/comparison-of-cluster-autoscaler-and-keda-machineset-autoscaling-on-red-hat-openshift>)

Author: Ramon Gordillo Gutierrez, Jose Ortiz Padilla

Published: 2026-09-21T13:17:24Z

Content type: comparison

Language: en

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

Topics: [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [containers](<https://devfeed.tech/tags/containers.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [performance-and-scale-engineering](<https://devfeed.tech/tags/performance-and-scale-engineering.md>)

### AI overview

This comparison examines Red Hat OpenShift Cluster Autoscaler and KEDA-based MachineSet Autoscaling. Cluster Autoscaler reacts to unschedulable pods and resource constraints, while KEDA scales from external or custom metrics such as PromQL thresholds. The article also contrasts their configuration, safety features, and workload-fit considerations.

### Source excerpt

As discussed in our previous articles, there are different solutions for scaling your Red Hat OpenShift compute infrastructure. In our first article, we demonstrated the built-in, Kubernetes-native Cluster Autoscaler, and in our second article we demonstrated the metrics-driven MachineSet Autoscaler with KEDA. The post Comparison of Cluster Autoscaler and KEDA MachineSet Autoscaling on Red Hat OpenShift appeared first on Red Hat Developer.

## Deploy Hugging Face models on Amazon SageMaker AI with coding agents

DevFeed: [Deploy Hugging Face models on Amazon SageMaker AI with coding agents](<https://devfeed.tech/articles/deploy-hugging-face-models-on-amazon-sagemaker-ai-with-coding-agents-55157.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/deploy-hugging-face-models-on-amazon-sagemaker-ai-with-coding-agents/>)

Author: Dario Salvati

Published: 2026-09-18T15:25:23Z

Content type: tutorial

Language: en

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

Topics: [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [hugging face](<https://devfeed.tech/topics/hugging-face.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [inference-endpoints](<https://devfeed.tech/topics/inference-endpoints.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [vllm](<https://devfeed.tech/topics/vllm.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-sagemaker-ai](<https://devfeed.tech/tags/amazon-sagemaker-ai.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [hugging-face](<https://devfeed.tech/tags/hugging-face.md>), [inference](<https://devfeed.tech/tags/inference.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

A tutorial on using six open-source agent skills to deploy Hugging Face models on Amazon SageMaker AI. It covers selecting serving containers, configuring autoscaling and CloudWatch alarms, supporting multiple inference modes, and verifying teardown paths.

### Source excerpt

Deploy production-ready Hugging Face models on Amazon SageMaker AI using six open-source agent skills. Point a coding agent at a model and get back a real-time endpoint with the right serving container, autoscaling, Amazon CloudWatch alarms, and a verified teardown path.

## Simplify application migrations to AWS with Elastic Beanstalk

DevFeed: [Simplify application migrations to AWS with Elastic Beanstalk](<https://devfeed.tech/articles/simplify-application-migrations-to-aws-with-elastic-beanstalk-50013.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/migration-and-modernization/simplify-application-migrations-to-aws-with-elastic-beanstalk/>)

Author: Nitish Kulkarni

Published: 2026-09-17T19:29:03Z

Content type: release

Language: en

Sources: [Migration & Modernization](<https://devfeed.tech/sources/migration-modernization.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Network](<https://devfeed.tech/topics/network.md>), [container](<https://devfeed.tech/topics/container.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-elastic-beanstalk](<https://devfeed.tech/tags/aws-elastic-beanstalk.md>), [compute](<https://devfeed.tech/tags/compute.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [learning-levels](<https://devfeed.tech/tags/learning-levels.md>), [migration](<https://devfeed.tech/tags/migration.md>), [networking](<https://devfeed.tech/tags/networking.md>), [observability](<https://devfeed.tech/tags/observability.md>), [scaling](<https://devfeed.tech/tags/scaling.md>)

### AI overview

AWS Elastic Beanstalk introduces a deployment mode for managing multiple applications on shared infrastructure operated and upgraded by AWS. The post describes migrations from other platforms and legacy applications, including Windows .NET, Java, and PHP applications, with support for source code, Dockerfiles, and prebuilt container images.

### Source excerpt

Today, AWS Elastic Beanstalk introduces a new deployment mode that manages multiple applications on shared infrastructure that AWS creates, operates, and upgrades for you. Whether you provide source code, a Dockerfile, or a prebuilt container image, Elastic Beanstalk takes care of building and deploying your application. It also configures networking, autoscaling, and observability. You manage [...]

## AWS Elastic Beanstalk introduces Cluster Mode

DevFeed: [AWS Elastic Beanstalk introduces Cluster Mode](<https://devfeed.tech/articles/aws-elastic-beanstalk-introduces-cluster-mode-42086.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/aws/aws-elastic-beanstalk-introduces-cluster-mode/>)

Author: Channy Yun (윤석찬)

Published: 2026-09-17T19:20:21Z

Content type: release

Language: en

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

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Amazon Elastic Kubernetes Service](<https://devfeed.tech/topics/amazon-elastic-kubernetes-service.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Provisioning](<https://devfeed.tech/topics/provisioning.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [AWS Certificate Manager](<https://devfeed.tech/topics/aws-certificate-manager.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [application](<https://devfeed.tech/tags/application.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-certificate-manager](<https://devfeed.tech/tags/aws-certificate-manager.md>), [aws-elastic-beanstalk](<https://devfeed.tech/tags/aws-elastic-beanstalk.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [code](<https://devfeed.tech/tags/code.md>), [compute](<https://devfeed.tech/tags/compute.md>), [container](<https://devfeed.tech/tags/container.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [dockerfiles](<https://devfeed.tech/tags/dockerfiles.md>), [https](<https://devfeed.tech/tags/https.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [launch](<https://devfeed.tech/tags/launch.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [news](<https://devfeed.tech/tags/news.md>), [provisioning](<https://devfeed.tech/tags/provisioning.md>)

### AI overview

AWS Elastic Beanstalk introduces a fully managed Cluster Mode that runs multiple applications on shared infrastructure powered by Amazon EKS. It also highlights AI-assisted environment analysis, GitHub Actions deployment, observability, traffic-splitting deployments with rollback, autoscaling, secrets management, and HTTPS by default.

### Source excerpt

Run an application on AWS Elastic Beanstalk Cluster Mode without provisioning or operating the compute underneath it. You provide a container image or source code; Elastic Beanstalk with service-operated compute creates and operates the environment that runs it.

## Multi-modal autoscaling with Amazon EC2 Auto Scaling: adding signals for faster, more reliable scaling

DevFeed: [Multi-modal autoscaling with Amazon EC2 Auto Scaling: adding signals for faster, more reliable scaling](<https://devfeed.tech/articles/multi-modal-autoscaling-with-amazon-ec2-auto-scaling-adding-signals-for-faster-more-reliable-scaling-42095.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/multi-modal-autoscaling-with-amazon-ec2-auto-scaling-adding-signals-for-faster-more-reliable-scaling/>)

Author: Shubhendu Dubey

Published: 2026-09-17T18:18:38Z

Content type: tutorial

Language: en

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

Topics: [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS CloudFormation](<https://devfeed.tech/topics/aws-cloudformation.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [api](<https://devfeed.tech/tags/api.md>), [auto-scaling](<https://devfeed.tech/tags/auto-scaling.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [forecasting](<https://devfeed.tech/tags/forecasting.md>), [latency](<https://devfeed.tech/tags/latency.md>), [load](<https://devfeed.tech/tags/load.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This tutorial explains multi-modal autoscaling with Amazon EC2 Auto Scaling by combining CPU, request-count, application-level, and predictive signals. It describes a controlled test in which application metrics avoided rejected checkout sessions and reduced p99 latency compared with CPU-only scaling.

### Source excerpt

Multi-modal autoscaling with Amazon EC2 Auto Scaling combines infrastructure metrics like CPU with application-level signals, so a group scales on the demand its users create. In this post, we show you how to implement it, with code samples and results from a controlled test.

## Neon launches a production-ready backend suite with Postgres, storage, functions, auth, and AI Gateway

DevFeed: [Neon launches a production-ready backend suite with Postgres, storage, functions, auth, and AI Gateway](<https://devfeed.tech/articles/the-neon-backend-is-ga-a-complete-set-of-primitives-so-agents-can-build-42099.md>)

Original publisher: [Read original article](<https://neon.com/blog/neon-backend-is-ga>)

Author: Bryan Clark

Published: 2026-09-17T12:00:00Z

Content type: release

Language: en

Sources: [Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [Back end](<https://devfeed.tech/topics/backend.md>), [Database](<https://devfeed.tech/topics/database.md>), [service](<https://devfeed.tech/topics/service.md>), [function](<https://devfeed.tech/topics/function.md>), [gateway](<https://devfeed.tech/topics/gateway.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Provisioning](<https://devfeed.tech/topics/provisioning.md>)

Tags: [ai-models](<https://devfeed.tech/tags/ai-models.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [backend](<https://devfeed.tech/tags/backend.md>), [backends](<https://devfeed.tech/tags/backends.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [company](<https://devfeed.tech/tags/company.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [functions](<https://devfeed.tech/tags/functions.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [github](<https://devfeed.tech/tags/github.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

Neon announces that its backend suite is generally available for production. The suite combines Lakebase Postgres, Object Storage, Functions, Managed Better Auth, and AI Gateway around a shared architecture designed for developer and coding-agent workflows.

### Source excerpt

Neon is now a complete suite of backend primitives built around the database and rooted on the lakebase architecture: Lakebase Postgres, Object Storage, Functions, Managed Better Auth, and AI Gateway. All tools are GA and ready for production. Tell your agent to deploy them.

## Kubernetes Cost Optimization: A Practical Guide for Teams

DevFeed: [Kubernetes Cost Optimization: A Practical Guide for Teams](<https://devfeed.tech/articles/kubernetes-cost-optimization-a-practical-guide-for-teams-55043.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/kubernetes-cost-optimization>)

Author: Kelsey Rosen

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

Content type: article

Language: en

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

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [finops](<https://devfeed.tech/topics/finops.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cost-optimization](<https://devfeed.tech/tags/cost-optimization.md>), [devops](<https://devfeed.tech/tags/devops.md>), [guide](<https://devfeed.tech/tags/guide.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [memory](<https://devfeed.tech/tags/memory.md>), [namespaces](<https://devfeed.tech/tags/namespaces.md>), [practical](<https://devfeed.tech/tags/practical.md>)

### AI overview

A practical guide to reducing Kubernetes costs through right-sizing CPU and memory requests, autoscaling, discounted spot or preemptible nodes, and namespace-level cost allocation. It explains how scheduler reservations, shared clusters, and incomplete ownership mapping can hide waste.

### Source excerpt

Practical Kubernetes cost optimization: right-sizing, autoscaling, spot and preemptible nodes, and namespace-level cost allocation for DevOps teams. | Blog

## Lyft Moves Streaming Fleet to Apache Flink Kubernetes Operator

DevFeed: [Lyft Moves Streaming Fleet to Apache Flink Kubernetes Operator](<https://devfeed.tech/articles/lyft-moves-streaming-fleet-to-apache-flink-kubernetes-operator-30910.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/09/lyft-flink-k8s-operator/>)

Author: Mark Silvester

Published: 2026-09-16T11:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Apache Flink](<https://devfeed.tech/topics/apache-flink.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [apache-flink](<https://devfeed.tech/tags/apache-flink.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [flink](<https://devfeed.tech/tags/flink.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-operator](<https://devfeed.tech/tags/kubernetes-operator.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [lyft-flink-k8s-operator](<https://devfeed.tech/tags/lyft-flink-k8s-operator.md>), [news](<https://devfeed.tech/tags/news.md>), [testing](<https://devfeed.tech/tags/testing.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

Lyft moved hundreds of production Apache Flink jobs from its in-house Kubernetes operator to the Apache Flink Kubernetes Operator. The change enabled last-state upgrades, in-place autoscaling, and resource autotuning, while Lyft adapted legacy deployment specifications through its deploy API and contributed a fix for a configuration-renaming bug.

### Source excerpt

Lyft has moved hundreds of production Flink jobs from a 2020 in-house Kubernetes operator to the Apache Flink Kubernetes Operator, unlocking last-state upgrades, in-place autoscaling and resource autotuning across the fleet. By Mark Silvester

## Apache Flink Kubernetes Operator 1.16.0 Release Announcement

DevFeed: [Apache Flink Kubernetes Operator 1.16.0 Release Announcement](<https://devfeed.tech/articles/apache-flink-kubernetes-operator-1-16-0-release-announcement-48539.md>)

Original publisher: [Read original article](<https://flink.apache.org/2026/09/15/apache-flink-kubernetes-operator-1.16.0-release-announcement/>)

Published: 2026-09-15T08:00:00Z

Content type: release

Language: en

Sources: [Apache Flink](<https://devfeed.tech/sources/apache-flink-stateful-computations-over-data-streams-on-apache-flink.md>)

Topics: [Apache Flink](<https://devfeed.tech/topics/apache-flink.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Parallelism](<https://devfeed.tech/topics/parallelism.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [Security](<https://devfeed.tech/topics/security.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>)

Tags: [announcement](<https://devfeed.tech/tags/announcement.md>), [apache-flink](<https://devfeed.tech/tags/apache-flink.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [extensibility](<https://devfeed.tech/tags/extensibility.md>), [flink](<https://devfeed.tech/tags/flink.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [parallelism](<https://devfeed.tech/tags/parallelism.md>), [release](<https://devfeed.tech/tags/release.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Apache Flink Kubernetes Operator 1.16.0 is announced with a restructured documentation site, extensibility improvements, a new default for autoscaler parallelism alignment, Kubernetes-native pod resource requirements, and fixes covering Blue/Green deployments, session jobs, savepoint reliability, and security hardening.

### Source excerpt

The Apache Flink community is excited to announce the release of Flink Kubernetes Operator 1.16.0! This release centers on extensibility and documentation: a completely restructured documentation site, a new default for autoscaler parallelism alignment, a trio of pluggable autoscaler SPIs (custom evaluators, scaling executors, and alignment modes), Kubernetes-native pod ResourceRequirements, and a range of Blue/Green, session job, savepoint reliability, and security hardening fixes. We encourage you to download the release and share your experience with the community through the Flink mailing lists or JIRA!

## Enterprise-Grade Precision for Long-Context Multimodal Embedding Inference on Cloud TPU

DevFeed: [Enterprise-Grade Precision for Long-Context Multimodal Embedding Inference on Cloud TPU](<https://devfeed.tech/articles/enterprise-grade-precision-for-long-context-multimodal-embedding-inference-on-cloud-tpu-4210.md>)

Original publisher: [Read original article](<https://developers.googleblog.com/enterprise-grade-precision-for-long-context-multimodal-embedding-inference-on-cloud-tpu/>)

Author: Anthony Su; Injae Kwak

Published: 2026-09-12T11:04:33.891311Z

Content type: article

Language: en

Sources: [Google Developers Blog](<https://devfeed.tech/sources/google-developers-blog.md>)

Topics: [Embeddings](<https://devfeed.tech/topics/embeddings.md>), [vllm](<https://devfeed.tech/topics/vllm.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [long-context](<https://devfeed.tech/topics/long-context.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Google](<https://devfeed.tech/topics/google.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [model-deployment](<https://devfeed.tech/topics/model-deployment.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [embedding](<https://devfeed.tech/tags/embedding.md>), [github](<https://devfeed.tech/tags/github.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [inference](<https://devfeed.tech/tags/inference.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [long-context](<https://devfeed.tech/tags/long-context.md>), [multimodal](<https://devfeed.tech/tags/multimodal.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [retrieval](<https://devfeed.tech/tags/retrieval.md>), [tpu](<https://devfeed.tech/tags/tpu.md>), [vllm](<https://devfeed.tech/tags/vllm.md>)

### AI overview

This article explains how Google Cloud integrated native TPU support into vLLM to serve long-context, multimodal embedding models at production scale. It describes elastic TPU provisioning with Google Kubernetes Engine, autoscaling across accelerator types, and TPU-specific optimizations for long sequences and chunked prefill. The resulting setup is designed to preserve numerical parity with GPU reference baselines while supporting high-throughput semantic retrieval applications.

### Source excerpt

Google Cloud has natively integrated TPU support into the vLLM serving engine, allowing developers to elastically scale high-demand embedding pipelines using Google Kubernetes Engine (GKE). To handle massive 15K+ token contexts for models like Qwen3-Embedding-8B, the engineering team implemented TPU-specific optimizations such as hardware-safe tensor alignment, JAX/XLA compilation pre-warming, and a hybrid StepPool architecture for chunked prefill management. These enhancements achieve near-perfect numerical parity with reference GPU baselines, and developers can immediately leverage the open-sourced setup recipes on the AI-Hypercomputer GitHub to build their own high-throughput semantic retrieval applications.

## Reduce inference cold starts on Amazon SageMaker HyperPod with model caching

DevFeed: [Reduce inference cold starts on Amazon SageMaker HyperPod with model caching](<https://devfeed.tech/articles/reduce-inference-cold-starts-on-amazon-sagemaker-hyperpod-with-model-caching-4739.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/reduce-inference-cold-starts-on-amazon-sagemaker-hyperpod-with-model-caching/>)

Author: Kareem Syed-Mohammed

Published: 2026-09-10T21:37:49Z

Content type: tutorial

Language: en

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

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [Inference](<https://devfeed.tech/topics/inference.md>), [model-deployment](<https://devfeed.tech/topics/model-deployment.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-sagemaker](<https://devfeed.tech/tags/amazon-sagemaker.md>), [amazon-sagemaker-hyperpod](<https://devfeed.tech/tags/amazon-sagemaker-hyperpod.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [caching](<https://devfeed.tech/tags/caching.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [inference](<https://devfeed.tech/tags/inference.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [llm](<https://devfeed.tech/tags/llm.md>)

### AI overview

Amazon SageMaker HyperPod model caching preloads model weights and container images onto cluster nodes, reducing inference-pod cold starts by serving assets from local NVMe storage.

### Source excerpt

Amazon SageMaker HyperPod now supports model caching for inference, which pre-loads model weights and container images onto cluster nodes so pods read from local NVMe storage instead of downloading over the network. Learn how model caching cuts cold starts from tens of minutes to seconds, how it works, and how to enable it.

## Announcing On-Demand Compute: Instant compute for your most intensive workloads

DevFeed: [Announcing On-Demand Compute: Instant compute for your most intensive workloads](<https://devfeed.tech/articles/announcing-on-demand-compute-instant-compute-for-your-most-intensive-workloads-5457.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/on-demand-compute>)

Author: Melvyn Peignon

Published: 2026-09-10T14:22:58Z

Content type: release

Language: en

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

Topics: [clickhouse](<https://devfeed.tech/topics/clickhouse.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [compute](<https://devfeed.tech/tags/compute.md>), [cost](<https://devfeed.tech/tags/cost.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [production](<https://devfeed.tech/tags/production.md>), [scale](<https://devfeed.tech/tags/scale.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

ClickHouse announces a private preview of On-Demand Compute, which allocates shared workers to eligible individual queries so intensive workloads can run without competing with a service's primary compute.

### Source excerpt

ClickHouse On-Demand Compute lets you scale individual queries with additional workers, run intensive workloads without disrupting production, and use compute when you need it.

## Improving Lakebase Postgres compute cache

DevFeed: [Improving Lakebase Postgres compute cache](<https://devfeed.tech/articles/improving-lakebase-postgres-compute-cache-11541.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/improving-lakebase-postgres-compute-cache>)

Author: David Wein; Sunil Kamath; Haoyu Huang

Published: 2026-09-10T13:47:03Z

Content type: article

Language: en

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

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [Database](<https://devfeed.tech/topics/database.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [filesystem](<https://devfeed.tech/tags/filesystem.md>), [latency](<https://devfeed.tech/tags/latency.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [memory](<https://devfeed.tech/tags/memory.md>), [s3](<https://devfeed.tech/tags/s3.md>), [storage](<https://devfeed.tech/tags/storage.md>)

### AI overview

This Databricks article describes improvements to compute-side caching for Lakebase Postgres, a disaggregated storage system backed by object storage such as Amazon S3. It explains PostgreSQL shared buffers, the operating system page cache, and the planned use of dynamically autoscaling shared buffers consuming up to 75% of compute memory. It also introduces a local file cache as an incremental solution for fixed compute instances.

### Source excerpt

The disaggregated storage model of Lakebase Postgres provides a feature rich, flexible...

## Introducing preemptible compute: the same compute, half the price

DevFeed: [Introducing preemptible compute: the same compute, half the price](<https://devfeed.tech/articles/introducing-preemptible-compute-the-same-compute-half-the-price-80191.md>)

Original publisher: [Read original article](<https://www.together.ai/blog/introducing-preemptible-compute-the-same-compute-half-the-price>)

Author: Pavneet Ahluwalia, Varun Chakravarthy

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

Content type: release

Language: en

Sources: [Together.ai](<https://devfeed.tech/sources/together-ai.md>)

Topics: [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [jobs](<https://devfeed.tech/topics/jobs.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [ai-compute](<https://devfeed.tech/tags/ai-compute.md>), [cost](<https://devfeed.tech/tags/cost.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [gpu-clusters](<https://devfeed.tech/tags/gpu-clusters.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>)

### AI overview

Together introduces preemptible compute in public preview for its Kubernetes GPU clusters. The nodes use spare capacity at a fixed 50% of the on-demand rate and can be reclaimed with up to five minutes for workloads to checkpoint and exit. The release targets interruptible jobs such as experiments, batch inference, and temporary bursts; critical components are meant to stay on standard nodes.

### Source excerpt

Together GPU Clusters now supports preemptible compute: the same GPU capacity at a flat 50% of the on-demand rate, with a five-minute drain window.

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