Solace Micro-Integrations and Integration Hub: How Solace Connects Everything Else

Solace Micro-Integrations are small connectors that sit at the edge of the Solace event mesh and move data between one external system and the broker: a database, a SaaS application, another message broker, a file store or a cloud service. Solace’s documentation defines them as “small, lightweight, event-driven integration modules that connect enterprise technologies, such as legacy and SaaS applications, messaging services, databases, filesystems, and AI agents, to Solace event brokers”. Until the May 2025 rename they were called PubSub+ Connectors, and many repositories still carry that name.

This page explains why Solace builds integration this way, the full toolset around it (the Integration Hub, the Transform Processor, the development kit, iPaaS partners and SAP), what it means for a plant, and the open questions as of October 2026. For the company and the rest of the portfolio, start at the Solace hub.

What Solace Micro-Integrations are

A broker only helps systems that can talk to it. The Solace Event Broker speaks SMF, MQTT, JMS, AMQP, REST and WebSocket natively (see protocols and APIs). A Java service, a PLC gateway publishing MQTT or a web application can connect directly. An Oracle database, a Salesforce org, an IBM MQ queue manager or an SFTP drop cannot. Something has to read from or write to those systems in their own terms and turn what it finds into events. That is the job of a micro-integration.

Each one does one thing. Solace’s development kit announcement describes them as “small, purpose-built modules that each move data between one external system and the event mesh, with room for transformation, enrichment, or filtering”. The docs split them by direction: a source carries data from the external system to the broker, and a target carries data from the broker to the external system.

They arrived in December 2024. Solace launched PubSub+ Micro-Integrations on 10 December 2024 in cloud-managed and self-managed forms, naming Boomi, MuleSoft and SAP as platform partners. The launch list of targets ran from SAP, Salesforce, Snowflake and Oracle GoldenGate to IBM MQ, TIBCO EMS, NATS, the hyperscaler queues and five Kafka variants. Five months later the rename to Solace Platform changed the names below.

Former name	Current name (since May 2025)	What it is
Solace PubSub+ Connectors, Connector for [X]	Solace Micro-Integrations, Micro-Integration for [X]	The connectors themselves
Solace PubSub+ Connector Manager	Solace Micro-Integration Manager	Management of self-hosted connectors
Solace PubSub+ Connector for Message Transformations	Solace Transform Processor	Payload transformation between topics

Why Solace calls it integration “inside out”

The product page headline is “It’s time to turn application integration inside out”, and the explanation is that micro-integrations “live at the edge, making life easy by linking systems to an event mesh that distributes data in the middle”.

The contrast is with the central integration engine. In a classic enterprise service bus or iPaaS design, one engine holds every mapping and every route. It is easy to see and govern, but every new consumer is a change to that engine, and the engine’s outage is everyone’s outage. In the micro-integration model, each system gets a small adapter that publishes or consumes events, and the routing lives in the broker’s topics and subscriptions. Adding a consumer becomes a subscription, not a project.

The trade-off is real. Many small adapters are many small things to deploy, version and monitor. The central engine’s weakness (one place for everything) is also its strength (one place to look). The model works when the broker’s topic design and governance are good, which is why Event Portal matters as much as the adapters.

The Solace integration toolset, mapped

Micro-integrations are the newest piece, not the only one. A reader evaluating “how does Solace connect to X” needs the whole map, as of October 2026:

Tool	What it does	Where it runs	Fits when
Micro-Integrations	One system to or from the broker, with transformation, enrichment and header changes	Managed in Solace Cloud, or self-managed as packages or containers	A database, SaaS app, file store or other broker must join the mesh
Integration Hub	The catalogue of Solace, partner and community assets	Web	Finding out whether an integration exists and who supports it
Transform Processor	Reshapes payloads between topics (formerly the Connector for Message Transformations); full XML attribute support added April 2026	Alongside the broker	Two systems agree on the event but not the format
Micro-Integration Development Kit	Build your own; built on Spring Cloud Stream, with an AI-assisted version from July 2026	Your build pipeline	Nothing in the catalogue fits
Kafka bridging and Kafka Connect connectors	In-broker Kafka sender and receiver, plus open-source source and sink connectors	Broker or Kafka Connect	A Kafka estate already exists (see Kafka integration)
iPaaS connectors	A MuleSoft connector on Anypoint Exchange and a Boomi connector	Inside the iPaaS	Orchestrated, multi-step flows stay in the iPaaS
SAP Integration Suite, advanced event mesh	SAP’s event broker service, built on Solace technology	SAP-sold service	The enterprise standardises on SAP BTP (see SAP Advanced Event Mesh)
ASAPIO Cloud Integrator	Reads SAP ERP change pointers and publishes events to Solace over REST	Partner product	Events must come out of SAP ECC

