The Future of Functions
summary
Explains why Functions as a Service (FaaS / Serverless) matters: pay-per-execution pricing, short-lived functions (typically seconds to a few minutes), and cold-start delays of a few hundred milliseconds. Covers concrete tools and patterns: API Gateway for HTTP triggers, IBM Cloud Functions (hosted Apache OpenWhisk) with local testing, packages, sequences and Composer/Step Functions for wiring, and CI/CD deployment. Recommends syntax checks and local runs, highlights good fits (APIs, microservices, data transformation/parallel processing) and when to avoid it (hard real‑time, long-running tasks).
AI-written summary · about
chapters (8)
- 0:00The Future of Functions
- 2:09Everything old is new again
- 4:06Run your functions in the cloud
- 7:20Gateway to the
- 10:13Develop your development process
- 13:02Functions are bricks. You are the architect
- 17:39You have a hammer. Now identify a nail
- 22:09Functions a disruptive force
related talks
39mFunction as a Service in the Cloud — Why You'll Still Use It
58mServerless Under the Hood
42mFaaS or not to FaaS: Visible & invisible benefits of the Serverless paradigm
34mServerless Commerce: Higher, Stronger, FaaSter!
30mServerless State of the Union
18mServerless Best Practices
18mServerless (aka FaaS) Computing With Swift
53mServerless is the Abstraction We Deserve