Solace Consulting and Services

Solace Consulting and Services for Event Brokers and Event Mesh Estates

AceMQ helps teams that run Solace event brokers with 24/7 support, consulting, upgrades, health checks and migrations to or from Kafka, IBM MQ and RabbitMQ. We also run Solace estates day to day when you want that. Typical starting points are a message spool that fills, an HA pair that fails over badly, or a mesh link that drops.

A senior engineer, not an SDR. No sales sequence attached.

Fastest response target, by plan
15 min
On-call cover
24/7
AceMQ customers
160+
Years in business
10+

Without replacing the broker your event mesh already runs onFor production incident cover, see AceMQ Solace 24/7 support.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

The Problem

Why teams call us about Solace

Eight Solace problems an AceMQ review starts from, a message spool that one queue fills and an HA pair that fails over while clients keep retrying the old node. If one describes your week, that is where the review starts.

  1. 01

    A message spool fills because one queue has no consumer and no maximum spool size, and every publisher on the broker feels it

  2. 02

    One slow subscriber backs up a message VPN because acknowledgement and flow settings were never tuned

  3. 03

    An HA pair fails over, but clients keep retrying a node that is no longer active

  4. 04

    Config-sync between the pair drifts after a manual change on one node

  5. 05

    An event mesh link between two sites drops after a certificate or firewall change, and bridge queues grow quietly

  6. 06

    A poison message loops between a queue and its consumer because no maximum redelivery count was set

  7. 07

    New applications join the broker with ACL and client profiles copied from the last team, and limits are hit in production

  8. 08

    The estate is on several releases and nobody has mapped the upgrade order

A good fit if Solace brokers carry production traffic and you want one team that answers at night, works the queues and clients, and plans upgrades or a move to another broker.

Not a fit for small teams with non-critical workloads. AceMQ is not a budget consultancy: we work with enterprises running business-critical and compliance-heavy Solace.

Running Solace in production? Get a quote from a senior engineer, answered within one hour.

Contact Us

How it breaks, and the fix

What happens to every publisher when one queue with no consumer fills the message spool?

A Solace broker has one message spool, shared by its queues. A queue that nobody consumes, with no maximum spool size, keeps accepting messages until it has used the spool that every other queue needs, and publishers on the broker can then be refused.

One orphan queue, one full spool

Two publishers, one broker, three queues and their consumers

Illustrative
  1. Publishers send, each queue is consumed and the spool sits well below its quota.

  2. A queue lost its consumer in a decommissioning and has no maximum spool size. It keeps taking messages until the shared spool is full, publishers are refused, and the healthy consumers have nothing to read.

  3. The orphan queue is drained or retired, every queue gets a maximum spool size and a dead message queue, and an alert fires on spool use well before the limit.

More spool quota only delays the next fill. The cause is a queue with no owner: no consumer, no spool limit and no alert. The review finds such queues with the spool and queue views on each broker, bounds each queue, adds a dead message queue and a time to live where the data allows it, and sets per-VPN limits so one team cannot consume the broker. The same pass reads the client side, because most messages reported as lost on a broker turn out to be a reconnect, acknowledgement or window setting.

Our Services

Solace Consulting & Services

