本文にスキップ
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.

ソースModal Blog
翻訳待ち: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…

要点と分析は自動生成され、誤りを含む場合があります。原典をご確認ください。