The Serverless Revolution
summary
HTTP endpoint accepts a color query, uses a color library to validate and convert it, and publishes RGB values to an Adafruit IO MQTT feed where a Raspberry Pi subscribes and updates a badge; code runs on Azure Functions with npm modules supported and deploys via the serverless framework (occasional deploy failures). Billing is per execution, cold starts for Node are ~1–2s, and observability/metrics can lag up to five minutes, so trade-offs are concrete.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:42Obligatory Introduction
- 5:03What the abstraction is
- 15:36Serverless vill not solve all of your problems
- 16:37How long is a cold start?
- 18:01Summary of when Serverless should work for you
related talks
26mThe Wide World of Serverless
23mMonitoring serverless applications
51mServerless – are you ready for the revolution?
45mHop on the serverless adventure with NodeJS
20mThe Serverless First Mindset
01h 00mServerless Trends of the Season
01h 08mUsing AWS Lambda and Azure Functions to develop serverless applications
28mHop on the serverless adventure with NodeJS
