This should probably be written as two modules, one for the producer and another for the consumer, since they use different types of connection. It's questionable whether PHP-Queue is a healthy layer. There's only a benefit if it's easy to swap out Kafka for another queue provider, so avoid creating any new custom APIs, or if we do, implement these functions for the other queues.
Description
Description
Details
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
[WIP] Kafka backend | wikimedia/fundraising/php-queue | master | +71 -0 | |
New interface for atomic reads | wikimedia/fundraising/php-queue | master | +151 -6 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | None | T117466 Q3 GOALS! (January-March) Keep at top of Q3 column | |||
Resolved | None | T108229 [Epic] SPOF: Replace ActiveMQ donation queues with a more robust software stack | |||
Invalid | awight | T131269 Write PHP-Queue module for new backend |
Event Timeline
Comment Actions
Change 284977 had a related patch set uploaded (by Awight):
[WIP] Playing with the FIFO API