The 4 elements of modern messaging middleware

Your legacy messaging middleware wasn’t built to communicate with today’s cloud-native, IoT and mobile technologies. It wasn’t built for modern microservices, event-driven architectures, or for the creation of an event mesh. And it doesn’t play well with open source. Today’s middleware must be able to do the following:

Plug into your existing apps and infrastructure on-premises

Let’s be real: there’s a good chance a hybrid cloud architecture will be your end state. And even if it isn’t, eliminating or migrating legacy technologies to the cloud doesn’t happen overnight.

Integrate your cloud-native apps and cloud services

And yes, this includes your containerized apps and your iPaaS. But connecting these things is only half the battle. Your messaging middleware should enable robust and event-driven data transport.

Supercharge IoT communications, and more

Your middleware should handle the highly scalable and efficient communication between IoT and mobile devices (thousands, millions and maybe billions of them), cloud apps and back-end systems.

Create digital transformation responsiveness

As your digital transformation (and the market) unfolds, your messaging middleware should move at the speed of change in enterprise IT without locking you in to any vendor or technology.

The future of messaging middleware

Hardware. Software. Cloud. PubSub+ is messaging middleware for distributed, event-driven enterprises.

Gartner refers to PubSub+ as an advanced event broker, which means it supports the publish-subscribe messaging pattern (among others), can be managed in the cloud and deployed in all environments (public cloud, private cloud, on-premises), and it provides all the enterprise-grade features and capabilities provided by traditional message-oriented middleware, and then some.

Explore a few use cases

Innovation takes collaboration. Here are a few of our partners:

grey_logos_pivotal
grey_logos_f5
grey_logos_sap
grey_logos_boomi

PubSub+ capabilities

Dynamic Message Routing

Without DMR, you must know what publishers are producing the data you want, configure messaging connectivity to wherever that data is being published, and manually configure routing rules to move the data to where consuming applications want it. This works, but DMR makes it much simpler by automating all the labor and providing intelligent, self-learning routing capabilities.

Learn more about DMR

Enterprise-grade performance​

Low latency, high availability, fault tolerance, and guaranteed delivery. And that’s just the start of it. PubSub+ is used and trusted in the most mission-critical environments. When we say tomorrow-proof, we mean it: The Royal Bank of Canada pushes 65 billion messages a day through PubSub+. And Airtel moves 100 billion, but who’s counting?

See the performance metrics

Message replay​

Replay allows a message broker to resend messages to new or existing clients that request them—hours or even days after those messages were first received by the message broker. With replay enabled, message brokers store persistent messages in a replay log. These messages are kept until the log is full, after which the oldest messages are removed to free-up space for new messages.

See how it works

Enterprise-grade functionality

PubSub+ supports multiple message exchange patterns (pub-sub, queuing, streaming, request-reply), open standard protocols and APIs (AMQP 1.0, MQTT, REST/HTTP, JMS, WebSocket), multiple Qualities of Service (persistent/guaranteed, non-persistent, direct), WAN optimization, burst-handling, filtering, governance and security, and message caching. We’d keep going but we ran out of space on this card.

Go deep-diving at docs
Our clients get the high rate, low and consistent latency they’re used to receiving from their messaging middleware on premises, but in a messaging layer that extends beyond their legacy infrastructure, to their public and private cloud infrastructure, the IoT and mobile technologies.”

Shawn McAllister CTO, Solace

But there’s one more thing (well, four)

Unified messaging middleware API

Solace provides enterprise messaging Application Programming Interfaces (APIs) that enable you to develop applications for use with PubSub+. Each API includes sample applications, release notes and developer documentation. APIs are provided for Java, C#/.NET, JavaScript, Node.js, iOS, C and Java RTO.

Learn more about our support for APIs & protocols

Open source messaging middleware technologies

The PubSub+ platform offers plug-and-play integration with JMS-based middleware like Apache ActiveMQ and RabbitMQ. And configuring Solace as the transport for open source frameworks lets developers using Apache Camel, UltraESB, WSO2, Mule and jBoss improve the performance of their applications and ESBs. And of course we support OpenMAMA and open wireline protocols such as AMQP, MQTT and REST.

See what OpenMAMA is all about

The Solace-enabled event mesh

Once deployed in multiple environments, PubSub+ advanced event brokers can be easily connected to form an event mesh that is self-routing, self-learning and self-healing, enabling the automated and efficient transmission of events between producer and consumer applications, wherever they run on the mesh.

What's an event mesh? Learn about it here.

Deploy as software, hardware, or as a service

You can deploy PubSub+ however you’d like, wherever you’d like. The IaaS/PaaS-ready PubSub+ Event Broker: Software runs on any computer in a virtual machine or a container. PubSub+ Event Broker: Cloud is a managed messaging as a service (MaaS) that lets developers tap PubSub+ power without installing, maintaining or upgrading messaging software. And PubSub+ Event Broker: Appliance routes messages entirely in hardware for unparalleled capacity, performance and robustness—with the low TCO of a turnkey appliance.

Explore the full product suite

Not all messaging middleware is created equal.

Have questions about how to modernize yours?

Let’s connect