# Serverless

Serverless is a cloud application development and execution model in which developers deploy code without managing the underlying server infrastructure.

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

## Held While Waiting: What LLM Agent Sessions Reserve on Serverless and Agent Runtimes

DevFeed: [Held While Waiting: What LLM Agent Sessions Reserve on Serverless and Agent Runtimes](<https://devfeed.tech/articles/held-while-waiting-what-llm-agent-sessions-reserve-on-serverless-and-agent-runtimes-145792.md>)

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

Author: Mekhala Hithyshini Sreenivasa

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

Content type: article

Language: en

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

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-runtimes](<https://devfeed.tech/tags/agent-runtimes.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-pf](<https://devfeed.tech/tags/cs-pf.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [llm](<https://devfeed.tech/tags/llm.md>), [runtimes](<https://devfeed.tech/tags/runtimes.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [waiting](<https://devfeed.tech/tags/waiting.md>)

### AI overview

On Amazon Bedrock AgentCore, each conversation reserves its own environment while waiting for model replies: the excerpt reports a 2.7-second median wait versus an estimated 5-40 milliseconds of computation. This can exhaust environment capacity well before processor capacity. Two remedies are described: clients can close conversations to release environments sooner (the benchmark found environments otherwise stayed reserved 15 minutes after conversations averaging 33 seconds), while sharing environments across conversations requires platform support. In simulation, sharing one environment among 64 conversations used 59 times fewer environments, with 99% of replies delayed by at most 40 milliseconds. The computation estimates are uncertain; three measurement approaches each produced plausible but too-low values. The excerpt says only one surveyed agent runtime permits sharing in part, and identifies safe isolation of model-selected tools or code as an open problem.

### Source excerpt

arXiv:2611.26480v1 Announce Type: cross Abstract: LLM agents spend nearly all their time waiting for the model. On Amazon Bedrock AgentCore, our agents waited a median of 2.7 seconds for each model reply, then computed for an estimated 5 to 40 milliseconds. AgentCore does not charge for CPU during the wait. But it reserves a separate environment, a virtual machine with its own memory, for every conversation, and keeps it reserved until the conversation is closed. So 1,000 conversations reserve 1,000 environments to do the work of 2 to 15 processor cores. A service runs out of environments long before it runs out of processing power. The shortage has two causes, and each has a fix. An environment stays reserved after its conversation ends: in the customer-service benchmark we ran, a conversation lasts 33 seconds on average, but its environment is held for 15 minutes more unless the client closes it. And an environment serves only one conversation, which is mostly waiting: in our simulation, 64 conversations sharing one environment need 59 times fewer environments, and 99 of every 100 replies are delayed by at most 40 milliseconds. The milliseconds are an estimate because they are hard to measure: a stubbed model, a timer around the model call, and steps run back to back each gave a plausible number that was too low. We show how to avoid all three. Of the two fixes, closing needs only the client. Sharing needs the platform, and of the agent runtimes we surveyed only one allows it, in part. They keep conversations apart because an agent runs tools, and sometimes code, chosen by a model. The open problem is to keep them apart without reserving an environment for each while it waits.

## Introducing Amazon EMR Serverless Flex: Run non-urgent Spark jobs at a discount

DevFeed: [Introducing Amazon EMR Serverless Flex: Run non-urgent Spark jobs at a discount](<https://devfeed.tech/articles/introducing-amazon-emr-serverless-flex-run-non-urgent-spark-jobs-at-a-discount-144577.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/introducing-amazon-emr-serverless-flex-run-non-urgent-spark-jobs-at-a-discount/>)

Author: Neil Mukerje

Published: 2026-11-19T20:58:07Z

Content type: release

Language: en

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

Topics: [Apache Spark](<https://devfeed.tech/topics/spark.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [batch](<https://devfeed.tech/tags/batch.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [billing](<https://devfeed.tech/tags/billing.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [discount](<https://devfeed.tech/tags/discount.md>), [driver](<https://devfeed.tech/tags/driver.md>), [flex](<https://devfeed.tech/tags/flex.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [retries](<https://devfeed.tech/tags/retries.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [spark](<https://devfeed.tech/tags/spark.md>), [standard](<https://devfeed.tech/tags/standard.md>)

### AI overview

Amazon EMR Serverless Flex runs non-urgent Spark batch jobs on spare capacity at a fixed 60% discount on worker vCPU and memory charges compared with Standard. It automates Availability Zone and instance selection, protects the driver on a Standard worker, and retries tasks when Flex workers are reclaimed; optional Serverless Storage can reduce recomputation for shuffle-heavy jobs. Flex may start more slowly and run longer than Standard, and a job fails if no executor joins the driver within 20 minutes. In the described 103-query benchmark, all queries completed without resubmission; runtime was 7% longer at 1 TB and 30% longer at 3 TB, while estimated cost fell about 63% at both scales. Results vary with workload and spare capacity. Flex is enabled per job, so teams can compare it with Standard on flexible-deadline workloads.

### Source excerpt

Amazon EMR Serverless Flex is a new execution option that runs non-urgent Spark batch jobs on spare compute capacity at a fixed 60% discount compared to standard pricing. Flex handles Availability Zone selection, instance diversification, driver protection, and automatic retries, so jobs complete even when spare capacity is reclaimed.

## Amazon ElastiCache Serverless turns three

DevFeed: [Amazon ElastiCache Serverless turns three](<https://devfeed.tech/articles/amazon-elasticache-serverless-turns-three-144309.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/amazon-elasticache-serverless-turns-three/>)

Author: Karthik Konaparthi

Published: 2026-11-19T18:35:55Z

Content type: article

Language: en

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

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-memory](<https://devfeed.tech/tags/agent-memory.md>), [agent-toolkit](<https://devfeed.tech/tags/agent-toolkit.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [ai-coding-assistant](<https://devfeed.tech/tags/ai-coding-assistant.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [costs](<https://devfeed.tech/tags/costs.md>), [customers](<https://devfeed.tech/tags/customers.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [patch](<https://devfeed.tech/tags/patch.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

Amazon ElastiCache Serverless removes cache capacity planning by scaling with demand; billing is based on stored data (GB-hours) and requests (ECPUs). The article highlights Valkey's faster scaling, lower storage minimum and pricing, plus a 30% Database Savings Plans discount with a one-year commitment. New Valkey 9.0 features include public endpoints (IAM authentication and TLS 1.3 required), online migration from cluster-mode Valkey or Redis OSS with traffic continuing, search, and write-through DynamoDB caching. AWS applies minor and patch updates automatically; major-version upgrades are customer scheduled, and recent patching improvements preserve more connections and in-flight requests. Serverless is presented as a fit for variable traffic and many separate caches; node-based deployments may suit steady workloads, especially with reserved nodes and capacity-tuning staff. The article recommends estimating costs from actual stored data and representative request volume, then checking CloudWatch metrics in a trial workload. Serverless clients must support cluster mode and TLS.

### Source excerpt

In this post, we look back at three years of Amazon ElastiCache Serverless, show how customers use it, cover what we launched this year and how we patch your cache with minimal disruption, show how to estimate what it costs, and help you decide whether it fits your workload.

## Microsoft adds knowledge graphs, retrieval model to Foundry IQ for better AI grounding

DevFeed: [Microsoft adds knowledge graphs, retrieval model to Foundry IQ for better AI grounding](<https://devfeed.tech/articles/microsoft-adds-knowledge-graphs-retrieval-model-to-foundry-iq-for-better-ai-grounding-143172.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4250726/microsoft-adds-knowledge-graphs-retrieval-model-to-foundry-iq-for-better-ai-grounding.html>)

Author: Anirban Ghoshal

Published: 2026-11-19T12:56:43Z

Content type: news

Language: en

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

Topics: [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>), [AI-driven information retrieval](<https://devfeed.tech/topics/ai-driven-information-retrieval.md>), [information retrieval](<https://devfeed.tech/topics/information-retrieval.md>), [knowledge-engineering](<https://devfeed.tech/topics/knowledge-engineering.md>), [Serverless](<https://devfeed.tech/topics/serverless.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>), [ai-grounding](<https://devfeed.tech/tags/ai-grounding.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [analytics-artificial-intelligence-data-management](<https://devfeed.tech/tags/analytics-artificial-intelligence-data-management.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [automate](<https://devfeed.tech/tags/automate.md>), [build](<https://devfeed.tech/tags/build.md>), [build-ai-agents](<https://devfeed.tech/tags/build-ai-agents.md>), [business](<https://devfeed.tech/tags/business.md>), [capability](<https://devfeed.tech/tags/capability.md>), [conference](<https://devfeed.tech/tags/conference.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [connect](<https://devfeed.tech/tags/connect.md>), [data-management](<https://devfeed.tech/tags/data-management.md>), [foundry](<https://devfeed.tech/tags/foundry.md>), [graphs](<https://devfeed.tech/tags/graphs.md>), [grounding](<https://devfeed.tech/tags/grounding.md>), [knowledge](<https://devfeed.tech/tags/knowledge.md>), [knowledge-graphs](<https://devfeed.tech/tags/knowledge-graphs.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [model](<https://devfeed.tech/tags/model.md>), [retrieval](<https://devfeed.tech/tags/retrieval.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>)

### AI overview

Foundry IQ adds knowledge graphs, Microsoft-Retriever-1, and automatic retrieval-resource provisioning to help ground agents in enterprise data. Developers can supply an ontology or bring an existing graph; the service maps relationships across documents and records each connection's source, supporting questions that span multiple sources. Graphs are in public preview. Microsoft-Retriever-1 reformulates queries using enterprise terminology and decides whether to search again; it can be enabled on existing indexes and knowledge bases without extra provisioning or reindexing. It aims to reduce search rounds and reliance on large models for retrieval planning, though iterative searches may add latency and cost, and Microsoft has published no detailed performance comparisons. New Foundry projects will automatically receive a managed resource, removing the need to provision a separate Azure AI Search resource. That service is planned for public preview in December 2026, with usage-based serverless pricing. The text cautions that graph extraction can misread jargon or naming, graphs need validation and upkeep, and graph answers may cost more and take longer than routine search. Usage and

### Source excerpt

Microsoft is enhancing its Foundry IQ knowledge retrieval service with knowledge graphs, a specialized retrieval model and automatic infrastructure provisioning, seeking to make it easier for developers to build AI agents that can access, understand and reason over enterprise data. Grounding AI agents in organizational data is critical for enterprises to ensure they can deliver responses based on accurate, relevant, and up-to-date business information as they look to increasingly automate business workflows. The new knowledge graphs in Foundry IQ, announced at the Microsoft Ignite conference, will help agents connect related entities and facts across documents and organize enterprise content into topics, allowing them to answer questions that require information from multiple sources, the hyperscaler wrote in a blog post. In order to map relationships across documents, developers can add a graph configuration containing their ontology to an existing Foundry IQ knowledge source or bring an existing graph into the service. Foundry IQ then uses the ontology to map how documents, contacts, and information relate, while recording the source of each connection, it added. Alongside knowledge graphs, which are currently in public preview, the hyperscaler is adding a new retrieval model named Microsoft-Retriever-1 to reduce the number of searches and the reliance on large language models (LLMs) for retrieval planning in an effort to help developers lower latency and token consumption. The new model, according to the hyperscaler, interprets user queries, reformulates them using terminology found in enterprise documents, and determines whether additional searches are needed to retrieve relevant information. Developers can enable it on existing Foundry IQ indexes and knowledge bases without requiring additional provisioning or document reindexing, the hyperscaler wrote. Additionally, to simplify deployment of Foundry IQ, Microsoft is adding a capability that will automatically

## Locality-Aware Scheduling for Stream Processing Applications in Serverless Environments

DevFeed: [Locality-Aware Scheduling for Stream Processing Applications in Serverless Environments](<https://devfeed.tech/articles/locality-aware-scheduling-for-stream-processing-applications-in-serverless-environments-142973.md>)

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

Author: Tianyu Qi, Maria A. Rodriguez, Rajkumar Buyya

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

Content type: article

Language: en

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

Topics: [scheduling](<https://devfeed.tech/topics/scheduling.md>), [stream-processing](<https://devfeed.tech/topics/stream-processing.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>)

Tags: [balance](<https://devfeed.tech/tags/balance.md>), [chaining](<https://devfeed.tech/tags/chaining.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [data-pipelines](<https://devfeed.tech/tags/data-pipelines.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [function](<https://devfeed.tech/tags/function.md>), [function-as-a-service](<https://devfeed.tech/tags/function-as-a-service.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [latency](<https://devfeed.tech/tags/latency.md>), [local](<https://devfeed.tech/tags/local.md>), [locality](<https://devfeed.tech/tags/locality.md>), [monitors](<https://devfeed.tech/tags/monitors.md>), [network](<https://devfeed.tech/tags/network.md>), [operator](<https://devfeed.tech/tags/operator.md>), [operators](<https://devfeed.tech/tags/operators.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scheduling](<https://devfeed.tech/tags/scheduling.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [stream-processing](<https://devfeed.tech/tags/stream-processing.md>)

### AI overview

LcSched targets a locality tradeoff in stateful serverless stream pipelines: keeping each operator's state with its execution can force chained invocations to cross workers, raising latency and I/O overhead. The distributed strategy aims to run chained invocations locally while ensuring they access state on the same worker, and monitors runtime workload to balance workers. The abstract reports up to 3.6x higher throughput and up to 79% lower end-to-end latency than the state-of-the-art distributed scheduling strategy for stateful serverless environments.

### Source excerpt

arXiv:2611.23879v1 Announce Type: new Abstract: Stateful Serverless (Function-as-a-Service) environment are increasingly used for stream processing applications. These applications are often structured as pipelines where data flows through a sequence of distinct processing operators. Many operators are stateful and require access to the processing state during execution. To address this, stateful serverless platforms introduce state servers on worker nodes, co-locating state with computation to dramatically reduce access latency. In serverless, these data pipelines are realized by chaining function invocations, passing the processed data from one function to the next. To reduce network overhead, state-of-the-art scheduling approaches employ a distributed worker-level scheduling model, routing locally generated chained requests directly to destination workers, bypassing centralized schedulers. However, these approaches always co-locate state and execution for the same operator in the same worker, which forces most invocations to the next operator to be transferred across workers, thereby increasing both latency and I/O overhead. As a result, this paper proposes LcSched, a novel distributed scheduling strategy tailored for stream processing applications in stateful serverless environments. LcSched seeks to maximise local execution of chained function invocations while ensuring that each execution accesses its state from the local worker. It also monitors workload at runtime to maintain workload balance between workers. Experimental results show that LcSched improves throughput by up to 3.6x and reduces end-to-end latency by up to 79% compared to the state-of-the-art distributed scheduling strategy for stateful serverless environments.

## Full Fine-Tuning (FFT) on SageMaker AI Serverless Model Customization

DevFeed: [Full Fine-Tuning (FFT) on SageMaker AI Serverless Model Customization](<https://devfeed.tech/articles/full-fine-tuning-fft-on-sagemaker-ai-serverless-model-customization-141875.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/full-fine-tuning-fft-on-sagemaker-ai-serverless-model-customization/>)

Author: Sandeep Raveesh-Babu

Published: 2026-11-19T00:15:58Z

Content type: article

Language: en

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

Topics: [Fine-tuning](<https://devfeed.tech/topics/fine-tuning.md>), [lora](<https://devfeed.tech/topics/lora.md>), [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [LLM evaluation / benchmarking](<https://devfeed.tech/topics/llm-evaluation-benchmarking.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [peft](<https://devfeed.tech/topics/peft.md>), [Hyperparameter optimization](<https://devfeed.tech/topics/hyperparameter-optimization.md>), [post-training](<https://devfeed.tech/topics/post-training.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-sagemaker](<https://devfeed.tech/tags/amazon-sagemaker.md>), [amazon-sagemaker-ai](<https://devfeed.tech/tags/amazon-sagemaker-ai.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [customization](<https://devfeed.tech/tags/customization.md>), [fft](<https://devfeed.tech/tags/fft.md>), [fine](<https://devfeed.tech/tags/fine.md>), [fine-tuning](<https://devfeed.tech/tags/fine-tuning.md>), [full](<https://devfeed.tech/tags/full.md>), [gap](<https://devfeed.tech/tags/gap.md>), [guidelines](<https://devfeed.tech/tags/guidelines.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [key](<https://devfeed.tech/tags/key.md>), [lora](<https://devfeed.tech/tags/lora.md>), [matrices](<https://devfeed.tech/tags/matrices.md>), [model](<https://devfeed.tech/tags/model.md>), [post](<https://devfeed.tech/tags/post.md>), [practical](<https://devfeed.tech/tags/practical.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

The excerpt reports that Full Fine-Tuning (FFT) can outperform LoRA on complex code-generation tasks with large datasets, while results depend heavily on hyperparameters and FFT can cause catastrophic forgetting. In experiments, Qwen3-4B was fine-tuned on 110,000 Magicoder coding pairs using SageMaker AI Serverless Model Customization. At 100K+ examples, FFT reached 90% LLM-as-Judge correctness; a baseline with 5% warmup, batch size 8, and learning rate 2e-5 best preserved MMLU knowledge. Three epochs yielded the reported correctness peak, while training beyond that degraded tested variants. Aggressive FFT learning rates of 5e-5 or higher sharply reduced MATH and MMLU scores. LoRA slightly exceeded FFT on one LLM-as-Judge comparison (81.5% versus 79.5%), and both methods fell below the base model on MATH exact match. The service handles compute allocation and checkpoints; switching between FFT and LoRA requires changing the training type. These findings reflect the reported coding experiments and do not establish FFT as universally superior.

### Source excerpt

Amazon SageMaker AI Serverless Model Customization now supports Full Fine-Tuning (FFT). This post explores when FFT outperforms LoRA across key benchmarks, examines the spectral properties of model weight matrices behind the quality gap, shares practical hyperparameter tuning guidelines, and shows how to get started.

## Microsoft adds HorizonDB to Fabric to ease development of agent-driven applications

DevFeed: [Microsoft adds HorizonDB to Fabric to ease development of agent-driven applications](<https://devfeed.tech/articles/microsoft-adds-horizondb-to-fabric-to-ease-development-of-agent-driven-applications-140731.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4250181/microsoft-adds-horizondb-to-fabric-to-ease-development-of-agent-driven-applications.html>)

Author: Anirban Ghoshal

Published: 2026-11-18T12:43:42Z

Content type: news

Language: en

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

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-data-management-databases](<https://devfeed.tech/tags/artificial-intelligence-data-management-databases.md>), [azure](<https://devfeed.tech/tags/azure.md>), [backend](<https://devfeed.tech/tags/backend.md>), [build](<https://devfeed.tech/tags/build.md>), [business](<https://devfeed.tech/tags/business.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [compute](<https://devfeed.tech/tags/compute.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [data](<https://devfeed.tech/tags/data.md>), [data-and-analytics](<https://devfeed.tech/tags/data-and-analytics.md>), [data-integration](<https://devfeed.tech/tags/data-integration.md>), [data-management](<https://devfeed.tech/tags/data-management.md>), [data-warehouse](<https://devfeed.tech/tags/data-warehouse.md>), [databases](<https://devfeed.tech/tags/databases.md>), [development](<https://devfeed.tech/tags/development.md>), [fabric](<https://devfeed.tech/tags/fabric.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>)

### AI overview

Fabric HorizonDB is a public-preview, serverless PostgreSQL option in Microsoft Fabric for smaller or intermittent workloads: it provisions and scales databases on demand, pauses eligible compute after five idle minutes, and resumes it when needed. Applications can query live transactional data and analytical data in OneLake through PostgreSQL; supported analytical query portions run on Fabric Data Warehouse distributed CPU and GPU compute, while transactions remain in the PostgreSQL engine. Analysts say this may reduce backend and data-pipeline work for agent-driven applications, but note potential resume latency, scaling lag, and less predictable performance, making it a weaker fit for systems requiring consistent response times. OneLake's analytical copy has a slight delay, so queries may not provide strict real-time consistency. Fabric-specific dependencies may limit portability, and CIOs may need cost visibility across compute, storage, and analytics.

### Source excerpt

Microsoft is adding a serverless flavor of HorizonDB to its data and analytics platform, Fabric, to make it easier for developers, business teams and AI agents to build intermittently used applications for automating business workflows and supporting agent-driven tasks. The hyperscaler first unveiled HorizonDB for Azure at its Ignite conference in November 2025, positioning it as a PostgreSQL-compatible database for demanding enterprise workloads, including mission-critical applications that require high performance and scalability. Its architecture, according to Microsoft, combines shared storage with elastic, scale-out compute to support the performance and scalability that large databases and transaction-heavy workloads require. The new flavor, named Fabric HorizonDB, which was launched in public preview at this year's ongoing Ignite conference, by contrast, targets smaller workloads that do not require continuously running database infrastructure. It provides a managed backend that automatically provisions and scales databases based on demand, pausing them when idle and resuming them when needed, the hyperscaler wrote in a blog post. It also lets applications query live transactional data alongside analytical data in OneLake through a single PostgreSQL interface, reducing the infrastructure and data integration work involved in building applications, it added. In order to support translytical queries, Fabric HorizonDB uses Fabric Data Warehouse's distributed compute to execute supported analytical portions of PostgreSQL queries across CPU- and GPU-powered resources, while retaining transactional processing in its PostgreSQL engine, it further wrote. New database could reduce engineering effort Analysts, too, see Fabric HorizonDB's serverless and translytical capabilities helping developers simplify the development of agent-driven applications. "Agent-driven applications often need to spin up databases on demand to support specific tasks and workflows. Fabric Hor

## Celebrating Microsoft Ignite with Azure region expansion in Toronto

DevFeed: [Celebrating Microsoft Ignite with Azure region expansion in Toronto](<https://devfeed.tech/articles/celebrating-microsoft-ignite-with-azure-region-expansion-in-toronto-140974.md>)

Original publisher: [Read original article](<https://www.elastic.co/blog/elastic-cloud-serverless-now-available-azure-toronto>)

Author: Lucy Wang,Brian Bergholm

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

Content type: release

Language: en

Sources: [Elastic Blog](<https://devfeed.tech/sources/elastic-blog-elasticsearch-kibana-and-elk-stack.md>)

Topics: [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>), [Azure](<https://devfeed.tech/topics/azure.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-builder](<https://devfeed.tech/tags/agent-builder.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-apps](<https://devfeed.tech/tags/ai-apps.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [availability](<https://devfeed.tech/tags/availability.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-elasticsearch](<https://devfeed.tech/tags/cloud-elasticsearch.md>), [cloud-regions-microsoft-azure](<https://devfeed.tech/tags/cloud-regions-microsoft-azure.md>), [customers](<https://devfeed.tech/tags/customers.md>), [data](<https://devfeed.tech/tags/data.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [elastic-cloud](<https://devfeed.tech/tags/elastic-cloud.md>), [elastic-cloud-serverless](<https://devfeed.tech/tags/elastic-cloud-serverless.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-ignite](<https://devfeed.tech/tags/microsoft-ignite.md>), [region](<https://devfeed.tech/tags/region.md>), [regions](<https://devfeed.tech/tags/regions.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [toronto](<https://devfeed.tech/tags/toronto.md>)

### AI overview

Elastic Cloud Serverless became available in Azure's Toronto (canadacentral) region on November 18, 2026, bringing Azure coverage to 13 regions and total coverage across hyperscalers to 35. Elastic says its stateless design stores data in Azure Blob Storage, separates indexing from search so those workloads can scale independently, and dynamically adjusts resources as demand changes. Elastic manages sizing, upgrades, backups, and shard balancing; billing is based on ingestion, search, and retention. The service also offers cross-project search and configurable audit-log delivery. To start, users can create a project through Microsoft Marketplace or the Elastic Cloud console, choose a serverless project type, select Azure and a region, then create the project. Marketplace signup supports a seven-day trial or existing credits, with subscription charges appearing in Azure consolidated billing.

### Source excerpt

Elastic announces the availability of Elastic Cloud Serverless in the Microsoft Azure region of Toronto, bringing serverless Azure regions to 13 worldwide. Elastic meets customers where their data is -- all around the globe.

## ESP RainMaker Neo: An Extensible IoT Cloud

DevFeed: [ESP RainMaker Neo: An Extensible IoT Cloud](<https://devfeed.tech/articles/esp-rainmaker-neo-an-extensible-iot-cloud-140733.md>)

Original publisher: [Read original article](<https://developer.espressif.com/blog/2026/11/own-your-iot-cloud-esp-rainmaker-neo/>)

Author: John Lee

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

Content type: article

Language: en

Sources: [Blog on Developer Portal](<https://devfeed.tech/sources/blog-on-developer-portal.md>)

Topics: [Esp Rainmaker](<https://devfeed.tech/topics/esp-rainmaker.md>), [Internet of things](<https://devfeed.tech/topics/iot.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [ESP-IDF](<https://devfeed.tech/topics/esp-idf.md>), [ESP Insights](<https://devfeed.tech/topics/esp-insights.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [admin](<https://devfeed.tech/tags/admin.md>), [admin-dashboard](<https://devfeed.tech/tags/admin-dashboard.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [ai-assistants](<https://devfeed.tech/tags/ai-assistants.md>), [alexa](<https://devfeed.tech/tags/alexa.md>), [amazon-alexa](<https://devfeed.tech/tags/amazon-alexa.md>), [apache](<https://devfeed.tech/tags/apache.md>), [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [blog](<https://devfeed.tech/tags/blog.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [complete](<https://devfeed.tech/tags/complete.md>), [costs](<https://devfeed.tech/tags/costs.md>), [day-one](<https://devfeed.tech/tags/day-one.md>), [esp](<https://devfeed.tech/tags/esp.md>), [esp-rainmaker](<https://devfeed.tech/tags/esp-rainmaker.md>), [iot](<https://devfeed.tech/tags/iot.md>), [neo](<https://devfeed.tech/tags/neo.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [rainmaker](<https://devfeed.tech/tags/rainmaker.md>)

### AI overview

ESP RainMaker Neo is an open-source, serverless IoT stack deployed in the customer's own AWS account, covering firmware, cloud backend, phone apps, admin dashboard and voice integrations. Its day-one features include BLE onboarding, local and remote control, device-run schedules, automations, device sharing, data history, notifications and OTA management. The article presents it as an alternative to SaaS platforms that constrain customization and building a cloud stack from scratch, which requires implementing identity, device lifecycle, OTA and other services. Costs are pay-as-you-go for AWS messages, requests and storage, with no per-node license or core platform fee; actual cost depends on fleet usage. It cites tooling, simulators, unit and live-deployment integration tests, design specs and security practices as support for safe customization, including AI-assisted changes. Users can first try a public deployment, then deploy their own cloud with the Installer in about an hour. Enterprise support and identity features are paid add-ons.

### Source excerpt

A complete IoT cloud. In your own AWS account. Open-source, Serverless and Extensible. Find out what you get on day one, what it costs, why it beats building one with AI from scratch, and where to start, with or without an AI assistant.

## What's new in Azure Cosmos DB at Microsoft Ignite 2026

DevFeed: [What's new in Azure Cosmos DB at Microsoft Ignite 2026](<https://devfeed.tech/articles/what-s-new-in-azure-cosmos-db-at-microsoft-ignite-2026-139452.md>)

Original publisher: [Read original article](<https://devblogs.microsoft.com/cosmosdb/whats-new-azure-cosmos-db-ignite-2026/>)

Author: Kirill Gavrylyuk

Published: 2026-11-17T18:33:17Z

Content type: release

Language: en

Sources: [Azure Cosmos DB Blog](<https://devfeed.tech/sources/azure-cosmos-db-blog.md>)

Topics: [Azure](<https://devfeed.tech/topics/azure.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-assisted-development](<https://devfeed.tech/tags/ai-assisted-development.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [application-development](<https://devfeed.tech/tags/application-development.md>), [azure](<https://devfeed.tech/tags/azure.md>), [azure-cosmos-db](<https://devfeed.tech/tags/azure-cosmos-db.md>), [azure-cosmos-db-for-nosql](<https://devfeed.tech/tags/azure-cosmos-db-for-nosql.md>), [data-protection](<https://devfeed.tech/tags/data-protection.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [ignite](<https://devfeed.tech/tags/ignite.md>), [microsoft-ignite](<https://devfeed.tech/tags/microsoft-ignite.md>), [microsoft-ignite-2026](<https://devfeed.tech/tags/microsoft-ignite-2026.md>), [relevance](<https://devfeed.tech/tags/relevance.md>), [search](<https://devfeed.tech/tags/search.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

The Ignite 2026 announcements add developer tools, agent retrieval features, and production controls to Azure Cosmos DB. In public preview, an AI-assisted data modeler recommends partition strategies and can generate Bicep, Terraform, or SDK configurations; the managed MCP server lets agents discover schemas, retrieve documents, and use full-text, vector, or hybrid search with Azure identity and role-based access controls. The Cosmos DB Shell is generally available for querying, managing, importing, and exporting data across terminal, VS Code, and portal, with MCP support. The Rust SDK is generally available and includes retries, partition-level failover, circuit breaking, and binary encoding. For retrieval, automatic embedding generation is in preview; semantic reranking and BM25 score projection are generally available. Production announcements include immutable, isolated Azure Backup vault copies and throughput buckets that limit each workload's RU/s use within a shared container. Azure RBAC integration is planned for public preview in mid-December 2026 and can coexist with native data-plane roles. The excerpt also cites OpenAI's reported efficiency gains after rearchitecting a

### Source excerpt

At Microsoft Ignite 2026, we're introducing new Azure Cosmos DB capabilities that help developers accelerate application development, build intelligent AI-powered experiences, and run production workloads with greater confidence. From AI-assisted development and agent tooling to improved search relevance, and enhanced data protection, these updates make it easier to build and evolve applications with Azure Cosmos [...] The post What's new in Azure Cosmos DB at Microsoft Ignite 2026 appeared first on Azure Cosmos DB Blog.

## RuralShield: Super Intelligence-Assisted Security Triage and Serverless Infrastructure for Resource-Constrained Healthcare

DevFeed: [RuralShield: Super Intelligence-Assisted Security Triage and Serverless Infrastructure for Resource-Constrained Healthcare](<https://devfeed.tech/articles/ruralshield-super-intelligence-assisted-security-triage-and-serverless-infrastructure-for-resource-constrained-healthcare-136039.md>)

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

Author: Mohammad Arman Ullah, Asif Ahmed

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

Content type: article

Language: en

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

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [assessment](<https://devfeed.tech/tags/assessment.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [healthcare](<https://devfeed.tech/tags/healthcare.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [language-model](<https://devfeed.tech/tags/language-model.md>), [resource](<https://devfeed.tech/tags/resource.md>), [security](<https://devfeed.tech/tags/security.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

RuralShield separates workload access, model-assessment validation, and action authorization, using deterministic routing and human approval to turn security recommendations into permitted containment actions. In the reported synthetic evaluation, a frozen 120-hour workload recorded 999,861 authenticated requests and 999,860 successful responses; eight successful model requests covered desktop and AWS cohorts. Together with five scripted controls, the AWS cohort completed nine workflows, including two human-approved Lambda containment cases with verified restoration of the original concurrency setting. The study reports inspectable records and checksum-verified archives under these evaluated conditions.

### Source excerpt

arXiv:2611.17887v1 Announce Type: new Abstract: Resource-constrained healthcare providers must connect cloud security controls to an operational response process. Introducing language-model assessments adds an authorization problem: a recommendation must be converted into a permitted action against a specific resource. RuralShield combines a configurable serverless application foundation with structured model assessment, deterministic routing, and human-approved containment. Its design separates workload access, assessment validation, and action authorization so that each boundary produces inspectable records. We evaluate the implementation through a frozen 120-hour non-AI workload and separate desktop and AWS AI cohorts. The workload recorded 999,861 authenticated requests and 999,860 successful responses, with one HTTP 404 and one missing minute representing 139 scheduled requests. Median, 95th-percentile, and 99th-percentile Ohio client latencies were 28.57, 53.01, and 110.77 ms. Eight successful model requests exercised assessment and reporting in two four-case cohorts. The AWS cohort and five scripted controls produced nine completed workflows, including two human-approved Lambda containment cases with verified restoration of the original concurrency setting. Source-linked, checksum-verified archives preserved the records before scoped cleanup. The study demonstrates an inspectable integration of application controls and human-mediated AI response under the evaluated synthetic conditions.

## Databricks is a Leader and positioned highest in execution in the 2026 Gartner® Magic Quadrant™ for Data Lakehouse Platforms

DevFeed: [Databricks is a Leader and positioned highest in execution in the 2026 Gartner® Magic Quadrant™ for Data Lakehouse Platforms](<https://devfeed.tech/articles/databricks-is-a-leader-and-positioned-highest-in-execution-in-the-2026-gartner-magic-quadranttm-for-data-lakehouse-platforms-136417.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/databricks-leader-and-positioned-highest-execution-2026-gartnerr-magic-quadranttm-data>)

Author: Kaitlin Baumgardner; Kevin Balaji; Brianna Helm; Jonathan Keller; Susan Pierce

Published: 2026-11-14T18:15:02Z

Content type: article

Language: en

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

Topics: [databricks](<https://devfeed.tech/topics/databricks.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [deltalake](<https://devfeed.tech/topics/deltalake.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [DataOps](<https://devfeed.tech/topics/dataops.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [BigQuery](<https://devfeed.tech/topics/bigquery.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [acid](<https://devfeed.tech/tags/acid.md>), [affiliates](<https://devfeed.tech/tags/affiliates.md>), [ai](<https://devfeed.tech/tags/ai.md>), [company](<https://devfeed.tech/tags/company.md>), [data](<https://devfeed.tech/tags/data.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [decades](<https://devfeed.tech/tags/decades.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [execution](<https://devfeed.tech/tags/execution.md>), [gartner](<https://devfeed.tech/tags/gartner.md>), [gartner-magic-quadranttm](<https://devfeed.tech/tags/gartner-magic-quadranttm.md>), [lakebase](<https://devfeed.tech/tags/lakebase.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>), [lakehouse-architecture](<https://devfeed.tech/tags/lakehouse-architecture.md>), [leader](<https://devfeed.tech/tags/leader.md>), [ltap](<https://devfeed.tech/tags/ltap.md>), [magic](<https://devfeed.tech/tags/magic.md>), [operational](<https://devfeed.tech/tags/operational.md>), [platforms](<https://devfeed.tech/tags/platforms.md>)

### AI overview

Databricks argues that AI workloads need operational and analytical data on one governed foundation. Its Lake Transactional/Analytical Processing (LTAP) architecture pairs Lakebase Postgres for ACID transactions with lakehouse engines for analytics, both reading one durable copy in open formats such as Delta Lake and Apache Iceberg under Unity Catalog. The company says this avoids pipelines and mirrored tables while giving analytics fresh application data without slowing transactions. Lakebase Postgres uses separated, serverless compute and storage on cloud object storage, scales compute to zero, and supports instant database branching. Databricks cites PRADA Group's reported KPI delivery at about 130 times faster and infrastructure costs about 50% lower. It also says Gartner named Databricks a Leader with the highest execution scores in its 2026 Data Lakehouse Platforms Magic Quadrant and the only Visionary in its Cloud Operational Database Management Systems Magic Quadrant. These are vendor-reported claims; the text includes Gartner's disclaimer that its research is not an endorsement.

### Source excerpt

AI is pulling analytical and operational data togetherFor decades, enterprises have...

## Beyond AI Applications: How openEuler Is Rethinking the Agentic Infra OS

DevFeed: [Beyond AI Applications: How openEuler Is Rethinking the Agentic Infra OS](<https://devfeed.tech/articles/beyond-ai-applications-how-openeuler-is-rethinking-the-agentic-infra-os-131797.md>)

Original publisher: [Read original article](<https://feed.itsfoss.com/link/24361/17523787/openeuler-agentic-infra-os>)

Author: Edmar Pereira

Published: 2026-11-13T10:30:23Z

Content type: article

Language: en

Sources: [It's FOSS](<https://devfeed.tech/sources/it-s-foss.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [NUMA](<https://devfeed.tech/topics/numa.md>), [vllm](<https://devfeed.tech/topics/vllm.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-infrastructure](<https://devfeed.tech/tags/agentic-infrastructure.md>), [agentic-os](<https://devfeed.tech/tags/agentic-os.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [caching](<https://devfeed.tech/tags/caching.md>), [data](<https://devfeed.tech/tags/data.md>), [data-services](<https://devfeed.tech/tags/data-services.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [infra](<https://devfeed.tech/tags/infra.md>), [memory](<https://devfeed.tech/tags/memory.md>), [news](<https://devfeed.tech/tags/news.md>), [os](<https://devfeed.tech/tags/os.md>), [persistent-memory](<https://devfeed.tech/tags/persistent-memory.md>)

### AI overview

openEuler's agentic infrastructure extends OS support beyond hardware and process management to the agent lifecycle, using an Agent Kernel and an Agent Service with reusable services across heterogeneous processors and accelerators. Five areas address distinct needs: StratoVirt and Conch support isolated, recoverable sandboxes; distributed KV caching reuses inference context; memory services retrieve persistent knowledge; openGauss serverless databases provide elastic, branchable data environments; and an open ecosystem connects frameworks, orchestration, and hardware. The source reports sandbox startup as low as 20 ms, more than 2,000 sandboxes, and 100,000 launched within 10 seconds in a separate test. It also reports targeted-scenario gains: 1.5x-3x inference throughput, 30%-70% lower time to first token, 30%-70% lower token costs, and 1.5x-3x higher task success. These are presented as openEuler performance results and targeted outcomes, not universal guarantees.

### Source excerpt

From secure execution and intelligent caching to persistent memory and elastic data services, openEuler is building an infrastructure foundation for large-scale, production-ready AI agents.

## The Hidden Cost of Adding a CDN to Google Cloud Run

DevFeed: [The Hidden Cost of Adding a CDN to Google Cloud Run](<https://devfeed.tech/articles/the-hidden-cost-of-adding-a-cdn-to-google-cloud-run-131621.md>)

Original publisher: [Read original article](<https://hackernoon.com/the-hidden-cost-of-adding-a-cdn-to-google-cloud-run?source=rss>)

Author: Nandan Kumar

Published: 2026-11-13T07:25:15Z

Content type: article

Language: en

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

Topics: [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>), [Cloud Run](<https://devfeed.tech/topics/cloud-run.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [backend-development](<https://devfeed.tech/tags/backend-development.md>), [bill](<https://devfeed.tech/tags/bill.md>), [billing](<https://devfeed.tech/tags/billing.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [cloud-costs](<https://devfeed.tech/tags/cloud-costs.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [cloud-run](<https://devfeed.tech/tags/cloud-run.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [estimator](<https://devfeed.tech/tags/estimator.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [google-cloud-pricing](<https://devfeed.tech/tags/google-cloud-pricing.md>), [google-cloud-run](<https://devfeed.tech/tags/google-cloud-run.md>), [latency](<https://devfeed.tech/tags/latency.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [performance](<https://devfeed.tech/tags/performance.md>), [website](<https://devfeed.tech/tags/website.md>)

### AI overview

Adding Google Cloud CDN to a low-traffic site on request-billed Cloud Run raised the reported monthly bill from about $2 to an estimated $30. The CDN setup requires an external HTTP(S) load balancer, whose fixed monthly cost applies regardless of request volume; the author says this fixed charge drove the jump. For this site, the CDN addressed only modest latency, so the author would have weighed that benefit against the cost before deploying. The resulting open-source Cloud Cost Estimator compares configurations across Google Cloud, AWS and Azure, but uses static prices from public sources rather than live APIs, so estimates may drift and are only general guidance.

### Source excerpt

Adding Google Cloud CDN increased a website's cloud bill by 15x. Here's why it happened and how it inspired an open-source cost estimator.

## Fast Serverless LLM Cold Starts by Sharing and Prewarming Startup Work

DevFeed: [Fast Serverless LLM Cold Starts by Sharing and Prewarming Startup Work](<https://devfeed.tech/articles/fast-serverless-llm-cold-starts-by-sharing-and-prewarming-startup-work-131542.md>)

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

Author: Hongjin Kim, Igjae Kim, Kwanghoon Choi, Minho Ha, Jaehyuk Huh

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

Content type: article

Language: en

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

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [vllm](<https://devfeed.tech/topics/vllm.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [cairn](<https://devfeed.tech/tags/cairn.md>), [checkpoint](<https://devfeed.tech/tags/checkpoint.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [cold-start](<https://devfeed.tech/tags/cold-start.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cxl](<https://devfeed.tech/tags/cxl.md>), [demand](<https://devfeed.tech/tags/demand.md>), [engine](<https://devfeed.tech/tags/engine.md>), [fast](<https://devfeed.tech/tags/fast.md>), [first](<https://devfeed.tech/tags/first.md>), [llm](<https://devfeed.tech/tags/llm.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [sharing](<https://devfeed.tech/tags/sharing.md>), [startup](<https://devfeed.tech/tags/startup.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

Cairn cuts serverless LLM cold starts by sharing startup artifacts and prewarming reusable setup. The first server to start a model publishes its weights and engine artifacts to a cluster-shared CXL memory pool, which other servers read in place; model-independent setup runs ahead of time in warm containers that are replenished with a template process. In tests with ServerlessLLM on vLLM v0.20, six models (1B-14B) and two servers using an emulated CXL pool, cold starts on servers without their own checkpoint were 4.1-5.2x faster, and median time to first token on a request stream fell 64%. The abstract notes that weight loading accounts for only 5-11% of roughly minute-long cold starts; compilation, memory profiling and runtime setup make up most of the rest.

### Source excerpt

arXiv:2611.16180v1 Announce Type: new Abstract: When a serverless LLM platform launches a model worker on demand, the cold start lasts roughly a minute, yet only 5-11% of it is spent loading weights. Most of the remainder goes to compilation, memory profiling and runtime setup, which each server performs again even though the outcome is identical across servers or independent of the model. We present Cairn. The server that is first to start a model publishes the weights and engine artifacts to a CXL memory pool shared across the cluster, and the remaining servers read them in place. Model-independent setup is completed ahead of time inside warm containers, and a template process replaces each container as soon as it is used. With ServerlessLLM on vLLM v0.20, six models from 1B to 14B, and two servers that share an emulated CXL pool, Cairn speeds up cold starts by 4.1-5.2x on servers without a checkpoint of their own and reduces median TTFT on a request stream by 64%.

## Build a serverless recipe-sharing API with Go and Amazon Aurora DSQL

DevFeed: [Build a serverless recipe-sharing API with Go and Amazon Aurora DSQL](<https://devfeed.tech/articles/build-a-serverless-recipe-sharing-api-with-go-and-amazon-aurora-dsql-131173.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/build-a-serverless-recipe-sharing-api-with-go-and-amazon-aurora-dsql/>)

Author: Steve Brown

Published: 2026-11-12T16:14:20Z

Content type: tutorial

Language: en

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

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>)

Tags: [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cloudformation](<https://devfeed.tech/tags/cloudformation.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [go](<https://devfeed.tech/tags/go.md>), [iam](<https://devfeed.tech/tags/iam.md>), [integrity](<https://devfeed.tech/tags/integrity.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [keys](<https://devfeed.tech/tags/keys.md>), [optimistic-concurrency](<https://devfeed.tech/tags/optimistic-concurrency.md>), [recipe](<https://devfeed.tech/tags/recipe.md>), [referential-integrity](<https://devfeed.tech/tags/referential-integrity.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [retries](<https://devfeed.tech/tags/retries.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [token](<https://devfeed.tech/tags/token.md>), [uuid](<https://devfeed.tech/tags/uuid.md>)

### AI overview

The article demonstrates a Go recipe-sharing REST API that runs locally as a Gin HTTP server or on AWS Lambda behind API Gateway, using the same handlers and an Amazon Aurora DSQL store. It describes UUID text primary keys to spread writes across storage partitions; short-lived IAM tokens, TLS, and a pgx connection pool managed by the Go connector; and separate DDL operations because DDL and DML cannot share a transaction. The sample checks chef and recipe references in handlers, though the database can enforce them with foreign keys instead. Aurora DSQL optimistic concurrency conflicts can be retried by the connector's occretry package with exponential backoff, so transaction logic should be idempotent. Deployment uses a script and CloudFormation for Lambda, API Gateway, IAM, and logs; its IP allowlist is not authentication, and the article recommends adding an authorization method for production. The text also notes connection recycling before the 60-minute server limit and low pool sizing for single-request Lambda invocations.

### Source excerpt

Build a fully serverless recipe-sharing REST API in Go on Amazon Aurora DSQL, AWS Lambda, and Amazon API Gateway. Learn UUID primary keys for even write distribution, short-lived IAM token authentication, application-layer referential integrity, and automatic optimistic-concurrency retries, with a one-command CloudFormation deployment.

## Migrate from Amazon EC2 to Amazon ElastiCache Serverless with zero downtime

DevFeed: [Migrate from Amazon EC2 to Amazon ElastiCache Serverless with zero downtime](<https://devfeed.tech/articles/migrate-from-amazon-ec2-to-amazon-elasticache-serverless-with-zero-downtime-129586.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/migrate-from-amazon-ec2-to-amazon-elasticache-serverless-with-zero-downtime/>)

Author: Rong Zhang

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

Content type: tutorial

Language: en

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

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [downtime](<https://devfeed.tech/topics/downtime.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>)

Tags: [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-command-line-interface-aws-cli](<https://devfeed.tech/tags/aws-command-line-interface-aws-cli.md>), [aws-govcloud-us](<https://devfeed.tech/tags/aws-govcloud-us.md>), [console](<https://devfeed.tech/tags/console.md>), [downtime](<https://devfeed.tech/tags/downtime.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [managed](<https://devfeed.tech/tags/managed.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [migration](<https://devfeed.tech/tags/migration.md>), [online](<https://devfeed.tech/tags/online.md>), [oss](<https://devfeed.tech/tags/oss.md>), [redis](<https://devfeed.tech/tags/redis.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Amazon ElastiCache's online migration lets workloads on self-managed Valkey or Redis OSS on EC2 move to ElastiCache Serverless for Valkey while clients keep using one endpoint. ElastiCache validates the source, provisions migration infrastructure, performs a full data sync followed by replication of writes, then routes the endpoint to the serverless cache at a fully synced window. Cutover can be manual, allowing validation first, or automatic; all shards switch together, and traffic continues through the same endpoint. At launch, serverless migrations require cluster-mode sources running Valkey 7.2-8.1 or Redis OSS 4.0-7.2, and target Valkey 7.2, 8.1, or 9.0 at least as new as the source. Prerequisites include an empty reachable target, TLS-capable clients, and source credentials and CA certificates where applicable. The migration is free for 180 days from the account's first preparation; afterward migration nodes are billed per node-hour, while the serverless cache is charged separately. The source should retain headroom and stable network, credentials, certificates, and shard layout until migration completes.

### Source excerpt

On October 20, 2026, Amazon ElastiCache introduced online migration to ElastiCache Serverless for Valkey from self-managed Valkey and Redis OSS on Amazon EC2 with zero downtime. This post shows what's supported at launch, how online migration works, and how to run a migration in the ElastiCache console.

## fRAC: Remote Accelerator Calls on Hostless FPGAs

DevFeed: [fRAC: Remote Accelerator Calls on Hostless FPGAs](<https://devfeed.tech/articles/frac-remote-accelerator-calls-on-hostless-fpgas-127829.md>)

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

Author: Ziyi Yang, Krishnan B. Iyer, Yixi Chen, Ran Shu, Zsolt Istv\\'an, Marco Canini, Suhaib A. Fahmy

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

Content type: article

Language: en

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

Topics: [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>), [rdma](<https://devfeed.tech/topics/rdma.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>)

Tags: [accelerators](<https://devfeed.tech/tags/accelerators.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cs-ar](<https://devfeed.tech/tags/cs-ar.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [dpu](<https://devfeed.tech/tags/dpu.md>), [fpgas](<https://devfeed.tech/tags/fpgas.md>), [functions](<https://devfeed.tech/tags/functions.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [interface](<https://devfeed.tech/tags/interface.md>), [latency](<https://devfeed.tech/tags/latency.md>), [optimized](<https://devfeed.tech/tags/optimized.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [power](<https://devfeed.tech/tags/power.md>), [prototype](<https://devfeed.tech/tags/prototype.md>), [remote](<https://devfeed.tech/tags/remote.md>), [request](<https://devfeed.tech/tags/request.md>), [rpc](<https://devfeed.tech/tags/rpc.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [throughput](<https://devfeed.tech/tags/throughput.md>), [transport](<https://devfeed.tech/tags/transport.md>), [under](<https://devfeed.tech/tags/under.md>)

### AI overview

fRAC moves network-to-accelerator invocation into FPGA hardware: it handles transport ingestion, request reassembly, dispatch, and accelerator launch without host software. The prototype is a lightweight shim on an FPGA hosting multiple virtualized accelerators, which can be reconfigured in a few milliseconds. The authors report under 7.8 μs end-to-end latency and up to 90 Gbps application throughput. Against optimized DPDK-based CPU and DPU baselines, fRAC reports at least 80% lower latency under saturation and 85% less power. The abstract identifies serverless functions using fine-grained accelerators as a suitable use case because host invocation overhead can match or exceed their execution time.

### Source excerpt

arXiv:2504.04404v3 Announce Type: replace Abstract: Hardware accelerators are essential for meeting microsecond-scale demands in distributed applications, but invoking them over the network remains bottlenecked by host software. Host-mediated paths (RPC, RDMA) still rely on the CPU to reassemble requests and launch accelerators, which dominates end-to-end latency, while packet-level offload on SmartNICs lacks any notion of a complete request. We introduce the Remote Accelerator Call (RAC) paradigm, in which transport ingestion, request reassembly, dispatch, and accelerator invocation are handled entirely in hardware. We build fRAC, a hostless prototype that implements this network-to-accelerator interface as a lightweight shim on an FPGA hosting multiple virtualized accelerators, reconfigurable at runtime in a few milliseconds. Serverless functions backed by fine-grained accelerators are a natural fit, since host-mediated invocation overhead can match or exceed their short execution times. fRAC achieves under 7.8us end-to-end latency while sustaining application throughput of up to 90 Gbps. Compared to highly optimized DPDK-based CPU and DPU baselines, it achieves at least 80% lower latency under saturation, while consuming 85% less power.

## 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.

## Cloudflare Makes Basin Serverless Analytics Generally Available

DevFeed: [Cloudflare Makes Basin Serverless Analytics Generally Available](<https://devfeed.tech/articles/cloudflare-makes-basin-serverless-analytics-generally-available-127296.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/cloudflare-basin-analytics/>)

Author: Renato Losio

Published: 2026-11-10T19:14:00Z

Content type: release

Language: en

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

Topics: [Cloudflare](<https://devfeed.tech/topics/cloudflare.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>), [analytics stack](<https://devfeed.tech/topics/analytics-stack.md>), [Apache Spark](<https://devfeed.tech/topics/spark.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [BigQuery](<https://devfeed.tech/topics/bigquery.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [apache-spark](<https://devfeed.tech/tags/apache-spark.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [availability](<https://devfeed.tech/tags/availability.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cloudflare-basin-analytics](<https://devfeed.tech/tags/cloudflare-basin-analytics.md>), [data-analytics](<https://devfeed.tech/tags/data-analytics.md>), [data-portability](<https://devfeed.tech/tags/data-portability.md>), [duckdb](<https://devfeed.tech/tags/duckdb.md>), [egress](<https://devfeed.tech/tags/egress.md>), [fees](<https://devfeed.tech/tags/fees.md>), [formats](<https://devfeed.tech/tags/formats.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [iceberg](<https://devfeed.tech/tags/iceberg.md>), [managed](<https://devfeed.tech/tags/managed.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [news](<https://devfeed.tech/tags/news.md>), [object-storage](<https://devfeed.tech/tags/object-storage.md>), [open-data](<https://devfeed.tech/tags/open-data.md>), [platform](<https://devfeed.tech/tags/platform.md>), [r2](<https://devfeed.tech/tags/r2.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [serverless-analytics](<https://devfeed.tech/tags/serverless-analytics.md>), [service](<https://devfeed.tech/tags/service.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [sql](<https://devfeed.tech/tags/sql.md>)

### AI overview

Cloudflare's Basin combines serverless data ingestion, Iceberg table management, and distributed SQL queries on R2, aiming to give smaller teams analytics without managing infrastructure. Basin Pipelines accepts events from Workers, HTTP endpoints, and Logpush, applies SQL transformations, and writes to Iceberg tables or R2; Basin Catalog manages Iceberg metadata and table maintenance; Basin SQL queries Iceberg tables. The platform supports Iceberg-compatible tools including PyIceberg, DuckDB, Snowflake, and Apache Spark, with free egress intended to enable portability across tools, regions, and clouds. Cloudflare says Basin is not a replacement for every warehouse workload; a data analyst describes it as an option for teams whose data is too large for spreadsheets but does not justify dedicated infrastructure. Since preview, Cloudflare reports higher ingestion capacity, expanded SQL capabilities, improved maintenance, Logpush integration, and Terraform support. Real-time processing, newer Iceberg specification support, adaptive maintenance, and more sovereignty and access controls are planned without committed release dates.

### Source excerpt

Cloudflare has announced the general availability of Basin, a serverless analytics platform built on Apache Iceberg and R2 Object Storage. The managed service supports open data formats and integrates with tools such as DuckDB, Snowflake, and Apache Spark, with no data egress fees. By Renato Losio

## AWS Serverless Infrastructure from WebAssembly Components

DevFeed: [AWS Serverless Infrastructure from WebAssembly Components](<https://devfeed.tech/articles/aws-serverless-infrastructure-from-webassembly-components-126722.md>)

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

Author: Philipp Vollmer

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

Content type: article

Language: en

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

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [Wasm components](<https://devfeed.tech/topics/wasm-components.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [component](<https://devfeed.tech/tags/component.md>), [components](<https://devfeed.tech/tags/components.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [iam](<https://devfeed.tech/tags/iam.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [least-privilege](<https://devfeed.tech/tags/least-privilege.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [s3](<https://devfeed.tech/tags/s3.md>), [sandboxing](<https://devfeed.tech/tags/sandboxing.md>), [security](<https://devfeed.tech/tags/security.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

The approach uses a WebAssembly component's WIT interface to keep AWS Lambda infrastructure and permissions aligned. One WIT interpreter generates S3 bucket infrastructure definitions and least-privilege IAM permissions; a generic runtime runs the component as a Lambda function and exposes buckets as capabilities. The authors state consistency properties for bucket existence and Lambda permissions and provide evidence that their interpreters satisfy them. In the limited Lambda-to-S3 example, they show selected deployment failures prevented by the approach that occur in a baseline setup. Combined with WebAssembly runtime sandboxing, this provides capability-based security for AWS infrastructure access.

### Source excerpt

arXiv:2611.11293v1 Announce Type: cross Abstract: The infrastructure definitions and the code for serverless applications are often only loosely connected. This yields a large error class: the referenced infrastructure components might not exist. It is also hard to keep the application and its permissions in sync. To address this problem we present an infrastructure from code solution where we provision cloud infrastructure from Wasm Interface Type (WIT) - the language defining the interface of WebAssembly components. We limit ourselves to the basic example of an AWS Lambda function accessing S3 buckets. We build two interpreters for the WIT language: one that derives the definition of S3 buckets as infrastructure as code and least-privilege IAM permissions, and a generic runtime that runs the component as a Lambda function and provides access to the S3 buckets as capabilities. We formulate consistency properties that ensure the existence of the S3 buckets and correct permissions of the Lambda, and provide evidence that our interpreters satisfy them. We show how selected failures for deployment of such cloud components can be prevented using our technique and how a baseline setup fails at this task. Together with the strict sandboxing of the WebAssembly runtime we achieve an instance of capability-based security for access to AWS infrastructure as a further result.

## How to get started with Qwen3.8-Flash-Next on Runpod Serverless

DevFeed: [How to get started with Qwen3.8-Flash-Next on Runpod Serverless](<https://devfeed.tech/articles/how-to-get-started-with-qwen3-8-flash-next-on-runpod-serverless-124880.md>)

Original publisher: [Read original article](<https://www.runpod.io/blog/getting-started-with-qwen3-8-flash-next-on-runpod-serverless>)

Author: Chris Vela

Published: 2026-11-09T23:35:25Z

Content type: tutorial

Language: en

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

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [vllm](<https://devfeed.tech/topics/vllm.md>), [quantization](<https://devfeed.tech/topics/quantization.md>), [CUDA Graphs](<https://devfeed.tech/topics/cuda-graphs.md>), [huggingface\_hub](<https://devfeed.tech/topics/huggingface-hub.md>)

Tags: [deploy](<https://devfeed.tech/tags/deploy.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [qwen3-8-flash-next](<https://devfeed.tech/tags/qwen3-8-flash-next.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [vllm](<https://devfeed.tech/tags/vllm.md>)

### AI overview

The Runpod Hub vLLM worker template described in the excerpt uses vLLM 0.28.0, below Qwen3.8-Flash-Next's stated 0.29 minimum, so the validated deployment uses vLLM's `vllm/vllm-openai:qwen38-flash-next` image. The authors ran the FP8 model on 4x H200 with tensor parallelism and expert parallelism; Hopper requires `--enable-expert-parallel --moe-backend triton`. Set `NCCL_NVLS_ENABLE=0` to avoid NVLS initialization failures. `--enforce-eager` shortens startup by skipping compilation and CUDA graph capture, but makes early requests much slower and steady-state decode slower than the compiled setup. The reported warm-host startup was about 11 minutes; a fully cold model download may take 20-25 minutes. The excerpt recommends load-balancing Serverless for bursty API traffic and pods for interactive work or latency-sensitive use. It reports successful checks for OpenAI-compatible requests, streaming, tool calling, instruct mode, and vision.

### Source excerpt

Deploy Qwen3.8-Flash-Next on Runpod with vLLM's dedicated image. Validated flags, 4x H200 hardware math, measured cold starts, and the NCCL fix you need on day one.

## Roboflow Serverless vs. Self-Hosted Inference: What a 90-Second Traffic Spike Does to One GPU Server

DevFeed: [Roboflow Serverless vs. Self-Hosted Inference: What a 90-Second Traffic Spike Does to One GPU Server](<https://devfeed.tech/articles/roboflow-serverless-vs-self-hosted-inference-what-a-90-second-traffic-spike-does-to-one-gpu-server-124832.md>)

Original publisher: [Read original article](<https://roboflow.com/blog/roboflow-serverless-vs-self-hosted-inference-what-a-90-second-traffic-spike-does-to-one-gpu-server>)

Author: Sachin Agarwal

Published: 2026-11-09T18:16:06Z

Content type: comparison

Language: en

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

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [benchmarking](<https://devfeed.tech/tags/benchmarking.md>), [cameras](<https://devfeed.tech/tags/cameras.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [computer-vision](<https://devfeed.tech/tags/computer-vision.md>), [container](<https://devfeed.tech/tags/container.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [demand](<https://devfeed.tech/tags/demand.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [detection](<https://devfeed.tech/tags/detection.md>), [failure](<https://devfeed.tech/tags/failure.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [gpus](<https://devfeed.tech/tags/gpus.md>), [inference](<https://devfeed.tech/tags/inference.md>), [load](<https://devfeed.tech/tags/load.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [serverless-inference](<https://devfeed.tech/tags/serverless-inference.md>), [test](<https://devfeed.tech/tags/test.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

In a three-minute test of vehicle counting on 1280x1280 aerial frames, a single NVIDIA L40S self-hosted server handled 5 requests per second at about one-second median latency. At 20 requests per second for 90 seconds, its throughput leveled off around 13-15 requests per second; latency reached the 20-second timeout, and responses stopped even after traffic returned to baseline. Roboflow Serverless handled the same traffic, returning 2,273 successful requests at a 1.4-second median, versus 1,095 for self-hosting; reported failures were 0% rounded versus 50%. Each request triggered 16 tiled model inferences. The author interprets the self-hosted latency ramp as backlog growth, while noting the queue was not measured directly. The article says self-hosting can address bursts by provisioning peak capacity, with GPUs idle between bursts, or autoscaling; in this setup, bringing up a GPU server took about five minutes, longer than the burst. Roboflow Serverless is described as using the same open-source inference server, with per-model queues, warm spare capacity, and scaling on total backlog.

### Source excerpt

Sizing GPUs for the traffic you expect works until traffic does something you didn't expect. In our load test, a short burst left one GPU server timing out even after traffic returned to normal, while Roboflow Serverless kept up. Here's what went wrong, and why autoscaling can't add a GPU in time.

## Scaling an autonomous agent from one team to fifty: A serverless-to-container decision framework

DevFeed: [Scaling an autonomous agent from one team to fifty: A serverless-to-container decision framework](<https://devfeed.tech/articles/scaling-an-autonomous-agent-from-one-team-to-fifty-a-serverless-to-container-decision-framework-122596.md>)

Original publisher: [Read original article](<https://thenewstack.io/scaling-autonomous-agents-framework/>)

Author: Rashmi Erande

Published: 2026-11-08T16:30:00Z

Content type: comparison

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [container native](<https://devfeed.tech/topics/container-native.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-delegation](<https://devfeed.tech/tags/agent-delegation.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-workloads](<https://devfeed.tech/tags/agentic-workloads.md>), [agents](<https://devfeed.tech/tags/agents.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [aws-marketplace](<https://devfeed.tech/tags/aws-marketplace.md>), [bug](<https://devfeed.tech/tags/bug.md>), [complex](<https://devfeed.tech/tags/complex.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [failure](<https://devfeed.tech/tags/failure.md>), [framework](<https://devfeed.tech/tags/framework.md>), [post-contributed](<https://devfeed.tech/tags/post-contributed.md>), [qa](<https://devfeed.tech/tags/qa.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [sponsor-aws-marketplace](<https://devfeed.tech/tags/sponsor-aws-marketplace.md>), [sponsored-post-contributed](<https://devfeed.tech/tags/sponsored-post-contributed.md>), [stack](<https://devfeed.tech/tags/stack.md>), [team](<https://devfeed.tech/tags/team.md>), [teams](<https://devfeed.tech/tags/teams.md>), [test](<https://devfeed.tech/tags/test.md>), [ticket](<https://devfeed.tech/tags/ticket.md>)

### AI overview

A Lambda based QA agent polls test results every 15 minutes, checks for duplicates and regressions, and files JIRA bugs; the author says it costs under $5 monthly for one team and saves 8-10 hours a week. The proposed decision rule is workload characteristics, not a team-count threshold: Lambda suits isolated, short event-driven jobs, while Durable Functions can handle longer workflows. For persistent shared services, cross-team analysis, centralized API rate limiting, GPU inference, and namespace isolation needed together, the author favors EKS Auto Mode. The proposed platform separates shared services, tenant namespaces, and shared ML inference, using quotas, network policies, and scoped IAM roles. Lambda remains the suggested starting point; the article estimates 50 teams on EKS Auto Mode at $200-250 monthly, but presents this as an architecture and cost projection.

### Source excerpt

QA teams shipping complex products generate test failures around the clock. Every failure needs a bug ticket with steps, screenshots, The post Scaling an autonomous agent from one team to fifty: A serverless-to-container decision framework appeared first on The New Stack.

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