Is the training remote or onsite?

Both are available and both work well. Remote sessions are delivered live rather than pre-recorded, with the same hands-on lab access. Onsite tends to produce better engagement for larger groups and is worth the cost when you are training a whole platform team at once. Our engineers span 26+ countries, so remote delivery can be scheduled in your team's working hours rather than ours.

How many people can attend?

Eight to twelve attendees is the sweet spot. Below that the hands-on portions lose the discussion that makes them valuable, and above about fifteen the instructor cannot give meaningful individual attention during lab work. For larger organizations we run multiple cohorts rather than one oversized session.

Do attendees need prior RabbitMQ experience?

Not for the administrator or developer tracks, which start from architecture fundamentals. Attendees should be comfortable with the command line, basic networking, and — for the Kubernetes track — Kubernetes itself. The troubleshooting workshop does assume working RabbitMQ familiarity and is not a good first course. The assessment phase catches mismatches before the course starts.

Is this the same as official RabbitMQ certification?

No. We deliver practical training rather than a vendor certification program, and we issue a certificate of completion rather than an accredited credential. What we offer that certification generally does not is training against your actual deployment, your versions, and your queue types, taught by engineers who resolve production RabbitMQ incidents as their day job.

Can you train us on our own environment rather than a lab?

Partly, and we would advise against doing it entirely. Lab clusters exist so attendees can break things — trigger partitions, exhaust memory, kill nodes — which is exactly what teaches the material and exactly what you cannot do in your environment. We tailor the curriculum to match your topology and versions, and the final sessions apply that directly to your real deployment.

What does the training actually cost?

Pricing depends on track, delivery mode, cohort size, and how much customization the curriculum needs. It is quoted per engagement rather than per seat, which usually works out better for teams training more than a handful of people. Contact us with your team size and what you are trying to achieve and we will return a quote within 24 hours.

Can training be combined with an implementation or migration?

Yes, and this is the most effective way to buy it. When training runs alongside an implementation or migration engagement, your team learns against the system being built and takes ownership as it goes, rather than receiving a handover document at the end. Customers who combine the two consistently reach operational independence faster than those who treat training as a separate later purchase.

RabbitMQ Training

RabbitMQ Training Taught by Engineers Who Run It in Production

Most RabbitMQ courses teach the tutorial. Ours teaches the failure modes — why memory alarms fire, what actually happens during a network partition, and how quorum queues behave when a node disappears. Every session is hands-on against a real cluster your team breaks and repairs.

The only partner with direct RabbitMQ core team access

11 + senior RabbitMQ SMEs130 + enterprise customers26 + countries served5 session core curriculum

Available Now

Book a free Consultation.

Prefer to chat first?

Prefer to E-mail?

info@acemq.com

Trusted for mission-critical RabbitMQ by teams in finance, healthcare, defense, and telecom

Is This You?

You probably need this if…

Your team inherited a RabbitMQ deployment nobody on staff originally designed

One engineer understands the cluster and everyone else escalates to them

On-call engineers can restart nodes but can't diagnose why the alarm fired

Developers are using RabbitMQ as a simple queue and hitting problems the docs already warn about

You're migrating to quorum queues and the team's mental model is still classic mirrored queues

New platform hires need to reach operational competence faster than trial and error allows

You're about to take a RabbitMQ implementation in-house from a consultancy

Incidents get resolved but the team can't explain afterwards what actually happened

Outcomes

Where you are now, and where you end up

Concrete state changes, not deliverable counts. This is what actually differs about your RabbitMQ estate when the engagement closes.

Before

A single engineer is the only person who genuinely understands the RabbitMQ estate.

After

The whole platform team can diagnose and act independently, with the bus factor removed as an operational risk.

Before

On-call response is restart-and-hope, because nobody can read what the broker is telling them.

After

On-call engineers interpret memory watermarks, flow control state, and queue metrics correctly and act on the actual cause.

Before

Developers treat RabbitMQ as a black-box queue and hit acknowledgement and prefetch problems repeatedly.

After

Developers understand the delivery guarantees they are actually getting and write consumers that behave correctly under failure.

Before

The team's mental model is classic mirrored queues, while production is moving to quorum.

After

Accurate understanding of quorum queue semantics, member behavior, and the operational differences that matter.

Before

Every incident is a first-time investigation because nothing was ever internalized.

After

A team that has already rehearsed partitions, node loss, and backlog scenarios in a lab before meeting them in production.

The Engagement

How it actually runs

Every phase has a defined duration and a concrete artifact handed over at the end of it. You always know what stage you're in and what you've received.