The catalogue grew steadily through 2026. Solace’s What’s New feed records a family of six database change data capture (CDC) micro-integrations in May, a Databricks “Zerobus” connector in July, MongoDB CDC on 30 September and an Amazon S3 target on 8 October. The connectors page groups the catalogue by category.

What Solace Micro-Integrations mean for a plant

Most plant data does not need one. A historian, an Ignition gateway or an edge gateway publishing MQTT talks to the broker directly. Micro-integrations earn their place at the IT side of the plant boundary, where the systems are databases and enterprise applications. That makes them more relevant to the MES and ERP layer than to the controls layer.

An illustrative scenario. A food manufacturer runs a MES whose production orders and confirmations live in a SQL Server database the vendor will not change. Today a nightly batch job copies completed orders to the ERP and a separate script feeds a quality dashboard. With a CDC source micro-integration on that database, each confirmed order becomes an event on a topic such as site/plant2/line4/order/confirmed. The ERP integration, the quality dashboard and a new data platform each subscribe. Adding a fourth consumer next year needs no change to the MES database, no new script and no new extract. Bosch describes a comparable pattern for production orders and confirmations in its Solace case study, which Solace publishes.

The CDC caveat matters in plants. Change data capture reads the database’s transaction log, which is low-impact compared with polling, but it couples you to the vendor’s table design. If the MES vendor changes the schema in an upgrade, the events change too. Treat the event schema as a contract, version it, and test it in your MES upgrade plan. Our IT/OT integration work starts from exactly that kind of interface inventory.

Limits and open questions

• No published catalogue count. The Integration Hub shows no total, and support status varies per entry (Solace-supported, partner-supported or community). A community asset is not a supported product.
• Not every integration is offered in both deployment models. The docs describe managed and self-managed options in general. Confirm per integration which models are available, and for which direction (source or target).
• No public pricing. Solace publishes no price for micro-integrations, and we found nothing public on whether they are licensed separately or consumed from a platform capacity agreement. Ask.
• Kafka bridging is documented for software brokers. The in-broker Kafka bridge is documented for software brokers; appliance and Solace Cloud support is not stated in the docs we found.
• Light transformation is not orchestration. Micro-integrations transform, enrich and filter. Multi-step business processes, compensation logic and human approval still belong in an iPaaS or application code.
• Many small deployments. Self-managed micro-integrations need container hosting, patching, secrets management and monitoring, per adapter.
• The names are still in transition. Repositories and images under pubsubplus and “connector” will appear in search results for some time.

How to evaluate it

• List the systems that must publish or consume events but cannot speak MQTT, JMS, AMQP or REST. That list is your micro-integration scope.
• For each, check the Integration Hub: does it exist, which direction, who supports it?
• Is it available managed, self-managed or both, and which does your security team accept for that system?
• For CDC sources: which database versions are supported, what permissions does it need, and what happens to events when the schema changes?
• How are failures surfaced? Ask how a stalled adapter shows up in monitoring and how far it can fall behind before data is lost.
• What is the commercial model, and is it in your quote?
• Which flows stay in your existing iPaaS, and who owns the boundary between the two?
• Who owns the topic and schema design that the adapters publish into?

Deeper

• Solace connectors and the Micro-Integrations catalogue: the catalogue by category as of October 2026, managed versus self-managed placement, and where connectors get hard
• SAP Advanced Event Mesh: SAP’s event broker service built on Solace technology, how SAP and Solace describe the relationship, and how it differs from SAP Event Mesh

Back to the Solace hub, or across to Event Portal, where the events that micro-integrations publish are designed and catalogued, and to the Solace partners and ecosystem page for iPaaS and technology partners.