Solace Use Cases by Industry, Explained

Solace use cases by industry: capital markets, retail, aviation, logistics and manufacturing, the event patterns each relies on, and the named customers.

Solace use cases fall into a short list of patterns that repeat across very different industries: fanning out fast-changing state such as prices or flight status, moving transactions that must not be lost, linking hundreds or thousands of remote sites to the centre, spanning on-premises and several clouds, and replacing batch files or ageing middleware. Solace grew up in capital markets, and today its public case studies also cover retail, airlines, ports, trucking, insurance and manufacturing. This page maps those industries to the patterns, names the customers Solace has published, and draws out what a manufacturer can borrow from each.

It belongs to the Solace hub. If you came here for plants, go straight to Solace in manufacturing, which covers the unified namespace, Sparkplug B and multi-site edge to cloud in depth.

Solace use cases at a glance

The table summarises each industry in Solace’s public material. Customer names and figures come from Solace’s own customer stories and press releases, so read them as vendor-published claims, as of October 2026.

Industry	What drives it	Patterns that recur	Named customers (Solace states)
Capital markets	Latency, volume spikes, fan-out to thousands of trading applications	Direct-messaging fan-out of prices; guaranteed flows for orders and trades; links between trading centres	RBC Capital Markets, Barclays, Standard Chartered, LSE Group, TMX Group
Banking and insurance	Digital channels, fintech partners, hybrid cloud	Events alongside APIs; batch and polling replaced	TAB Bank, Indiana Farm Bureau Insurance
Retail	Thousands of stores, daily price changes, omnichannel orders	Store-to-centre mesh; price and product fan-out; batch replaced	Schwarz Group, EDEKA, Les Mousquetaires, HORNBACH
Aviation	Disruption recovery, many partners and agencies	Multi-region cloud brokers; dozens of systems integrated; public data feeds	United Airlines, Bengaluru Airport, FAA SWIM
Logistics and transport	Automation, assets on the move, legacy systems in transition	Buffering between equipment and applications; old and new systems kept in step	PSA Singapore, Bison Transport
Manufacturing	IT/OT integration across many plants, ERP	Enterprise backbone above plant systems; master data and production orders	Bosch, Danone, Heineken, Absolics

Solace also lists telecoms (Jio, Airtel) and gaming (bet365, ATG) on its customer page, without published architecture detail.

The five patterns behind Solace use cases

Why patterns matter more than industries. A trading floor and a supermarket chain look nothing alike, but the integration problem underneath is often the same. Reading case studies by pattern lets an engineer in one industry learn from another, and it is the honest way to judge whether a reference applies to you.

Fan-out of fast-changing state. One source, many consumers, and only the latest value matters: a currency price, a shelf price, a gate change. The broker routes on hierarchical topics so each consumer subscribes only to what it needs. The messaging model page explains direct messaging and topic routing.
Guaranteed transactions. An order, a trade confirmation or a production order must arrive exactly once in the business sense, in order, even if the consumer is down. Queues spool messages until they are acknowledged.
Many sites linked to the centre. Stores, airports, trading centres and plants each run a broker locally, and an event mesh routes events between them over the WAN, only where a subscriber exists.
Hybrid and multi-cloud. Brokers on-premises and in more than one cloud act as one routing fabric, so an application can move without its publishers and subscribers being rewired.
Batch files and legacy middleware replaced. The single most common story in Solace’s case studies is not “we built something new” but “we stopped exchanging files overnight” or “we retired the old message bus”.

Manufacturing shares three of its patterns with capital markets. That overlap is why lessons from trading floors transfer to multi-plant integration better than the industries' differences suggest.

Capital markets: where Solace started

Solace was founded in Ottawa in 2001 to put messaging into hardware, and banks were its first market. Solace states that 6 of the 10 biggest investment banks and 3 of the top 6 FX trading banks use it (solace.com). Its largest published deployment is RBC Capital Markets, which Solace says grew from 65 billion to over 118 billion messages a day without outages. The driver is fan-out at low latency: one price update reaching every trading application that needs it, in microseconds, through volatile days.

The financial services page covers market data, FX, exchanges and post-trade in detail.

Retail, airlines and logistics: the edge is a store, a gate or a crane

These industries share a shape: thousands of remote locations, each changing state all day, and a centre that needs to see it now rather than overnight. Les Mousquetaires, Solace states, deployed more than 450 new event flows in two years across over 4,000 outlets, including real-time price updates to digital shelf tags (case study). United Airlines reports about six billion events a day through its brokers and four hours cut from outage recovery (case study). PSA Singapore uses Solace between automated port equipment and the applications that run it (case study).

The retail, airlines and logistics page works through order, inventory and flight-operations event flows.

Manufacturing: the backbone above the plant

This is the industry most of our readers work in, and it has its own section. Solace lists Bosch, Danone, Heineken, JDE Peet’s, Renault Group, Stellantis, Airbus and Absolics among its manufacturing customers. The published stories describe enterprise integration, not plant-floor data collection: Bosch distributes production master data and runs production order and confirmation flows (case study); Danone runs an event mesh across more than 100 production sites and 300 distribution centres, joining MES, WMS, SAP and IoT (case study).

An operator smiling at a computer workstation on a busy factory production floor — Manufacturing reuses the patterns banks and retailers proved: fan-out of master data, guaranteed production orders and many sites linked to the centre.

In practice that places Solace above the plant’s own data layer. PLCs, SCADA and a plant MQTT broker or unified namespace handle the line; the event mesh links sites to each other, to ERP and to the cloud. Solace in manufacturing explains that placement against ISA-95, and its child pages cover the unified namespace, Sparkplug B and multi-site edge to cloud.

What a plant can borrow from other industries

