Microservices for Microcontrollers: Composable Software Architecture for Embedded De...
summary
Claim: firmware becomes a set of tiny, loosely coupled modules that are composed at build time and communicate via pubsub so features can be added or removed without touching other code. Implementation uses Zephyr® primitives: zbus, kconfig, and iterable sections, plus event-listener callbacks and thread tasks for hardware. Real example: a cold‑chain asset tracker (GPS temperature cellular) where adding an alarm is a few lines and deleting the display simply drops the module. Notes on performance include copy vs reference subscriptions and observed up to 6,000 messages per second.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:24Microservices for embedded
- 3:06Composability in firmware
- 5:14Tasks and event-driven
- 7:40PubSub paradigm
- 10:48Event tasks and threadless
- 12:34Zephyr RTOS implementation
- 14:00Iterable sections for modularity
- 15:48System init without main thread
- 17:12Cold chain tracker example
- 23:13Q&A
- 30:50Q&A
- 36:13Q&A
related talks
38mMicroservices for Microcontrollers: Composable Software Architecture for Embedded...
15mLightning Talk: A Reusable Zbus Based Architecture, Abstracting Core Application Components- 15mA Reusable Zbus Based Architecture, Abstracting Core Application...
27mInsights on the Re-Architecting to a Single Codebase, Running on Different Hardware...
30mCombining Zephyr & C++20 to Build Safe, Low-footprint, Event-based Applicati...
32mArchitecting an IoT Product Line: Part 1 - Scoping
48mMicroservices? Monoliths? Modules!
43mBeyond micro-services, embrace composable architectures