Shiba - Serverless Slack ChatOps
summary
Malwarebytes replaces a legacy bot with a serverless Slack integration called Shiba that uses API Gateway → Lambda → DynamoDB, SQS for queuing and Jenkins for deploys, handling about 1800 deployments per month; development takes a single engineer ~20 hours to prototype and Shiba cuts hosting cost to roughly 98% cost savings versus the prior EC2/ECS setup. It addresses Slack’s 3‑second timeout with SQS/callbacks, mitigates cold starts with a warm‑lambda strategy, and exposes simple Python modules for extensions.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:31About me
- 0:54Agenda
- 1:27What is Serverless
- 5:36Cons
- 10:46Shiba Architecture
- 13:45Shiba Cost
- 15:15Extendability
- 17:29Maintaining Shiba
- 21:26Moving Forward
related talks
04mSlackbot Development Serverless Framework
39m/Automate. Serverless and event-driven approach to DevOps
56mBuilding a Serverless, EventSourced Slack clone
32mEmbracing Serverless Ops
44mBuilding a serverless event driven Slack Bot
50mBuild, Deploy, Debug and Tune Serverless Microservices
45mDr. Strangelove or How I Learned to Stop Worrying and Love the Serverless Chatbots
14mAutomate intelligent cloud operations with Slack and AWS