The point of reading other industries’ case studies is to borrow solutions to problems a plant already has. The mapping below is our reading, not Solace’s.

Pattern proven elsewhere	Where it was proven	The plant equivalent
Price updates fanned out to every store shelf	Retail (Les Mousquetaires, HORNBACH)	Recipe, specification and master data changes pushed to every site, instead of nightly exports
A broker in each store, linked to the centre	Retail (HORNBACH)	A broker per plant, so a WAN outage does not stop the line and events catch up afterwards
Old and new systems kept in step during a multi-year migration	Logistics (Bison Transport’s TMS replacement)	An MES or ERP migration where the old and new systems must both see production events for a year or more
Buffering between automated equipment and applications	Ports (PSA Singapore)	A “shock absorber” between line-speed data and slower business systems
One governed catalogue of event streams for outside parties	Aviation (FAA SWIM with AsyncAPI)	A documented event catalogue for suppliers, co-packers and contract manufacturers
Many teams onboarded without touching production	Banking (RBC)	New consumers such as analytics, quality or AI agents added without changing PLC or SCADA code

An illustrative scenario. A food manufacturer with nine plants changes a product specification. Today, an export runs at 02:00 and two plants miss it because a file transfer failed. With a per-plant broker and a mesh, the change is published once on a topic such as spec/product/1234/updated, each plant’s MES subscribes, and a plant that is offline receives it from its queue when the link returns. The pattern is the retail price-update story, pointed at a different payload.

Limits and open questions

Case studies are vendor-published. Figures such as RBC’s 118 billion messages a day or United’s six billion events are Solace’s or its customers’ statements, not independent measurements. None publish cost, project duration or what went wrong.
Logo lists are not architectures. Renault Group, Stellantis, Airbus, Groupe Rocher and Sonos appear as manufacturing logos with no published project detail, as of October 2026.
Several stories predate the 2025 rename. Older case studies describe “PubSub+” and sometimes the hardware appliance. Ask which form factor and version the reference runs today.
The plant floor is not Solace’s published strength. Solace’s MQTT has documented limits (QoS 2 is downgraded to QoS 1, QoS 1 shared subscriptions to QoS 0, retained messages are in controlled availability), and it is not on the Eclipse Sparkplug compatible list. See the MQTT page.
Pricing is not public. The Standard Edition is free but marked “not production deployable” in the docs, and Enterprise and Solace Cloud pricing comes from sales. See editions and pricing.
Industry fit is not a reason on its own. Kafka, IBM MQ, HiveMQ and cloud services each win in some of the same industries. The alternatives page compares them on equal terms.

How to evaluate Solace use cases against your own

Which of the five patterns does our problem actually need? Write them down before reading any case study.
Is there a published reference in our industry with our pattern, or only a logo?
Can the vendor arrange a reference call with a customer of similar size, sites and team skills?
Does the reference run the same form factor we would (Solace Cloud, software broker or appliance)?
What did the reference replace, and how long did old and new run side by side?
Which team owns the brokers at the reference, IT integration or OT? Do we have that team?
What is our hardest flow (highest volume, strictest ordering, least tolerant of loss), and can a pilot prove it in four to six weeks?
What would the same outcome cost on the platform we already run?

If these questions expose gaps in your current architecture rather than a product choice, a modernization roadmap is the better first step, and the vendor-neutral event-driven architecture guide explains the concepts without a product attached.

Deeper

Solace in Financial Services: the origin market. Market data fan-out, FX, exchanges and post-trade, with RBC, Barclays, Standard Chartered, LSE Group and TMX Group
Solace in Retail, Airlines and Logistics: order, inventory and flight-operations event flows, with HORNBACH, Les Mousquetaires, United Airlines, the FAA and PSA Singapore

Also see Solace in Manufacturing, the cluster’s deepest section, and back to the Solace hub.

Frequently asked questions

What is Solace used for?

Solace is used to move events between applications in real time: market prices to trading desks, price changes to store shelves, flight status to airline systems, production orders to plants. Its Event Broker handles publish-subscribe fan-out, guaranteed queues and request-reply, and brokers can be linked into an event mesh across data centres, clouds and remote sites. Most published use cases replace batch files or older messaging middleware.

Which industries use Solace?

Solace's public case studies cover capital markets and banking, insurance, retail, aviation, logistics and transport, manufacturing, telecoms and gaming. Capital markets is the origin market: Solace states that 6 of the 10 biggest investment banks use it. Named customers elsewhere include United Airlines, the FAA, PSA Singapore, Schwarz Group, HORNBACH, Bosch, Danone and Heineken, as of October 2026.

Is Solace used in manufacturing?

Yes. Solace lists Bosch, Danone, Heineken, JDE Peet's, Renault Group, Stellantis, Airbus and Absolics among its manufacturing customers. In public material its role is the enterprise backbone above plant systems: distributing master data and production orders, linking sites and feeding ERP. It is usually not the plant-floor MQTT broker. Our manufacturing page covers the detail.

Who are Solace's biggest customers?

Solace does not rank its customers. The largest published deployment is RBC Capital Markets, which Solace states handles about 118 billion messages a day. Its homepage also names Barclays, Danone, the Federal Aviation Administration, Heineken, JDE Peet's, Renault Group, Stellantis, Unilever, United Airlines, Les Mousquetaires and PSA Singapore, as of October 2026.

Do vendor case studies prove Solace will work for my company?

No. A case study shows that a pattern worked for one organisation with its own team, budget and partner. It rarely states what failed, what it cost or how long it took. Use case studies to find comparable patterns, then ask the vendor for a reference call with a customer of similar size and industry, and test your hardest flow in a pilot.

Solace Use Cases by Industry: Banks, Retail, Airlines, Logistics and Plants