Solace supports persistent and non-persistent JMS, version 1.1. Client applications connect to Solace like any other JMS broker so companies whose applications are struggling with performance or reliability issues can easily upgrade to Solace’s hardware or Virtual Message Router.
The Solace JCA adapter enables companies to integrate Solace messaging functionality with other frameworks (such as IBM WebSphere and RedHat JBoss) using Java Connector Architecture. Solace’s JCA adapter handles integration within the container layer so companies can use it to migrate applications from other JMS brokers to Solace without changing any code, which reduces the cost and risk associated with migrating.
Solace supports the OASIS MQTT 3.1.1 standard to meet the needs of connected devices and mobile applications that need an efficient way to send and receive information that requires very little client-side processing power, memory and/or bandwidth. The Solace message router works with any third-party MQTT 3.1.1 compliant client API, including open source APIs available via an Eclipse initiative called Paho.
The Open Middleware Agnostic Messaging API (OpenMAMA) is an open source, lightweight, vendor-neutral integration layer for sending and receiving market data information supported by the Linux Foundation. With unified support for many different kinds of data distribution in a compact, cost-effective platform, Solace’s platform is the ideal foundation for OpenMAMA-based market data distribution systems.
The Solace REST Messaging API allows HTTP clients to send and receive messages with a Solace message router using HTTP POST requests. This enables REST clients to send messages to and receive messages from any Solace message router clients without needing to use any Solace-provided API.