Building a Serverless, EventSourced Slack clone
summary
Builds a Slack-like chat using Terraform to provision AWS: static front end on S3, API Gateway -> Lambda for commands, Cognito for auth, DynamoDB as the event store, projections written as JSON views back to S3, and SNS/SQS to decouple projections and plugins. Notes: DynamoDB prohibits empty strings, Kinesis holds data only 7‑day retention, and local limits force using Dynamo with two and a half writes/sec capacity in the demo. Observed latency differences 200 ms vs 800 ms (and 15 s cold start) between Node and C# Lambdas; design favours eventual consistency and simple, upgradeable architecture.
AI-written summary · about
chapters (15)
- 0:00Start
- 3:55Set Up a Resource in Aws with Terraform
- 5:53Ui
- 8:39Policy for the S3 Bucket
- 9:00Architecture
- 13:47Projections
- 21:11Event Storage
- 28:14Setup for an Api Gateway in Aws
- 36:38Kognito
- 37:03Summary of How To Use It for Javascript
- 40:01Sign Up
- 43:24Parallel Updates to S3
- 45:51Irc Plugin
- 50:39Cost
- 55:10Latency Cluster
related talks
44mBuilding a serverless event driven Slack Bot
29mHow to build a social network on serverless
53mLook Ma! No servers!
04mSlackbot Development Serverless Framework
39m/Automate. Serverless and event-driven approach to DevOps
43mBuilding an AWS Serverless Application with Terraform
30mThinking Serverless: From User Request to Serverless Solution
50mBuild, Deploy, Debug and Tune Serverless Microservices
