Echobot: Migrating a Teams Calling Bot from VMSS to a lower-cost, modern architecture?
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- azure, docker, kubernetes
- 领域
- audio-video-rtc, cloud, devops
调研方向
首先审查 issue 中描述的 EchoBot 方法和现有的 VMSS-based architecture，然后将其与 Azure AKS/ACI Windows container guidance 以及 Service-Hosted Media capabilities 进行比较。完成标准是形成一份有文档记录且适合生产环境的迁移建议，涵盖持续原始音频、扩展、维护和成本。
由索引模型根据 Issue 内容生成。
描述
Hi everyone,
Some time ago, I implemented a Microsoft Teams bot that joins meetings and captures real-time raw audio streams from the participants' microphones. I used the architecture from the official microsoft-graph-comms-samples (EchoBot approach) as my reference.
The system has been running in production for a while and works perfectly, but the infrastructure is becoming incredibly expensive and hard to maintain. As you know, this approach relies heavily on Azure Virtual Machine Scale Sets (VMSS) and full Windows Server environments running 24/7 just to handle the native media platform binaries.
I’m looking to modernize this stack and drastically cut down our Azure bill. I wanted to ask if anyone has successfully migrated away from VMSS for this specific production use case:
Windows Containers (AKS/ACI): Has anyone successfully moved an Application-Hosted Media Bot into Windows-based Docker containers using Azure Kubernetes Service (AKS) or Azure Container Instances (ACI)? Does it actually help reduce costs and scale better than VMSS?
Serverless / Service-Hosted: Is there any trick to get continuous raw audio streaming using Service-Hosted Media (serverless), or are we still strictly limited to just playing prompts and recording files?
Alternative architectures: If you have optimized a real-time Teams media streaming bot for production, what architecture or hosting strategy did you use to keep costs under control?
Could you please point me in the right direction regarding which specific tools or services I should use for this migration? Any links to official documentation, articles, or reference architectures would be highly appreciated.
Thanks!
- 主要语言
- 没有语言数据
- 星标
- 252
- 派生
- 276
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoftgraph/microsoft-graph-comms-samples 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 5/5 一周以上 新手友好度 25/100
microsoftgraph/microsoft-graph-comms-samples#871 · 5 条评论 ·
-
难度 4/5 3-5 天 新手友好度 30/100
microsoftgraph/microsoft-graph-comms-samples#870 · 11 条评论 ·
-
难度 4/5 3-5 天 新手友好度 45/100
microsoftgraph/microsoft-graph-comms-samples#868 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
查看 microsoftgraph/microsoft-graph-comms-samples 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
tone-3000/tone3000-plugin#257 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
moonshine-ai/moonshine#231 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
omacom/omarchy#16102 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
Thorium-Sim/thorium-nova#791 ·
-
bug
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复