Drogue Device project. Background A lot of embedded frameworks and RTOSs rely on procedural coding, "copy these source files into your tree" or a lot of manual connection of APIs to the runtime. Since We Are Red Hat (or IBM, or more specifically/historically "JBoss"), we like reusable components. And frameworks. They represent guardrails and provide guidance on how to build larger systems, we feel. Component Systems In enterprise software, component systems abound. There's Enterprise Java Beans, Actix, CDI, Vert.x, Node.js, Akka framework, Quarkus, Spring, etc. Many of these component systems tend to rely on multi-threading capability of the underlying system, and bring about concurrency issues, such as shared-state and locking.