AceMQ runs five Solace service lines: health check, architecture and design, upgrade planning, performance and capacity, and migration planning. A senior engineer leads each one, and any of them can roll into 24/7 support with response targets from 15 minutes, by plan.

  • 01

    Solace Health Check

    The fixed-scope entry engagement: a written report on how your Solace brokers are configured and where they are exposed.

    • Message spool and queue sizing
    • Message VPN limits, client and ACL profile review
    • HA pair, config-sync and mesh link state
    • Certificate expiry and client reconnect behavior
  • 02

    Architecture and Design

    A written topology for new or growing Solace estates, so the next team does not copy the last team's settings.

    • Message VPN layout and topic hierarchy
    • Queue patterns: exclusive, non-exclusive, partitioned
    • Replay and replication design
    • Event mesh topology across sites
  • 03

    Upgrade Planning

    A written upgrade path for every broker, rehearsed before production.

    • Inventory of broker releases and the stream each is on
    • Client and API compatibility
    • Backup node first in an HA pair, then a rehearsed switchover
    • A rollback that has been tested
  • 04

    Performance and Capacity

    Sizing from measured traffic, and the slow subscribers that hold everyone else back.

    • Spool and ingress sizing
    • Slow subscriber analysis
    • Flow control and delivery settings
    • Per-VPN limits so one team cannot consume the broker
  • 05

    Migration Planning

    Phased moves between Solace, Kafka, IBM MQ, RabbitMQ and ActiveMQ, with parallel running and a rollback.

    • Topic and queue mapping to the target
    • Delivery guarantee mapping
    • Parallel running and cutover by application
    • An honest answer on whether to stay
  • Response targets from 15 minutes, by plan

    24/7 Solace Support

    Senior engineers briefed on your environment, response targets from 15 minutes, by plan, and no ticket routing.

    • Response targets from 15 minutes, by plan
    • Senior engineers, no first-line triage layer
    • Proactive CVE & health monitoring
    • Quarterly deployment reviews

Want AceMQ to take this off your team's plate? Tell us about your Solace estate.

Contact Us

24/7 Support

Solace Support When It Matters Most

AceMQ Solace support gives you an AceMQ engineer and response targets from 15 minutes, by plan, when a broker is failing, 24/7. It runs beside your Solace plan: Solace supplies releases, fixes and hardware, and AceMQ works your queues, spool limits, HA pairs and mesh links.

  1. From 15 min (by plan)first responseEmergencyProduction down, messages not flowing, queue manager failure
  2. 1 hourfirst responseCriticalSevere degradation, high error rates, approaching capacity
  3. 4 hoursfirst responseHighPerformance issues, configuration problems, non-critical failures
  4. Next Dayfirst responseStandardQuestions, guidance, best practices, non-urgent improvements

Response targets by plan; your contract sets the tier.

P1 escalation path

A replay of one P1, from the first page to the written root-cause analysis

SLA 15:00
T+Elapsed15:00
Engineer on your bridge

Response targets from 15 minutes, by plan; 24/7.
A response time, not a resolution time.

  1. T+00:00

    P1 opened, on-call engineer paged

    Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.

    Paged
  2. T+15:00

    Senior engineer on your bridge

    A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.

    Live
  3. T+30:00

    Specialists across the stack join

    When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.

    If needed
  4. After

    Written root-cause analysis

    Root cause, the fix applied and the prevention steps, delivered after every P1.

    Every P1

How Our Support Actually Works

Beyond SLAs — the model behind senior-only, zero-cold-start expert access.

  • Engineers Who Know Your Environment

    Tickets go to senior engineers briefed on your environment, not an anonymous queue. The proposal states who does the work.

  • Live Escalation on Any Ticket

    Any ticket can be escalated to a live session with an engineer through calendar booking. No gatekeeping and no approval step.

  • Proactive Risk Mitigation

    Scheduled health checks on your deployment and alerts on risks in the versions you run, so problems surface before they reach production.

  • Critical Bug & CVE Intelligence

    Proactive alerts on critical bugs and CVEs affecting your exact version, with version compliance monitoring so you're never caught off guard.

How It Works

What actually happens next

An AceMQ Solace engagement runs in four stages: a scoping call with a quote within 1 hour, a broker assessment, a written plan, then the work or a handover. Each stage ends in writing.

Quote within 1 hour

Scoping call and quote

A senior AceMQ engineer asks what you run: how many brokers and message VPNs, software or appliance, the HA and replication sites, the mesh links, and what has prompted the question. A quote request is answered within 1 hour.

Scoped per estate

Broker assessment

We read the configuration, spool and queue state, HA and mesh topology and client settings, then show which of them your current traffic actually breaks. Findings are written down and your team keeps them.

Scoped per estate

Written findings and plan

Prioritised findings with the reasoning attached, and a straight answer on whether a migration is worth doing. The plan includes a rehearsal and a rollback that has been tested, not assumed.

