Design a Fault-Tolerant Meeting Bot Allocation System
Otter.AiSoftware Engineer · Onsite
Last updated
Design the infrastructure between a web UI and a bot pool. Connect requirements and APIs to data modeling, consistency, scaling, failure recovery, observability, and the important design trade-offs.
Design a Fault-Tolerant Meeting Bot Allocation System
Design the infrastructure between a web UI and a bot pool. A user submits a meeting URL and optional credentials; the service returns acceptance asynchronously, atomically assigns an idle bot, and streams states through joined, failed, disconnected, or ended. Plan for 100,000 concurrent meetings and one million meetings daily.
Constraints & Assumptions
- An acknowledged request cannot be silently lost.
- Messages may be duplicated and bots may fail mid-session.
Clarifying Questions to Ask
- Are credentials stored or passed through?
- How quickly must state reach the browser?
Follow-up questions
- How do you prevent double assignment?
- How do platform-specific adapters fit?
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.