跳到正文
Vercel Blog(vercel.com)· Alex Langenfeld·· 14 天前品質評分55

Vercel Workflow SDK 預設透過 WebSocket 寫入 Workflows

Workflow SDK now writes over WebSockets on Vercel

重點導讀

Vercel Workflow SDK 現在預設透過 WebSocket 將事件與串流寫入 Vercel Workflows,升級至 workflow@5.2.0 或更新版本即可使用。

AI 伴隨問答

自備 Key 深度分析

針對這篇報導有疑問?可直接點選快捷問題或向 AI 追問背景脈絡與技術細節:

正文

The Workflow SDK now sends event writes and stream writes to Vercel Workflows over a WebSocket by default, replacing one HTTP request per write, or per write group for streams. No code change is needed beyond upgrading to workflow@5.2.0 or later.

Once you deploy the upgrade, new runs use it. In-flight runs finish on the deployment they started on.

terminal

npm install workflow@latest

Existing streaming code works as is. A step that writes a burst of chunks, like AI tokens, sends them over the WebSocket once it opens:

stream-chunks.ts

import { getWritable } from "workflow";

async function streamChunks(chunks: string[]) {

"use step";

const writer = getWritable<string>().getWriter();

for (const chunk of chunks) {

await writer.write(chunk);

}

writer.releaseLock();

}

export async function streamingWorkflow(chunks: string[]) {

"use workflow";

await streamChunks(chunks);

}

Copy link to headingStreams keep pace with AI output

In a benchmark replaying an AI agent's token stream, v5.2.0, which writes streams over a WebSocket by default, delivered the full response 4.2× faster than v4.8.12, with no chunk delayed over a second.

Copy link to headingFewer HTTP requests for event writes

Every step start and completion is an event write, now sent over the WebSocket, so workflows with many steps make fewer HTTP requests. The added efficiency also improves performance and reduces costs. The queue handler opens the connection for every delivery.

Copy link to headingGet started

Read the Vercel World documentation to get started. If you're on 4.x, start with the upgrade guide, since v5 is a major release.

來源: Vercel Blog (vercel.com)
開啟原文

讀者討論

理性交流 · 即時討論