this post was submitted on 19 May 2026
12 points (100.0% liked)

Programming

27205 readers
681 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
12
iceoryx2 v0.9 released: Fast and Robust Inter-Process Communication (IPC) Library (ekxide.io)
submitted 3 weeks ago* (last edited 3 weeks ago) by elBoberido@programming.dev to c/programming@programming.dev
2 comments fedilink hide all child comments
 

Hello everyone

We released iceoryx2 v0.9 tonight. With the release, we are pushing more and more iceoryx2 into the embedded world. We have written a test runner that runs on std and no_std environments, stabilized the decentralized recovery, and added a ton of quality of life improvements.

For those who haven’t heard of it yet: iceoryx2 is a zero-copy inter-process communication library.

The basic idea is: instead of serializing data, copying it through sockets, pipes, message queues, or some broker process, iceoryx2 lets processes communicate via shared memory. That makes it useful when you care about latency, throughput, or moving large amounts of data between processes without wasting CPU cycles on copies.

It supports C, C++, Python, Rust, and C#, and runs on Linux, macOS, Windows, FreeBSD, and QNX, with experimental support for Android and VxWorks.

It is not limited to plain pub/sub either. iceoryx2 supports publish-subscribe, events, request-response streams, and a blackboard pattern, which is basically a key-value repository directly in shared memory.

The architecture is fully decentralized: no central broker, no daemon that everything depends on, and no single process that becomes the obvious bottleneck or failure point.

Happy to answer questions about the release, the no_std work, or zero-copy IPC in general.

you are viewing a single comment's thread
view the rest of the comments
[–] elBoberido@programming.dev 2 points 4 days ago

@kibiz0r@midwest.social sorry for the late reply. I'm not that familiar with CRDTs but what I understand, the blackboard is not a direkt match. It is intended for data that does not change or at least only rarely change. Contrary to the other messaging pattern like publish-subscribe or requrest-response, the blackboard does copy on access. This means, it is ideal for things like providing a configuration to other processes or other small data.