publish_subscribe

Publish-Subscribe

Running The Example

Caution

Every payload you transmit with iceoryx2 must be compatible with shared memory. Specifically, it must:

• be self contained, no heap, no pointers to external sources
• have a uniform memory representation -> #[repr(C)]
• not use pointers to manage their internal structure

Data types like String or Vec will cause undefined behavior and may result in segmentation faults. We provide alternative data types that are compatible with shared memory. See the complex data type example for guidance on how to use them.

This example illustrates a robust publisher-subscriber communication pattern between two separate processes. The publisher sends two messages every second, each containing [TransmissionData]. On the receiving end, the subscriber checks for new data every second.

The subscriber is printing the sample on the console whenever new data arrives.

To observe this dynamic communication in action, open two separate terminals and execute the following commands:

Terminal 1

cargo run --example publish_subscribe_subscriber

Terminal 2

cargo run --example publish_subscribe_publisher

Feel free to run multiple instances of publisher or subscriber processes simultaneously to explore how iceoryx2 handles publisher-subscriber communication efficiently.

You may hit the maximum supported number of ports when too many publisher or subscriber processes run. Take a look at the iceoryx2 config to set the limits globally or at the API of the Service builder to set them for a single service.