In the world of Iceoryx2, communication is at the core of everything. To facilitate seamless communication, we always begin by opening or creating a service, the fundamental building block of an Iceoryx2 application. Services serve as the conduit through which different parts of your application interact.
The type of service you create is defined by a messaging pattern, which dictates how data flows between participants. Iceoryx2 supports various messaging patterns, including:
-
Publish-Subscribe: In this pattern, a publisher sends a continuous stream of data to one or more subscribers, enabling real-time data dissemination.
-
Request-Response: (planned) This pattern enables clients to send requests to a server, which in turn responds with the requested data or action, making it suitable for interactive, transactional communication.
-
Pipeline: (planned) Borrowed from the Unix command line, this pattern involves a data source that produces data and transfers ownership to a sink, where it can be modified or processed in a pipeline-like fashion.
The service itself acts as a factory, creating service participants, often referred to as "ports." These ports establish communication links between different components of your application. Each service can be customized with a specific quality of service to meet the unique requirements of your application.
Within the service builder, you can configure various service-specific quality of service parameters, ensuring that your communication behaves exactly as you intend. The service port factory allows you to fine-tune the settings and behavior of individual ports, giving you precise control over how they interact and exchange data.
| Name | Description |
|---|---|
| discovery | List all available services in a system. |
| event | Exchanging event signals between multiple processes. |
| publish subscribe | Communication between multiple processes with a publish subscribe messaging pattern. |