A Python asyncio-based client for RabbitMQ Streams
The RabbitMQ stream plug-in is required. See the documentation for enabling it.
- Installation
- Examples
- Client Codecs
- Publishing messages
- Sub-Entry Batching and Compression
- Deduplication
- Consuming messages
- Super Streams
- Single Active Consumer
- Connecting with SSL
- Sasl Mechanisms
- Managing disconnections
- Load Balancer
- Client Performances
- Build and Test
- Project Notes
The RabbitMQ stream plug-in is required. See the documentation for enabling it.
The client is distributed via PIP:
pip install rstreamHere you can find different examples.
Before start using the client is important to read this section. The client supports two codecs to store the messages to the server:
AMQP 1.0Binary
By default you should use AMQP 1.0 codec:
amqp_message = AMQPMessage(
body=bytes("hello: {}".format(i), "utf-8"),
)You need to use the AMQP 1.0 codec to exchange messages with other stream clients like
Java, .NET, Rust, Go or if you want to use the AMQP 0.9.1 clients.
You can use the Binary version if you need to exchange messages from Python to Python.
Note: The messages stored in Binary are not compatible with the other clients and with AMQP 0.9.1 clients.
Once the messages are stored to the server, you can't change them.
Read also the Client Performances section
You can publish messages with four different methods:
send: asynchronous, messages are automatically buffered internally and sent at once after a timeout expires.send_batch: synchronous, the user buffers the messages and sends them. This is the fastest publishing method.send_wait: synchronous, the caller wait till the message is confirmed. This is the slowest publishing method.send_sub_entry: asynchronous. See Sub-entry batching and compression.
On the examples directory you can find diffent way to send the messages:
- producer using send
- producer using send_wait
- producer using send_batch
- producer using sub_entry_batch
The Send method takes as parameter an handle function that will be called asynchronously when the message sent will be notified from the server to have been published.
Example:
With send_wait instead will wait until the confirmation from the server is received.
RabbitMQ Stream provides a special mode to publish, store, and dispatch messages: sub-entry batching. This mode increases throughput at the cost of increased latency and potential duplicated messages even when deduplication is enabled. It also allows using compression to reduce bandwidth and storage if messages are reasonably similar, at the cost of increasing CPU usage on the client side.
Sub-entry batching consists in squeezing several messages – a batch – in the slot that is usually used for one message. This means outbound messages are not only batched in publishing frames, but in sub-entries as well.
# sending with compression
await producer.send_sub_entry(
STREAM, compression_type=CompressionType.Gzip, sub_entry_messages=messages
)Full example producer using sub-entry batch
Consumer side is automatic, so no need configurations.
The client is shipped with No Compression (CompressionType.No) and Gzip Compression (CompressionType.Gzip) the other compressions (Snappy, Lz4, Zstd) can be used implementing the ICompressionCodec class.
RabbitMQ Stream can detect and filter out duplicated messages, based on 2 client-side elements: the producer name and the message publishing ID. All the producer methods to send messages (send, send_batch, send_wait) takes a publisher_name parameter while the message publishing id can be set in the AMQP message.
Example:
See consumer examples for basic consumer and consumers with different offsets.
RabbitMQ Streams provides server-side offset tracking for consumers. This features allows a consuming application to restart consuming where it left off in a previous run. You can use the store_offset (to store an offset in the server) and query_offset (to query it) methods of the consumer class like in this example:
A super stream is a logical stream made of individual, regular streams. It is a way to scale out publishing and consuming with RabbitMQ Streams: a large logical stream is divided into partition streams, splitting up the storage and the traffic on several cluster nodes.
See the blog post for more info.
You can use superstream_producer and superstream_consumer classes which internally uses producers and consumers to operate on the componsing streams.
See the Super Stream example
Single active consumer provides exclusive consumption and consumption continuity on a stream.
See the blog post for more info.
See examples in:
See the single active consumer example
Filtering is a new streaming feature enabled from RabbitMQ 3.13 based on Bloom filter. RabbitMQ Stream provides a server-side filtering feature that avoids reading all the messages of a stream and filtering only on the client side. This helps to save network bandwidth when a consuming application needs only a subset of messages.
https://rabbitmq.github.io/rabbitmq-stream-java-client/stable/htmlsingle/#filtering
See the filtering examples
You can enable ssl/tls. See example here: tls example
You can use the following sasl mechanisms:
- PLAIN
- EXTERNAL
The client uses PLAIN mechanism by default.
The EXTERNAL mechanism is used to authenticate a user based on a certificate presented by the client.
Example:
ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)
# put the root certificate of the ca
ssl_context.load_verify_locations("certs/ca_certificate.pem")
ssl_context.load_cert_chain(
"certs/client_HOSTNAME_certificate.pem",
"certs/client_HOSTNAME_key.pem",
)
async with Producer(
"HOSTNAME",
username="not_important",
password="not_important",
port=5551,
ssl_context=ssl_context,
sasl_configuration_mechanism=SlasMechanism.MechanismExternal ## <--- here EXTERNAL configurationThe plugin rabbitmq_auth_mechanism_ssl needs to be enabled on the server side, and ssl_options.fail_if_no_peer_cert needs to set to true
config example:
auth_mechanisms.3 = PLAIN
auth_mechanisms.2 = AMQPLAIN
auth_mechanisms.1 = EXTERNAL
ssl_options.cacertfile = certs/ca_certificate.pem
ssl_options.certfile = certs/server_certificate.pem
ssl_options.keyfile = certs/server_key.pem
listeners.ssl.default = 5671
stream.listeners.ssl.default = 5551
ssl_options.verify = verify_peer
ssl_options.fail_if_no_peer_cert = true
The client supports auto-reconnect just for Producer and SuperstreamProducer at the moment.
When the TCP connection is disconnected unexpectedly, the Producer and the SuperstreamProducer will try to automatically reconnect while in case of the Consumer/SuperstreamConsumer the client raises an event that needs to be managed:
async def on_connection_closed(disconnection_info: DisconnectionErrorInfo) -> None:
print(
"connection has been closed from stream: "
+ str(disconnection_info.streams)
+ " for reason: "
+ str(disconnection_info.reason)
)
consumer = Consumer(
..
on_close_handler=on_connection_closed,
)When the on_close_handler event is raised, you can close the Consumers by doing a correct clean-up or try reconnecting using the reconnect stream.
Example:
async def on_connection_closed(disconnection_info: OnClosedErrorInfo) -> None:
print(
"connection has been closed from stream: "
+ str(disconnection_info.streams)
+ " for reason: "
+ str(disconnection_info.reason)
)
for stream in disconnection_info.streams:
print("reconnecting stream: " + stream)
await producer.reconnect_stream(stream)Please take a look at the complete reliable client example here
If the streams topology changes (ex:Stream deleted or add/remove follower), The server removes the producers and consumers linked to the stream and then it sends the Metadata update event. the behaviour is similar to what we have for disconnections. In case of the Producer/Superstream Producer the Client will try to automatically reconnect while the Consumer needs to manage the on_close_handler event.
Please take a look at the complete reliable client example here
In order to handle load balancers, you can use the load_balancer_mode parameter for producers and consumers. This will always attempt to create a connection via the load balancer, discarding connections that are inappropriate for the client type.
Producers must connect to the leader node, while consumers can connect to any, prioritizing replicas if available.
The RabbitMQ Stream queues can handle high throughput. Currently, the client cannot reach the maximum throughput the server can handle.
We found some bottlenecks; one of them is the current AMQP 1.0 marshal and unmarshal message format.
This one:
for i in range(1_000_000):
amqp_message = AMQPMessage(
body=bytes("hello: {}".format(i), "utf-8"),
)
# send is asynchronous
await producer.send(stream=STREAM, message=amqp_message)is more or less ~55% slower than:
for i in range(1_000_000):
# send is asynchronous
await producer.send(stream=STREAM, message=b"hello")You can use the batch_send to test the performances.
We are evaluating rewriting the AMQP 1.0 codec optimized for the stream use case.
-
Linux Ubuntu 4 cores and 8 GB of Ram
-
RabbitMQ installed to the server
-
Send batch with AMQP 1.0 codec:
$ python3 docs/examples/basic_producers/producer_send_batch.py
Sent 1.000.000 messages in 9.3218 seconds. 107.275,5970 messages per second- Send batch with binary codec:
$ python3 docs/examples/basic_producers/producer_send_batch_binary.py
Sent 1.000.000 messages in 2.9930 seconds. 334.116,5639 messages per secondTo run the tests, you need to have a running RabbitMQ Stream server. You can use the docker official image.
Run the server with the following command:
docker run -it --rm --name rabbitmq -p 5552:5552 -p 5672:5672 -p 15672:15672 \
-e RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS='-rabbitmq_stream advertised_host localhost' \
rabbitmq:3.12-managementenable the plugin:
docker exec rabbitmq rabbitmq-plugins enable rabbitmq_streamand run the tests:
poetry run pytestThe project is in development and stabilization phase. Features and API are subject to change, but breaking changes will be kept to a minimum.
Any feedback or contribution is welcome
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent