OpenWhisk as an Apache Mesos Framework
summary
OpenWhisk runs actions in Docker but now operates its invoker as a Mesos framework by embedding a Mesos actor that talks to the Mesos scheduler HTTP API, letting Mesos launch and manage containers instead of direct Docker CLI calls. Demo shows Alexa → Adobe Analytics returning 1,658 page views and 11,000,799 visitors, and OpenWhisk keeps a pre-warmed pool of containers; Akka clustering handles leader election and failover, while reconcile and task-state sharing are still work in progress.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:10Open Whisk on Mesos
- 0:40USER EXPERIENCES -A DRIVING FACTOR
- 3:20COST AND OPS OPTIMIZATIONS
- 3:58PRODUCT EXTENSIBILITY
- 5:14MODERN APPS HAVE A RICHER UX. ARE SMALLER. COMPOSABLE. AND REAL-TIME.
- 7:45INSIDE APACHE OPENWHISK
- 8:52OPENWHISK CONCEPTS
- 10:11OPENWHISK SCALING
- 11:02WE'RE A MESOS SHOP
- 15:18A SHORT DEMO
related talks
55mApache OpenWhisk: How it Works and How You Can Benefit
56mApache OpenWhisk
34mApache OpenWhisk: Building a Production-Ready Serverless Stack on/for Kubernetes
27mCloud Native, Event Drive, Serverless, Microservices Framework - OpenWhisk
15mServerless Apps with Node.JS in OpenWhisk and Adobe I/O Runtime
30mPython with Apache OpenWhisk
44mA Tour of the New Apache OpenWhisk Incubator Project and Its Numerous Repositories
37mBuilding Serverless Applications (...)
