Implementation Chapter 3

niniBUS Engineering Journal – Chapter 2 | Bounded Queue, Lane Credit & Design Walkthrough This isn't a tutorial on implementing a message queue. This is an engineering journal documenting the evolution of **niniBUS**—a lightweight C++ message bus I'm building from scratch. The goal is to explore design decisions, understand trade-offs, and gradually evolve the architecture rather than jump directly to the "perfect" solution. In this chapter we move from the mental model to the actual implementation and discuss why the architecture looks the way it does. In this video Building the mental model before reading code Why *code is the source of truth* while architecture is the source of inspiration Bus → Lane → FIFO architecture Designing a bounded circular FIFO Why I implemented a custom FIFO instead of using `std::queue` Runtime lane creation and configurable capacity Lane Credit and backpressure (inspired by flow control concepts) Walking through the complete V1.0.0 implementation Looking ahead to the next challenge: Broadcast Delivery vs Competing Consumers This series is intentionally recorded as an engineering journey. You'll see the architecture evolve, mistakes get corrected, trade-offs discussed, and ideas refined over time instead of only presenting the final polished solution. If you're interested in: C++ Embedded Systems System Design Operating Systems Message Bus Architecture Software Architecture Engineering Thought Process I hope you'll enjoy following along. GitHub Repository: https://github.com/debadarshana1990/n... If you have suggestions, alternative designs, or see trade-offs I haven't considered, I'd love to hear your thoughts in the comments. #cpp #embedded #systemdesign #softwarearchitecture #operatingsystems #cplusplus #engineering #messagequeue #opensource #niniBUS