How netflix/dispatch works
Project type and purpose
• Dispatch is a full-stack incident management system.
• Backend: Python service exposing a REST/CLI API, orchestrating data models, scheduled jobs, and integration plugins.
• Frontend: Vue.js single-page application served as static assets.
• Purpose: automate incident workflows, notifications, and post-mortems by integrating with tools (Slack, Jira, PagerDuty, GSuite, etc.).
File structure
• Top level:
– src/dispatch: Flask/Connexion application modules (auth, incidents, cases, workflows, plugins, scheduler, database, etc.).
– src/dispatch/static/dispatch: Vue.js frontend code (components, router, store, assets).
– dispatch/plugins: plugin base interfaces + concrete implementations (Slack, OpsGenie, GitHub, Google, Zoom, etc.).
– src/dispatch/database: Alembic migration scripts, multi-tenant schema.
– bin/run.py & src/dispatch/cli.py: command-line interface.
– docs/: self-hosted documentation powered by Docusaurus.
– docker & .devcontainer: Docker Compose definitions for local development, dev containers.
– tests/: unit, integration, e2e tests for both backend and frontend.
README
• Confirms orchestration role, deep integrations, and that Dispatch “focuses on creating resources, assembling participants, sending notifications, tracking tasks, and post-incident reviews.”
• Mentions Docker and external docs.