Systems | Development | Analytics | API | Testing

You can now execute DDL and DML operations through the Managed Data Lake Service.

Platform teams want to maximize the value of data in motion, but separate workstreams for stream processing, monitoring, KRaft migrations, and data governance create friction as environments grow. As a result, teams spend more time managing operational overhead and less time building. Today, we’re excited to announce Confluent Platform (CP) 8.3.0, built on Apache Kafka 4.3.0, reinforcing our core capabilities as a data streaming platform.

Steering lets a client redirect an agent while the agent is still working, so a follow-up message reshapes the answer in flight instead of cancelling the Run and starting over, or waiting for it to finish. In the AI Transport SDK, a Run encapsulates the agent's output for a single turn (including multiple iterations around an agentic loop). The last release, v0.5.0, made a single agent turn survive a crash by splitting a Run into re-attemptable Steps.

Fivetran’s Db2 portfolio is now complete, bringing modern analytics to all Db2 users.

We have big news for platform and AI infra teams: *Kong AI Gateway 2.0 is available today in private beta*. It runs on its own dedicated runtime, ships on its own release cadence, and carries a completely reimagined user experience designed around the way teams actually build with AI: models, MCP servers, and agents as first-class citizens, not plugins bolted onto an API gateway.

Performance engineering teams are already stretched. AI-accelerated development means more code, more releases, and more pressure on the people responsible for making sure it all holds up. Tricentis NeoLoad 2026.2 is built around a straightforward premise: performance validation must scale to match the pace of delivery, and that means more than just making specialists faster.

AI Transport v0.5.0 is now available. It adds first-class support for running an agent turn inside a durable execution framework, such as Temporal or Vercel's Workflow Development Kit (WDK), while every client watching the conversation still sees one clean, resumable stream. The last release, v0.4.0, let an agent hydrate its history from your own database. This one is about what happens when the process running the agent isn't around for the whole turn.

AI Transport v0.4.0 includes changes to optionally support database hydration. Some applications may wish to store AI conversation history in an external store, such as a database. AI Transport's support for database hydration allows applications to reconcile that stored history with the live activity in the AI session. When using database hydration, your application persists messages for completed runs to the database.