惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
aimingoo的专栏
aimingoo的专栏
Martin Fowler
Martin Fowler
C
Check Point Blog
G
Google Developers Blog
V
Visual Studio Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Google DeepMind News
Google DeepMind News
人人都是产品经理
人人都是产品经理
有赞技术团队
有赞技术团队
MongoDB | Blog
MongoDB | Blog
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
大猫的无限游戏
大猫的无限游戏
D
Docker
Hugging Face - Blog
Hugging Face - Blog
The GitHub Blog
The GitHub Blog
博客园 - 三生石上(FineUI控件)
A
About on SuperTechFans
Recent Announcements
Recent Announcements
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
阮一峰的网络日志
阮一峰的网络日志
Stack Overflow Blog
Stack Overflow Blog
Vercel News
Vercel News

The New Stack | DevOps, Open Source, and Cloud Native News

Agentic development hinges on verification. For cloud-native software, that is a runtime problem. AI agents need infrastructure: Why Europe’s regional cloud strategy matters Transform your AI coding agent into a deterministic Java Spring expert WeAreDevelopers is coming to the US to give unsung developers a bigger voice Cleaner AI training data, fewer bugs: Sonar’s SonarSweep explained Observability overload is drowning engineers Google’s DiffusionGemma is 4x faster than its other Gemma models Fable 5: Guardrails and burn rate are annoying users, who say it’s still better than Opus 4.8 The Anthropic leader who built Claude Code says he ditched prompting — now he just writes loops. AWS can now mathematically prove your VMs are isolated Microsoft pulled 73 GitHub repos after malware attack — but still won’t say who’s compromised Databricks wants to kill the “email me a file” problem for AI agent skills Ramp bets forward deployed engineers can do what off-the-shelf finance AI can’t Git real: AI agents aren’t just for solo developers anymore Anthropic launches Claude Mythos/Fable 5, but you better try it soon Spring is 23 years old. AI just made it a security emergency. This AI agent startup ditched Anthropic for DeepSeek — and says it’s saving millions When your data model is the bottleneck: lessons from Medium’s feature store How long before we stop reading the code? The tokenmaxxing party is over, and Revenium is mopping up How AI is solving the memory crunch it created Microsoft’s pitch to enterprises: Ditch Azure Repos for GitHub, despite its rocky reliability record Claude Code’s biggest upgrade yet ran 5 agents at once — here’s what happened Why Anthropic just doubled Claude Cowork limits at no charge For years, Apache Cassandra handed this work to your team — 6.0 takes it back “A dangerous combination”: The 2 factors that can “corrupt” AI agent workflows With Foundry, Microsoft bets the enterprise AI battle is about reliability, not capability Microsoft unlocks Visual Studio for developers left behind by its own AI AI teams now deploy 1,000 times a month. Your pipeline wasn’t built for that. Microsoft just made the agent runtime free — and kept everything around it
Why AWS scrapped OpenSearch’s architecture to chase agent...
Frederic Lardinois · 2026-05-29 · via The New Stack | DevOps, Open Source, and Cloud Native News

AWS on Thursday launched what it calls a near-total rebuild of its managed search and vector engine, in an effort to better meet demands of the agentic age.

This next generation of Amazon OpenSearch Serverless scales to zero when idle and aims to cut costs by up to 60 percent compared with provisioned clusters running at peak capacity.

The usage patterns of AI agents, which tend to come in bursts with long idle stretches, essentially broke the assumptions of the original serverless architecture AWS originally used for OpenSearch Serverless.

“About 97 percent of it has been built from the ground up by the engineers on the managed service.”

Tia White, who became general manager for OpenSearch at AWS in February, tells The New Stack, “The vast majority of it is a massive rebuild. About 97 percent of it has been built from the ground up by the engineers on the managed service. And then there are pieces that are already available via the open source repo, but anything that’s truly novel or true IP, we don’t make available via that open source project.”

The “Swiss Army Knife” problem

The biggest architectural change is the separation of storage and compute, White explains, with OpenSearch sitting on a new proprietary storage layer. “Collections can truly shrink all the way to zero, meaning you’re not paying for anything if your resources are not active,” White explains. “And then they can spin back up in a matter of seconds to handle the needs of agents because of the bursty workload. We don’t want a cold-start problem.”

She also notes that the service auto-scales 20 times faster than the previous generation and also now supports search and vector collection types at launch. All of this is priced per OpenSearch Compute Unit for indexing, search, and GPU acceleration. Native integrations with Vercel and AWS’s own Kiro IDE are also part of the launch, along with a set of OpenSearch Agent Skills that let developers work with their preferred tools, including Claude Code and Cursor.

The 60 percent cost savings compared to running at peak capacity come from two places, White says: the new proprietary storage layer with its compression feature, and the auto-scaler being aggressive enough to drop capacity in seconds when traffic falls off.

“Since we’re able to predict what you need and we’re able to deliver and scale back down in a very rapid fashion, you’re going to automatically save money,” White says.

White is also candid about why OpenSearch needed to make these changes. “Predominantly, OpenSearch has been the Swiss Army knife, a hodgepodge of everything,” she says. “We even tried to do a pivot into SIEM [Security Information and Event Management] last year.” That detour did not stick. The new framing pairs the traditional search OpenSearch is known for with log analytics, but shaped around agent workloads.

Coming soon: agent memory, log analytics, and a reasoning model for search workloads

That two-pillar refocus comes with a roadmap White previewed a bit in the interview.

A long-term memory feature for agents is slated for the second half of 2026, with built-in evaluation and governance from day one. As White describes the design problem: “Evaluation, which you could argue is a governance aspect, is an art and a science. The evaluation approach to what is good, what should be stored, what should be purged — that constant feedback loop.”

“Building an agentic-first platform for our customers, those are things that we understand we have to provide at day one. It can’t be an afterthought or an add-on.”

She says those guardrails cannot be retrofitted. “Building an agentic-first platform for our customers, those are things that we understand we have to provide at day one. It can’t be an afterthought or an add-on.” The company is also focusing on building out OpenSearch Serverless’ features around knowledge graphs and semantic layers, alongside what White describes as “an advanced reasoning model for search-specific workloads.”

A major log analytics launch is coming in June, White says. That will put AWS back into a market currently dominated by Datadog, Splunk, and Grafana. A TIMESERIES collection type will follow at AWS’s New York Summit, extending OpenSearch Serverless to more observability workloads.

“Eventually, when the precision is there, and the token optimization is there, and all of these things, you beg the question of can LLMs replace something like OpenSearch,” White asks. But to AWS, the answer here is that OpenSearch Serverless (and OpenSearch in general) will become a vital semantic layer for the LLM to call — not something replaced by the LLM.

YOUTUBE.COM/THENEWSTACK

Tech moves fast, don't miss an episode. Subscribe to our YouTube channel to stream all our podcasts, interviews, demos, and more.

Created with Sketch.