Wiring a Microservices Application Architecture to Respond to Events
summary
OpenWhisk is a serverless event-action platform that wires triggers → rules → actions so small teams run microservices in NodeJS, Swift or Docker without managing infra. It demos creating actions, triggers and rules via the CLI, binding GitHub webhooks to post to Slack, and chaining Cloudant upload→autosharpen→noise‑reduction→Watson tagging for an image pipeline that recognizes “Eiffel Tower.” Claims include deploy actions in milliseconds and pay only for code when it runs with automatic parallel scaling and no vendor lock‑in (Bluemix or open source).
AI-written summary · about
chapters (8)
- 0:00Start
- 1:12Agenda
- 2:22OpenWhisk in a nutshell
- 4:48Meet Dave & his team
- 14:45OpenWhisk: How does it work?
- 17:33OpenWhisk Comparison to traditional models
- 21:27Programming model
- 26:18Live demo
related talks
38mHow to Build a Distributed Serverless Polyglot Micro Services IoT Platform
44mMicroservices Without Servers
41mOpenWhisk as an Apache Mesos Framework
50mChoreography vs Orchestration in serverless microservices
51mChoreography vs Orchestration in serverless microservices
32mChoreography vs Orchestration in serverless microservices
29mNode.js Micro-Services
37mBuild next-gen applications with event-driven architectures