RabbitMQ Messaging & Async Systems · 课时

事务与发布者确认

比较 AMQP 事务与更轻量的发布者确认机制，并了解每种机制何时能保证消息已被代理安全接收。

事务与发布者确认 是 CoddyKit 上的免费 RabbitMQ Messaging & Async Systems 课时。这是第 4 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 RabbitMQ Messaging & Async Systems 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 RabbitMQ Messaging & Async Systems 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Reliability Needs More Than Persistence

Persistent messages survive a broker restart, but persistence alone does not tell the publisher whether the broker actually received and stored the message.

For end-to-end reliability you need confirmation.

AMQP Transactions

AMQP supports transactions on a channel: you begin a transaction, publish messages, then commit. The broker confirms the whole batch atomically.

Using a Transaction

Enable transaction mode with tx_select, publish, then tx_commit.

channel.tx_select()
channel.basic_publish(exchange='', routing_key='jobs', body='task')
channel.tx_commit()

The Cost of Transactions

Transactions are synchronous and slow. Each commit blocks until the broker responds, often cutting throughput by 200x or more.

They serialize publishing, which kills pipelining.

Publisher Confirms Recap

Publisher confirms are an asynchronous alternative. The broker sends an ack per message (or per batch) once it is safely handled, without blocking the publisher.

Enabling Confirm Mode

Put the channel into confirm mode once; you cannot mix it with transaction mode on the same channel.

channel.confirm_delivery()
channel.basic_publish(exchange='', routing_key='jobs', body='task')

Asynchronous Acks

With confirms you can keep publishing while acks arrive in the background, then match acks to delivery tags. This preserves high throughput.

Handling Nacks

If the broker cannot handle a message it sends a nack. Your code must resend or log it. Nacks are rare but signal internal broker errors.

Choosing Between Them

Transactions: true atomic multi-message commit, but very slow
Confirms: near-equivalent safety with far higher throughput

The RabbitMQ team recommends confirms for almost all cases.

Combine With Persistence

For the strongest guarantee, mark messages persistent and use confirms; the broker only acks a persistent message after it is written to disk.

props = pika.BasicProperties(delivery_mode=2)
channel.basic_publish(exchange='', routing_key='jobs', body='task', properties=props)

Mutually Exclusive Modes

A single channel cannot be in both transaction and confirm mode. Pick one per channel; attempting both raises a channel error.

Quick Check

Test your reliability knowledge.

Recap

Both transactions and publisher confirms tell a publisher the broker accepted a message.

Transactions are atomic but slow; confirms are asynchronous and fast. Combine confirms with persistent messages for the best balance of reliability and performance.

常见问题解答

「事务与发布者确认」课时是免费的吗？

是的 — 「事务与发布者确认」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 RabbitMQ Messaging & Async Systems 课程的其余内容，请升级到 CoddyKit PRO。 RabbitMQ Messaging & Async Systems 课程共包含 4 节课。

「事务与发布者确认」这节课中我会学到什么？

比较 AMQP 事务与更轻量的发布者确认机制，并了解每种机制何时能保证消息已被代理安全接收。你通过在浏览器中直接运行的动手代码来练习 RabbitMQ Messaging & Async Systems，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 RabbitMQ Messaging & Async Systems 需要有经验吗？

无需任何先前经验。CoddyKit 上的 RabbitMQ Messaging & Async Systems 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 4 节课，共 4 节。

「事务与发布者确认」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 RabbitMQ Messaging & Async Systems 课中编写并运行代码吗？

能。每节 RabbitMQ Messaging & Async Systems 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 RabbitMQ Messaging & Async Systems