3.2k sao GitHub và vẫn tăng — celery/kombu là dự án Python mà TopGit đang theo dõi trên nền tảng. Messaging library for Python.
Tóm tắt dựng từ metadata GitHub của chính dự án — chưa có bài review TopGit. Trang sẽ tự động cập nhật khi bài review đầy đủ được xuất bản.
VÌ SAO CHƯA CÓ REVIEW
TopGit viết bài đầy đủ cho repo có nhiều sao nhất và được yêu cầu nhiều nhất. Trang này là snapshot trong thời gian chờ — xem README gốc ở tab READ ME.
The aim of Kombu is to make messaging in Python as easy as possible by
providing an idiomatic high-level interface for the AMQ protocol, and also
provide proven and tested solutions to common messaging problems.
AMQP_ is the Advanced Message Queuing Protocol, an open standard protocol
for message orientation, queuing, routing, reliability and security,
for which the RabbitMQ_ messaging server is the most popular implementation.
Features
Allows application authors to support several message server
solutions by using pluggable transports.
AMQP transport using the py-amqp, or qpid-python libraries.
Virtual transports makes it really easy to add support for non-AMQP
transports. There is already built-in support for Redis,
Amazon SQS, ZooKeeper, SoftLayer MQ, MongoDB, PGMQ and Pyro_.
In-memory transport for unit testing.
Supports automatic encoding, serialization and compression of message
payloads.
Consistent exception handling across transports.
The ability to ensure that an operation is performed by gracefully
handling connection and channel errors.
Several annoyances with amqplib_ has been fixed, like supporting
timeouts and the ability to wait for events on more than one channel.
Projects already using carrot_ can easily be ported by using
a compatibility layer.
For an introduction to AMQP you should read the article Rabbits and warrens,
and the Wikipedia article about AMQP.
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| Client | Type | Direct | Topic | Fanout | Priority | TTL |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| amqp | Native | Yes | Yes | Yes | Yes [#f3]_ | Yes [#f4]_ |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| qpid | Native | Yes | Yes | Yes | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| redis | Virtual | Yes | Yes | Yes (PUB/SUB) | Yes | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| mongodb | Virtual | Yes | Yes | Yes | Yes | Yes |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| pgmq | Virtual | Yes | Yes | Yes | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| SQS | Virtual | Yes | Yes [#f1]_ | Yes [#f2]_ | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| zookeeper | Virtual | Yes | Yes [#f1]_ | No | Yes | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| in-memory | Virtual | Yes | Yes [#f1]_ | No | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| SLMQ | Virtual | Yes | Yes [#f1]_ | No | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
| Pyro | Virtual | Yes | Yes [#f1]_ | No | No | No |
+---------------+----------+------------+------------+---------------+--------------+-----------------------+
.. [#f1] Declarations only kept in memory, so exchanges/queues
must be declared by all clients that needs them.
.. [#f2] Fanout is supported via AWS SNS. A notification is sent to SNS, and a copy is set to all subscribed
Amazon SQS queues. Please consult the AWS SNS and SQS pricing pages to see how this will affect your usage
costs. Disabled by default, but can be enabled by using the supports_fanout transport option.
.. [#f3] AMQP Message priority support depends on broker implementation.
.. [#f4] AMQP Message/Queue TTL support depends on broker implementation.
Documentation
Kombu is using Sphinx, and the latest documentation can be found here:
https://kombu.readthedocs.io/
Quick overview
.. code:: python
from kombu import Connection, Exchange, Queue
media_exchange = Exchange('media', 'direct', durable=True)
video_queue = Queue('video', exchange=media_exchange, routing_key='video')
def process_media(body, message):
print(body)
message.ack()
# connections
with Connection('amqp://guest:guest@localhost//') as conn:
# produce
producer = conn.Producer(serializer='json')
producer.publish({'name': '/tmp/lolcat1.avi', 'size': 1301013},
exchange=media_exchange, routing_key='video',
declare=[video_queue])
# the declare above, makes sure the video queue is declared
# so that the messages can be delivered.
# It's a best practice in Kombu to have both publishers and
# consumers declare the queue. You can also declare the
# queue manually using:
# video_queue(conn).declare()
# consume
with conn.Consumer(video_queue, callbacks=[process_media]) as consumer:
# Process messages and handle events on all channels
while True:
conn.drain_events()
# Consume from several queues on the same channel:
video_queue = Queue('video', exchange=media_exchange, key='video')
image_queue = Queue('image', exchange=media_exchange, key='image')
with connection.Consumer([video_queue, image_queue],
callbacks=[process_media]) as consumer:
while True:
connection.drain_events()
Or handle channels manually:
.. code:: python
with connection.channel() as channel:
producer = Producer(channel, ...)
consumer = Consumer(channel)
All objects can be used outside of with statements too,
just remember to close the objects after use:
Exchange and Queue are simply declarations that can be pickled
and used in configuration files etc.
They also support operations, but to do so they need to be bound
to a channel.
Binding exchanges and queues to a connection will make it use
that connections default channel.
::
>>> exchange = Exchange('tasks', 'direct')
>>> connection = Connection()
>>> bound_exchange = exchange(connection)
>>> bound_exchange.delete()
# the original exchange is not affected, and stays unbound.
>>> exchange.delete()
raise NotBoundError: Can't call delete on Exchange not bound to
a channel.
Terminology
There are some concepts you should be familiar with before starting:
* Producers
Producers sends messages to an exchange.
* Exchanges
Messages are sent to exchanges. Exchanges are named and can be
configured to use one of several routing algorithms. The exchange
routes the messages to consumers by matching the routing key in the
message with the routing key the consumer provides when binding to
the exchange.
* Consumers
Consumers declares a queue, binds it to a exchange and receives
messages from it.
* Queues
Queues receive messages sent to exchanges. The queues are declared
by consumers.
* Routing keys
Every message has a routing key. The interpretation of the routing
key depends on the exchange type. There are four default exchange
types defined by the AMQP standard, and vendors can define custom
types (so see your vendors manual for details).
These are the default exchange types defined by AMQP/0.8:
* Direct exchange
Matches if the routing key property of the message and
the `routing_key` attribute of the consumer are identical.
* Fan-out exchange
Always matches, even if the binding does not have a routing
key.
* Topic exchange
Matches the routing key property of the message by a primitive
pattern matching scheme. The message routing key then consists
of words separated by dots (`"."`, like domain names), and
two special characters are available; star (`"*"`) and hash
(`"#"`). The star matches any word, and the hash matches
zero or more words. For example `"*.stock.#"` matches the
routing keys `"usd.stock"` and `"eur.stock.db"` but not
`"stock.nasdaq"`.
Installation
You can install Kombu either via the Python Package Index (PyPI)
or from source.
To install using pip,:
::
$ pip install kombu
To install using easy_install,:
::
$ easy_install kombu
If you have downloaded a source tarball you can install it
by doing the following,:
The maintainers of kombu and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. Learn more.
celery/kombu có 3.2k sao GitHub — tải lại trang để xem số mới nhất, hoặc xem trực tiếp github.com/celery/kombu. TopGit phản chiếu số sao của GitHub nhưng không cam kết đến từng phút.
Commit gần nhất trên celery/kombu là 3 tháng trước (theo timestamp GitHub). Repo có 1.1k fork — một chỉ báo về mức độ quan tâm của cộng đồng.
celery/kombu viết bằng ngôn ngữ gì?
celery/kombu chủ yếu viết bằng Python. Trường "language" của GitHub dựa trên phần lớn byte ở nhánh mặc định.
Cùng nhóm Backend còn repo nào?
celery/kombu thuộc nhóm Backend trên TopGit, cùng 11 topic GitHub. Trang Trending và Topics liệt kê các repo cùng số sao và cùng ngôn ngữ để so sánh.
Đọc thêm về celery/kombu ở đâu?
Trang TopGit này là một snapshot — tab "Readme" hiển thị nguyên văn README của repo (đã bỏ link, giữ ảnh). Repo GitHub ở github.com/celery/kombu là nguồn chính thức.
Vì sao celery/kombu được xếp vào nhóm Backend?
TopGit xếp celery/kombu vào nhóm Backend dựa trên GitHub topics và mô tả của repo (gắn thẻ: "celery", "kombu", "message-queue"). Việc phân loại dựa trên metadata thật của repo, không phải đoán theo cảm tính biên tập.
Đọc đầy đủ README ở tab phía trên.
Muốn nghe thêm một ý kiến về kombu?
Hỏi một AI đọc được trang này — một cú bấm là có ngay nhận định về kombu.