Phase 11 week

Assessment & Tailoring

We establish what your team already knows and what your deployment actually looks like. A team running RabbitMQ on Kubernetes with quorum queues needs a different course from one running classic queues on VMs, and generic training wastes most of its time on material that does not apply to you.

You receive

Skills assessment across the attending team
Curriculum tailored to your deployment and queue types
Agreed learning objectives and success criteria

Phase 25 sessions

Core Sessions

Instructor-led sessions delivered onsite or remotely, each pairing concept with immediate hands-on work. Sessions are typically half-days spread across two to three weeks rather than a compressed week, because retention is materially better when people apply material against their own systems between sessions.

You receive

Five instructor-led sessions with a working engineer
Course materials and reference slides retained by your team
Per-session exercises against a live lab cluster

Phase 3Throughout

Hands-On Lab Work

Each attendee gets a lab cluster to break and repair. This is where the training actually lands — reading a real memory alarm, triggering a real partition, and recovering under-replicated quorum queues teaches what slides cannot.

You receive

Dedicated lab environment per attendee
Guided failure scenarios with worked solutions
Troubleshooting exercises drawn from real production incidents

Phase 42 weeks after

Assessment & Follow-Up

We verify the training took. Attendees complete a practical assessment against the lab, and we run a follow-up session a couple of weeks later once real questions have surfaced from applying the material to your actual environment.

You receive

Practical assessment with per-attendee results
Follow-up Q&A session after material has been applied
Written reference guide specific to your deployment
Recommendations for gaps that need further work

Curriculum

What your team walks away knowing

MODULE 01

RabbitMQ Architecture & Core Concepts

Exchanges, queues, bindings, and routing. The AMQP model, what the broker actually guarantees, and where those guarantees end.

MODULE 02

Queue Types in Depth

Classic, quorum, and stream queues — durability semantics, memory behavior, and choosing correctly per workload rather than by default.

MODULE 03

Clustering & Network Partitions

How clustering works, Erlang distribution, partition handling strategies, and what actually happens to your data during a split.

MODULE 04

Publisher Confirms & Consumer Acknowledgement

The delivery guarantees you get versus the ones you assume. Prefetch, unacked growth, and where message loss genuinely originates.

MODULE 05

Memory, Disk & Flow Control

Watermarks, paging, disk free-space limits, and credit-based flow control — reading the signals before an alarm fires.

MODULE 06

High Availability & Disaster Recovery

Quorum queue member sizing, federation and shovel for cross-region, and the trade-offs each pattern actually imposes.

MODULE 07

RabbitMQ on Kubernetes

Cluster Operator and Topology Operator, PVC sizing, network policy for inter-node traffic, and rolling updates that preserve quorum.

MODULE 08

Security & Multi-Tenancy

TLS for client and inter-node connections, vhost isolation, users and permissions, and least-privilege access design.

MODULE 09

Monitoring & Observability

Prometheus metrics that matter, Grafana dashboards, and alerting on leading indicators rather than on node death.

MODULE 10

Production Troubleshooting Lab

A deliberately broken cluster. Your team diagnoses memory alarms, backlogs, partitions, and under-replicated quorum queues under time pressure.

Scope

What's covered

Administrator Track

For platform and SRE teams operating RabbitMQ. Clustering, partitions, capacity, upgrades, monitoring, and incident diagnosis — the operational surface that on-call actually meets.

Developer Track

For engineers writing producers and consumers. Delivery guarantees, acknowledgement patterns, prefetch, idempotency, error handling, and the client library behavior that causes most application-side incidents.

Kubernetes Track

For teams running RabbitMQ on Kubernetes. Cluster Operator, Topology Operator, storage and network configuration, and the interaction between pod lifecycle and broker state.

Troubleshooting Workshop

An intensive scenario-based workshop. Teams diagnose deliberately broken clusters under time pressure, drawn from incidents we have actually resolved for customers.

Migration Readiness

Focused training for teams moving from classic mirrored queues to quorum queues, or migrating from another broker — covering the semantic differences that break applications.

Custom Curriculum

Where none of the standard tracks fit, we build a curriculum around your specific deployment, versions, and the problems your team is actually hitting.

FAQ

Questions about RabbitMQ training

Make Your Whole Team Dangerous With RabbitMQ

Tell us your team size, what you're running, and where the knowledge gaps are. We'll tailor a curriculum and return a quote within 24 hours.

Get in Touch

Talk to a RabbitMQ Expert

Send us a message and we'll follow up within one business day — 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.