Ichor, Greek Mythos for ethereal fluid that is the blood of the gods/immortals, is a C++ framework/middleware for microservices. Ichor allows re-usable services and components to be used in multiple microservices, greatly supporting the workflow for large teams. It also supports reasoning in multithreaded environments, reducing the chances for data races.
TL;DR: Node.js-style event loops with coroutines and dependency injection, except it's C++.
Ichor borrows from the concept of Fearless Concurrency and offers thread confinement.
Boost supports event loops, dependency injection, networking, can do all of that, and more. Any reason i'd want to use your lib instead?
Excellent question! Please see this page to get a more in-depth answer.
Multithreading is hard. There exist plenty of methods trying to make it easier, ranging from the actor framework, static analysis a la rust, software transaction memory and traditional manual lock-wrangling.
Thread confinement is one such approach. Instead of having to protect resources, Ichor attempts to make it well-defined on which thread an instance of a C++ class runs and pushes you to only access and modify memory from that thread. Thereby removing the need to think about atomics/mutexes, unless you use threads not managed by, or otherwise trying to circumvent, Ichor. In which case, you're on your own.
To support software lifecycles measured in decades, engineers try to encapsulate functionality. Using the Dependency Injection approach allows engineers to insulate updates to parts of the code.
There exist many Dependency Injection libraries for C++ already, but where those usually only provide Dependency Injection, Ichor also provides service lifecycle management and thread confinement. If a dependency goes away at runtime, e.g. a network client, then all the services depending on it will be cleaned up at that moment.
The minimal example requires a main function, which initiates at least one event loop, a framework logger and one service and quitting the program gracefully using ctrl+c.
The realtime example shows a trivial program running with realtime priorities and shows some usage of Ichor priorities.
More examples can be found in the examples directory.
- Linux (including aarch64 and musl-based distros like alpine linux)
- Windows
- Partial support for OSX Monterey (using
brew install llvm, ASAN in combination with boost beast may result in false positives)
- Gcc 11.3 or newer (see this gcc bug for why)
- Clang 14 or newer
- MSVC 17.4+ (though some workarounds for some compiler bugs are used)
- Baremetal, might change if someone puts in the effort to modify Ichor to work with freestanding implementations of C++20
- Far out future plans for any RTOS that supports C++20 such as VxWorks Wind River, FreeRTOS
For build instructions and required dependencies, please see GettingStarted.
Documentation can be found in the docs directory.
- code as configuration, as much as possible bundled in one place
- As much type-safety as possible, prefer compile errors over run-time errors.
- Well-defined and managed multi-threading to prevent data races and similar issues
- Use of an event loop
- Where multi-threading is desired, provide easy to use abstractions to prevent issues
- Performance-oriented design in all-parts of the framework / making it easy to get high performance and low latency
- Fully utilise OOP, RAII and C++20 Concepts to steer users to using the framework correctly
- Implement business logic in the least amount of code possible
- Less error-prone code and better time to market
The framework provides several core features and optional services behind cmake feature flags:
- Coroutine-based event loop
- Event-based message passing
- Dependency Injection
- Service lifecycle management (sort of like OSGi-lite services)
- data race free communication between event loops on multiple threads
Optional services:
- Websocket service through Boost.BEAST
- HTTP/HTTPS client and server services through Boost.BEAST
- Spdlog logging service
- TCP communication service
- JSON serialization services examples
- Timer service
- Redis service
- Etcd v2 service
- EDF scheduling / WCET measurements
- Look into Etcd v3 HTTP API
- Pubsub interfaces
- Kafka? Pulsar? Ecal?
- Shell Commands / REPL
- Tracing interface
- Opentracing? Jaeger?
- "Remote" services, where services are either in a different thread or a different machine
- Code generator to reduce boilerplate
- ...
Feel free to make issues/pull requests, and I'm sometimes online on Discord: https://discord.gg/r9BtesB
Business inquiries can be sent to michael AT volt-software.nl
By default, Ichor uses a mutex when inserting/extracting events from its queue. Because non-voluntary user-space scheduling requires lock-free data-structures, this is not possible.
Ichor used to have full support for the polymorphic allocators, but as not all compilers support it yet (looking at you libc++) as well as having a negative impact on developer ergonomy, it has been removed. Instead, Ichor now recommends usage with mimalloc:
it does not suffer from blowup, has bounded worst-case allocation times (wcat), bounded space overhead (~0.2% meta-data, with low internal fragmentation), and has no internal points of contention using only atomic operations.
What is necessary to implement before using Ichor on these platforms:
- Ichor STL functionality, namely the RealtimeMutex and ConditionVariable.
- Compiler support for C++20 may not be adequate yet.
- Time / effort.
The same goes for Wind River. Freestanding implementations might be necessary for Baremetal support, but that would stray rather far from my expertise.
To add support for -fno-rtti while providing the functionality of std::any and realtime mutexes (at least on linux).
The real-time extensions to mutexes (PTHREAD_MUTEX_ADAPTIVE_NP/PTHREAD_PRIO_INHERIT/PTHREAD_RWLOCK_PREFER_WRITER_NONRECURSIVE_NP) are either not a standard extension or not exposed by the standard library equivalents.
Ichor is licensed under the MIT license.