Ongoing or fixed scope

Run the work or hand over

We change broker configuration and client settings with your engineers, each change staged and reversible. The work ends with runbooks for spool pressure, failover and mesh recovery. You can stop there, add 24/7 cover, or have AceMQ run the brokers for you.

  • Written findings before any change
  • Changes staged and reversible, with a rollback plan
  • Your engineers in the room
  • Ad hoc engagements or an annual partnership

A senior engineer, not an SDR. No sales sequence attached.

Typical engagements

How Solace engagements run

Solace work from AceMQ will appear here as engagements are published. Each card links to the full write-up.

All use cases

Solutions

Every way AceMQ works with Solace.

AceMQ covers Solace end to end. Projects: consulting and implementation, health checks and migrations. Ongoing cover in four tiers, from 24/7 support and incident management to proactive monitoring, managed Solace on your infrastructure and fully managed Solace on AceMQ infrastructure, plus end-of-life versions.

Projects

Build, fix or move Solace

Fixed-scope work led by a senior engineer: architecture and new builds, a health check of what you run today, or a migration with a reversible cutover.

Side by side

Solace on its own support plan, Solace with AceMQ cover, or a move to another broker: what changes?

Solace supplies releases, defect fixes and hardware under your support plan. AceMQ supplies engineers who work your configuration and clients, alongside that plan, and can plan a move to another broker for the workloads that should not stay on Solace. Each row answers one question about the choice.

Solace on its own support plan, Solace with AceMQ cover and a move to Kafka, IBM MQ or RabbitMQ compared on who answers at night, who works the configuration, where fixes come from, what a switch takes and fit
QuestionSolace on its own support planSolace with AceMQ coverMove to Kafka, IBM MQ or RabbitMQ
Who answers at 3am?Solace support, 24/7/365. Severity 1 targets are 30 minutes on Standard Support or Essential Services and 15 minutes on Advanced Services, measured for Severity 1 and 2 only when you contact support by phone (solace.com/support, read 17 November 2026).An AceMQ engineer 24/7, with response targets from 15 minutes, by plan, with your topology and runbooks in front of them. A defect that needs a Solace fix still goes to Solace.Solace still needs cover until the last application has moved. After cutover, the target platform's support route takes over.
Who works your queues, ACLs and clients?Your own engineers. A support plan answers questions about the product; it does not run your estate.AceMQ engineers, remotely, or your team with AceMQ on call.Your team or a provider for the target broker, once the applications have moved.
Where do fixes come from?Solace releases and defect fixes. Hardware repair goes through a Return Material Authorization.Solace, as before. AceMQ plans and applies releases, opens the case with Solace on your behalf and produces no Solace fix itself.The target platform's vendor or community.
What does a switch take?Nothing changes.A scoping call and a quote. Nothing changes in the brokers before the written review.Topics and queues mapped to the target, delivery guarantees compared, both sides run in parallel and cut over by application with a rollback. Solace's protocol support (AMQP, Kafka, MQTT, REST, WebSocket) makes phased moves practical.
When does it fit?You have broker engineers in-house and need Solace's releases and fixes.You want Solace's fixes and a second team that works the estate, answers at night and plans upgrades.The workload no longer needs Solace's features, or the platform is being consolidated, and you can fund a migration project.

To see how a move between brokers is scoped, read legacy messaging modernization.

Not sure which option fits? A senior Solace engineer will scope it with you.

Contact Us

One partner, not five

We Support Your Entire Tech Stack

Solace rarely fails in isolation. AceMQ covers the full surrounding infrastructure — so one team owns the whole path instead of pointing at each other.

See all the technologies we supportShow fewer

An independent view

When does a Solace estate need an independent view?

Solace supports its own product. AceMQ sits beside that support: the engineers who work your queues, spool limits, HA pairs, mesh links and client settings, and who also run your other brokers.

