IoT & Microservices
summary
Proposes solving IoT platform chaos with Asynchronous MicroServices that publish device state to a RabbitMQ event bus and vote via lightweight, idempotent services rather than REST orchestration. Demonstrates working home setup using Hue lights, Amazon Alexa, Apple TV, Docker on ARM Raspberry Pi for cheap redundancy, JSON messages, polling bridges and choreography for scenes and motion->light rules. Claims rapid iteration and real deployments—about production pushes every 3.5 minutes—with graceful degradation.
AI-written summary · about
chapters (29)
- 0:00AGILE INDIA 2018
- 2:45Amazon Echo
- 3:27Xbox One
- 4:08Phillips Hue Bridge
- 4:54Samsung Refrigerator
- 6:39MicroServices to the Rescue!
- 7:48Asynchronous MicroServices
- 8:31Rapids, Rivers, and Ponds
- 10:01Need Pattern for Asynchronous
- 12:23Incremental Applications
- 13:14Technology Choices
- 14:14Architectural Principles
- 16:44Framework from MicroServices Workshop
- 18:42Architecture: Hardware
- 19:17Add Event Bus
- 20:03Scenes
- 20:50Reactive Services
- 21:20MetaServices: Monitor
- 21:30MetaServices: Detection
- 21:51MetaServices: Correction
- 22:22Maintaining State
- 23:27Choreography - Sticky Colors
- 27:19Observations
- 30:29XP Values at Work
- 33:29Case Study: From 2006
- 35:18Requirements Uncertainty
- 37:07Future: More Devices
- 37:58Future: Security
- 38:51Future: Docker on Raspberry Pi
related talks
03mMicroServices - Let’s Build Some!
53mIoT powered by Microprofile
48mChallenges in Implementing MicroServices
35mMicroservices: From dream to reality in forty five minutes
29mNode.js Micro-Services
50m"Problems you’ll face in the microservice world"
49mMicroservices: An unexpected Journey
34mMicroservices using Node.js and RabbitMQ