RMQ (.6k)

Tied exclusively to Redis, which might not suit teams using other storage backends or needing features beyond Redis's capabilities, such as built-in message brokering or advanced persistence options.

Requires careful handling of background errors via error channels, and if not managed properly, can lead to data loss or double deliveries, as admitted in the README's warnings about cleanup and acknowledgment retries.

Compared to established message queues like RabbitMQ or Kafka, rmq has a smaller community and fewer third-party integrations, which could affect long-term support, tooling, and documentation updates.

The README explicitly warns that switching between single Redis and Redis cluster connections is unsafe and can lead to data loss, indicating potential migration challenges and vendor lock-in to specific Redis setups.