Fun With Serverless Javascript

on YouTube ↗28m

" summary

Argues serverless shifts ops to pay-per-run functions and gives concrete tooling and cost details: billing in gigabyte-seconds and many free invocations, typical runs use well under 1 GB and under a second. Shows deployment commands and CLIs for AWS Lambda and IBM Cloud Functions/OpenWhisk, recommends the Serverless Framework for multi-provider deploys. Demonstrates a working Amazon Echo skill (project codename) that generates names, saves them to Redis using the Node Redis client and bluebird, and successfully responds on voice.

AI-written summary · about

" chapters (11)

1. 0:00Start
2. 11:24Amazon Lambda
3. 12:45Hello World Lambda
4. 13:58Hello World OpenWhisk
5. 14:57IBM Cloud Functions Get the wsk CLI tool or the bx tool with wsk plugin, then log in
6. 16:23Bluemix OpenWhisk Run your action from the CLI
7. 20:09Alexa: Amazon Echo
8. 22:37Example: Project Codename Existing npm library
9. 23:37Project Codename: Code
10. 24:47Project Codename: Run wsk action invoke --blocking alexa/project-cadenane
11. 25:58Redis Integration As an example, storing the new project codename in Redis

" related talks

• 01h 00mServerless - reality or BS - notes from the trenchesLynn Langit · NDC Oslo 2017
• 28mServerless - the way microservices should beIvan Jovanovic · OdessaJS 2018
• 02h 37mServerless Deep DiveBert Ertman · Devoxx Belgium 2017
• 42mNo Server Is Better Than No Server: Building Blocks for Serverless ArchitecturesConstantin Gonzalez · code.talks 2017
• 20mWhy Serverless Architecture is Changing Software DevelopmentDavid Wells · Reactathon 2018
• 56m8 1/2 things about serverless (with Node.js)Slobodan Stojanović · HolyJS 2017 Piter
• 54mServerless beyond FunctionsDanilo Poccia · Voxxed Days Bucharest 2018
• 47mAdvanced Serverless Architectural Patterns on AWSAlex Casalboni · Heapcon 2019