Solace makes it easy to connect all kinds of applications to your event mesh with a rich set of APIs, support for all popular protocols, and packaged micro-integrations.
APIs / Client Libraries
Solace messaging APIs provide uniform client access to all Solace Platform capabilities and qualities of service. Each API includes sample applications, release notes, and developer documentation. APIs are available for the following languages:
- C: Provides high message throughput and low latency with minimal CPU utilization.
- C# / .NET: An object-oriented, managed wrapper for the C API.
- Go: Enables cloud-based and enterprise-scale server-based apps to use Solace messaging.
- iOS: An iOS native wrapper of the C API designed for high message throughput and low latency.
- Java: High message throughput utilizing modern Java features and programming models.
- Java RTO: A low-latency Java Native Interface (JNI) wrapper for the C API.
- JCSMP: A classic, object-oriented Java API that delivers high message throughput with low latency.
- JavaScript: Enables Web and mobile applications to use Solace messaging.
- JMS: Provides a common way for Java programs to create, send, receive and read messages.
- Node.js: Enables server-side web-connected enterprise apps use Solace messaging and take advantage of event-based programming.
- Python: Enables cloud-based and enterprise-scale server-based applications to use Solace messaging.
Open APIs and Protocols
AMQP / Qpid
Advanced Message Queuing Protocol is an open standard for sending information between applications, and Apache Qpid is an open source implementation of AMQP that offers transaction management, queuing, distribution, security and multi-platform support. Solace supports the OASIS-recognized version of AMQP, as do the Apache Qpid APIs.
JMS
Java Message Service is a Java messaging specification that enables messaging between computers in a network. Solace Event Broker supports persistent and non-persistent JMS, and client applications can connect to Solace like any other JMS broker. The Solace JCA adapter enables companies to integrate Solace messaging functionality with frameworks like IBM WebSphere and RedHat JBoss, and handles integration within the container layer so companies can use it to migrate applications from other JMS brokers to Solace without changing any code.
MQTT
MQTT is a publish/subscribe messaging protocol ideal for communications between systems where a small code footprint is needed or network bandwidth is limited. Solace Event Broker supports the latest MQTT standards, and works with any third-party MQTT-compliant client API, including open source Paho APIs.
REST
Applications can send and receive messages to/from a Solace Event Broker using native HTTP client libraries instead of any messaging client libraries.
WebSocket
Solace enables streaming and Web messaging with APIs for JavaScript and iOS, and supports HTML5 WebSocket for full-duplex communication channels over a single TCP connection.
Micro-Integrations
Micro-integrations replace monolithic integration flows with small, manageable, purpose-built components, making it easier for applications and devices to exchange information, and improving the performance and reliability of legacy integration tools. Most micro-integrations consist of a connector and functions like payload transformation, data enrichment, and header modification. You can build micro-integrations with your iPaaS or favorite code framework, or find one in our Integration Hub and deploy it from within Solace Platform’s cloud console.
Learn moreVisit Integration Hub