跳到主要內容
AI News HubLIVE
更多
來源內容 · 翻譯待補全1 分鐘閱讀

待翻譯:Serverless routing made sticky

文章摘要

AI 服務暫時不可用,以下為來源摘要,待恢復後補全翻譯:Voice agents, multiplayer games, and other workloads can now build on Sticky Sessions. Achieve strong affinity without losing autoscaling. Here’s how we built this on Modal Servers.

待翻譯:Serverless routing made sticky
報告錯誤

更正渠道尚未開通,可先複製下方文章資訊留存。

查看更正說明
直接讀正文

AI 服務暫時不可用,以下為來源正文,待恢復後補全翻譯。

At Modal, our serverless compute powers real-time inference, training, and batch jobs, scaling automatically with demand. Sandboxes offer a different model, containers whose lifecycles you explicitly control. A growing number of workloads require something in-between; autoscaling serverless compute that maintains continuity between requests. Consider a speech-to-text model with decoder state for an audio stream, a voice agent that holds a conversation, or a multiplayer game. For these workloads, users must come back to the same container on every reconnect for the entirety of their session. We recently launched Sticky Sessions, built on top of our low-latency Modal Servers. Every session’s requests land on the same container. To use Sticky Sessions, just create a Modal Server with the @modal.sessioned() decorator and start the sessions with the SDK or the HTTP API: @app.server() @modal.sessioned() class Server: @modal.enter() def start(self): subprocess.Popen(["python", "-m", "http.server", "8000"]) @app.local_entrypoint() def main(): session = Server.sessions.start(idle_timeout=600) headers = {"Modal-Authorization": f"Bearer {session.token}"} print(requests.get(Server.get_url(), headers=headers).text)

展開要點與分析

文章情報

工程師中級

要點

  • AI 服務暫時不可用,系統已先保留來源內容與降級元數據。
  • Voice agents, multiplayer games, and other workloads can now build on Sticky Sessions. Achieve strong affinity without losing autoscaling. Here’s how we built this on Modal Server…

技術影響

可能影響 Agent 架構、工具調用、工作流自動化和產品集成。

要點與分析由自動化流程生成,可能有誤,請結合原始來源核實。