iceoryx
A true zero-copy inter-process-communication (IPC) middleware for high-performance data transfer between processes.
What is iceoryx?
Eclipse iceoryx is a high-performance inter-process-communication (IPC) middleware that enables true zero-copy data transfer between processes using shared memory. It solves the problem of efficiently moving large data volumes in real-time systems, such as automotive driver assistance or robotics, without the latency overhead of traditional copying methods.
Developers building real-time, data-intensive systems in automotive, robotics, or gaming where low-latency, high-throughput IPC is critical. It is also suited for framework integrators needing a transport layer for larger middleware stacks.
Developers choose iceoryx for its true zero-copy architecture, which guarantees constant latency regardless of data size, and its multi-platform support. It provides a robust, efficient foundation for high-performance IPC without the serialization bottlenecks of conventional approaches.
Overview
Eclipse iceoryx™ - true zero-copy inter-process-communication
Use Cases
Best For
- Automotive systems requiring high-bandwidth sensor data sharing
- Robotics applications with real-time inter-process communication needs
- Game engines needing low-latency data transfer between components
- Integrating as a transport layer in middleware frameworks like ROS 2
- Building real-time data pipelines in embedded or edge computing
- Developing high-performance IPC for safety-critical systems
Not Ideal For
- Projects with lightweight, infrequent inter-process communication that don't justify the shared memory complexity
- Systems where shared memory is restricted due to security or sandboxing policies (e.g., cloud-native or containerized environments with strict isolation)
- Teams needing out-of-the-box serialization, message queuing, or high-level abstractions without custom integration
- Cross-platform applications requiring uniform access control and feature support across all OSes (since macOS, FreeBSD, and Windows lack full access rights implementation)
Pros & Cons
Pros
Uses shared memory to transfer data without copying, ensuring constant latency regardless of payload size, as emphasized in the introduction for real-time applications like automotive systems.
Supports Linux, macOS, QNX, FreeBSD, and Windows 10, making it suitable for embedded, desktop, and automotive environments with diverse OS requirements.
Provides a typed C++ API for ease of use and low-level plumbing APIs for custom implementations, facilitating integration into larger frameworks like ROS 2 and eCAL.
Originated in automotive industry with defined quality levels (e.g., target level 1+ for QNX), ensuring reliability for safety-critical systems as per the quality declaration.
Cons
Access rights for shared memory are not supported on macOS, FreeBSD, and Windows, and command line parsing is pending on Windows, limiting security and ease of use on those OSes.
Focuses solely on the transport layer; lacks built-in serialization, service discovery, or advanced messaging patterns, requiring additional layers for full middleware solutions.
The distinction between plumbing and porcelain APIs means developers must handle low-level details or integrate with frameworks, increasing initial setup complexity compared to all-in-one IPC libraries.
Frequently Asked Questions
Related Projects
bRPCbrpc is an Industrial-grade RPC framework using C++ Language, which is often used in high performance system such as Search, Storage, Machine learning, Advertisement, Recommendation etc. "brpc" means "better RPC".
Cap'n ProtoCap'n Proto serialization/RPC system - core tools and C++ library
nanomsgnanomsg library
nngnanomsg-next-generation -- light-weight brokerless messaging
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.