Serverless Microservices
summary
Proposes replacing servers with AWS API Gateway + Lambda to run Clojure/ClojureScript service functions, with a single-page Reagent app hosted on S3, Cognito for authentication, and DynamoDB for storage; demonstrates scraping EC2/Lambda pricing via a Lambda proxy and signup/login flows that write to DynamoDB. Notes Lambda is billed by 100ms slices, has a 60s max execution, JVM cold starts push prefer Node/ClojureScript, and deployment uses Swagger import plus clj-s-lambda; it works for low-to-moderate traffic but tooling and docs remain flaky.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:21aerostat
- 5:59compose apps out of distributed components accessed via connections
- 10:38what ben's dad might call MEGABUCKS
- 13:03services are functions not applications not servers just functions
- 15:42API Gateway Lambda DynamoDB Cognito
- 17:38easy persistence for data with light relational needs . works seamlessly • pricing is complicated
- 19:05$+ Storage and Network Costs
- 19:55Examples? Examples
- 46:37new landscape new approaches
related talks
54mServerless Architectures: no servers allowed!
28mServerless - the way microservices should be
40mThe serverless startup
54mYou should be building Serverless Microservices
54mContainerless in the cloud with AWS Lambda
04mServerless applications, Microservices, AWS
31mA quick intro to AWS Serverless
02h 37mServerless Deep Dive