Situations where an independent view of a Solace estate helps, and why
SituationWhy an independent view helps
Solace sits beside Kafka, IBM MQ or RabbitMQOne team and one contract across the brokers, with honest guidance on which workload belongs where
A migration is on the tableSolace's protocol support (AMQP, Kafka, MQTT, REST, WebSocket) makes phased moves possible; the work is mapping semantics and proving them in parallel
Spool or HA incidents repeatThe cause is usually configuration or client behavior, which a defect ticket does not address
You are choosing a brokerWe have no licence to sell, so the comparison is on your requirements

Where AceMQ is not the right fit: hardware replacement and repair, new product features and product defects all go through Solace. See Solace support for who covers what, and legacy messaging modernization for how a move between brokers is run.

FAQs

Solace Questions Answered

Answers on Solace from AceMQ: who provides enterprise support, what a health check includes, how an upgrade or a migration is planned, and what the scope excludes.

Still have questions about Solace? Email an Expert

Who provides enterprise support for Solace?

Solace provides enterprise support for its event brokers through its support plan, with 24/7/365 hours (solace.com/support, read 17 November 2026). AceMQ provides independent Solace support beside that plan or on its own, with response targets from 15 minutes, by plan. Details and a comparison table are on the Solace support page.

Who offers Solace consulting and professional services?

Solace and its partners offer consulting, and independent firms such as AceMQ consult on Solace without a licence to sell. AceMQ's engineers cover health checks, design, upgrades and migrations, and are the same people who work the 24/7 rota.

What does a Solace health check include?

Message spool and queue sizing, message VPN limits, client and ACL profile review, HA and config-sync state, mesh link and bridge queue state, certificate expiry, client reconnect behavior and a ranked plan.

Can AceMQ migrate us from Solace to Kafka, IBM MQ or RabbitMQ?

Yes. We map topics, queues and delivery guarantees to the target, run both sides in parallel and cut over by application with a rollback. Solace supports AMQP, Kafka, MQTT, REST and WebSocket (solace.com/products/event-broker, read 17 November 2026), which makes phased moves practical. We also advise when staying on Solace is the better answer.

Can you move us onto Solace, or onto Solace Cloud?

Yes. The work is the same in reverse: mapping destinations, ACLs and clients, then a phased cutover. Solace Cloud is operated by Solace; we cover the application and configuration layer.

How do you plan a Solace upgrade without downtime?

We inventory releases and clients, upgrade the backup node of an HA pair first, rehearse a switchover, then upgrade the other node, with a rollback. Solace publishes more than one release stream, so the first decision is which stream each broker should follow.

Is Solace PubSub+ the same as Solace Event Broker?

They refer to the same broker product line. Solace's pages use the name Solace Event Broker and still carry the PubSub+ name in places (solace.com/products/event-broker, read 17 November 2026). We support the deployed broker whichever name your team uses.

What does "we run your estate" mean for Solace?

AceMQ operates your Solace brokers day to day on your infrastructure: monitoring, alert handling, patching windows, capacity checks and on-call, with the incident side covered by the support SLA.

Can we work with AceMQ on Solace without a long contract?

Yes. AceMQ works on Solace in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual contract that covers 24/7 support and proactive reviews. Many teams start ad hoc and move to an annual contract once the first engagement is done.

How much does AceMQ Solace support or consulting cost?

Every AceMQ proposal is tailored to your requirements: your Solace environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how Solace is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.

Let's talk

Map the Queues, Limits and Mesh Links Before the Next Spool Alarm

Tell us how many brokers you run, where they sit and what you want to change. We reply to quote requests within 1 hour to schedule a scoping call.

A senior AceMQ engineer, not a sales queueAbout your Solace estate, not a pitch deckQuote requests answered within 1 hour

Production incident right now?Email a Solace Architect

Get in Touch

Talk to a Solace Expert

Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.

305-204-2607
info@acemq.com
66 W. Flagler St. 9th Floor
Miami, FL 33130

Prefer to talk now? Call us directly or use the consultation tab to find a time that works.

We respond within 1 hour.

Pick a time that works — no pressure, no pitch. Just 30 minutes with an expert.

We respond within 1 hour.