Lightning Talk: A Reusable Zbus Based Architecture, Abstracting Core Application Components
summary
Claims a reusable Zephyr app architecture that actually runs: a link layer built on zbus event and command channels, five-ish modules per product (~5 independent services) that communicate with thin if-this-then-that glue. Uses Zephyr threads, zbus listeners to execute in publisher context and message/normal subscribers to defer work; this improves testability and reuse across devices. Practical caveats: unioned struct definitions for channels, large payloads force copies or risky pointer-sharing and manual lifetime management.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:05Reusable architecture motivation
- 2:29Command and event channels
- 5:40Zbus introduction
- 7:07Zbus for inter-thread communication
- 9:37Architecture benefits and REST analogy
- 11:00Reusable services advantages
- 11:44Channel challenges
- 13:20Q&A
related talks
15mA Reusable Zbus Based Architecture, Abstracting Core Application...
01h 31mTutorial: Zbus - the Lightweight & Flexible Zephyr Message Bus
30mCombining Zephyr & C++20 to Build Safe, Low-footprint, Event-based Applicati...
38mMicroservices for Microcontrollers: Composable Software Architecture for Embedded...
16mKeynote: The Rise of Frameworks in Zephyr: From Devices to Subsystems to Frameworks
38mMicroservices for Microcontrollers: Composable Software Architecture for Embedded De...
41mFuture of Zephyr Device Model
53mField Report: Setting up a Software Product Line (SPL) Architecture based on Zephyr