Overwatch: A serverless approach to orchestrating your...
summary
A serverless orchestration platform written in Go uses a GitHub App to ingest org‑wide events into a Go orchestrator that decides whether to invoke isolated Lambda scanners; it handles 22,000 events/day with about 15% trigger lambdas, currently six integrations, and writes unified reports to S3. Alerts surface via GitHub Advanced Security and Slack with consistent triage buttons, lambdas deploy fleet‑wide from one YAML, Terraform modules and Lambda versions/aliases enable staged rollouts, and pipelines stay unblocked by default.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:46Shift Left
- 1:38Practical Implementation
- 3:04Triaging
- 3:35Combining two ideas
- 3:52Product Manager hats
- 5:04GitHub Events
- 8:06Lambdas
- 9:59Unified Alerts
- 10:52Security Alerts
- 11:22Source of Truth
- 11:49Lambda
- 12:30Lambdas job
- 13:14Testing
- 13:50Versions
- 16:23chime
- 18:09Lego blocks
- 18:49Surprise
- 19:28Key takeaways
- 20:45Wrap up
related talks
58mWho Goes There? - building a serverless Github auditor
39m/Automate. Serverless and event-driven approach to DevOps
17mHow do we use Serverless Architectures on AWS Lambda
51mChoreography vs Orchestration in serverless microservices
38mChoreography vs Orchestration in serverless microservices
29mGoing Serverless
42mEnterprise Serverless Adoption. An Experience Report
39mServerless in production, an experience report