<![CDATA[ ]]>Messaging API Concepts
The Solace Messaging Application Programming Interfaces (APIs) are designed with the same core concepts, and they use the same fundamental components to process messages and data. Understanding how the APIs use these components, and how they relate to each other, is necessary to develop applications to send and receive messages over Solace PubSub+.
This section provides an introduction to these core concepts and processing components.
The messaging APIs support both Point-to-Point (PTP) and Publish and Subscribe (Pub/Sub) messaging domains.
PTP messaging is built around the concept of message Queues that clients can publish messages to. Each message is addressed to a specific Queue. Consuming clients can also extract messages from Queues that hold messages for them.
- Publish and Subscribe
Pub/Sub clients address messages to some node in a content hierarchy. These nodes are defined Topics. Publishers and subscribers are generally anonymous and may dynamically publish or subscribe to the content hierarchy. The Solace message bus distributes the messages published to a node to those clients that have subscribed to the same node.
The messaging APIs provide many features, including:
- connection management to Solace PubSub+ event brokers
- addition and removal of topic-based subscriptions
- sending and receiving messages (blocking and non-blocking)
- Direct and Guaranteed message delivery modes
- structured data types that do not rely on a specific architecture or programming language
- extensive support for logging and customizing through property parameters
- Request/Reply messaging support
- Queue Browser support
- PubSub+ Cache client API support