Introduction of FaaS (Function as a Service) in starlingX
summary
Integration of FaaS into starlingX builds a working prototype that runs short-lived functions on edge nodes using the platform’s service and lifecycle management, with support for multiple runtimes (including native C), a small RAM/CPU footprint and high-availability restart behavior. Features include event/alert hooks, a controller CLI for deploying functions, and per-execution metering to enable pay-per-use. The implementation targets IoT and mobile backends and demonstrates end-to-end deployment, resource-limited scaling, and live function recovery. serverless on edge minimal RAM footprint per-execution billing CLI controller
AI-written summary · about
chapters (6)
- 0:00Introduction to FaaS
- 3:03Key features of FaaS
- 6:54Benefits for developers
- 10:53Resource efficiency in FaaS
- 14:10Open source and community support
- 16:08Use cases and scalability
related talks
33mFaaS 101
31mGoing FaaSter: Function as a Service at Netflix
23mOpenFaaS: Serverless platform with no strings attached?
12mFaaS Platform Engineering with Wasm
39mFaaS: A Contemporary, Comparative Study
24mThe Future of Functions
23mFaaS with No Strings Attache
34mFaaS and Furious - 0 to Serverless in 60 Seconds, Anywhere