exq
Job processing library for Elixir - compatible with Resque / Sidekiq (by akira)
kafka_consumer
Consumer for Kafka using brod and elixir (production ready) (by anoskov)
Our great sponsors
| exq | kafka_consumer | |
|---|---|---|
| 4 | - | |
| 1,475 | 26 | |
| - | - | |
| 3.8 | 0.0 | |
| 2 months ago | about 4 years ago | |
| Elixir | Elixir | |
| Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
exq
Posts with mentions or reviews of exq.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-16.
-
How to Use Flume in your Elixir Application
Oban, backed by PostgreSQL or SQLite, also provides a queue-based job processing system. Exq, on the other hand, is backed by Redis. It provides features similar to Flume, but without built-in rate limiting and batch processing capabilities.
- Exq is a job processing library compatible with Resque / Sidekiq for Elixir
-
Complete, Production-Ready Phoenix Reference Applications
Enter Oban, which leverages Postgres' notify/listen functionality to provide a durable queue. Oban is solid and doesn't require Redis, which is cool. I end up using this in most projects I work on. If you absolutely need the speed of Redis, Exq is a pretty good option.
-
sidekiq-dry
Job processing libraries compatible with Sidekiq, for example exq, won't deserialise your Dry::Struct arguments. This is most likely an acceptable tradeoff.
kafka_consumer
Posts with mentions or reviews of kafka_consumer.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning kafka_consumer yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
When comparing exq and kafka_consumer you can also consider the following projects:
oban - 💎 Robust job processing in Elixir, backed by modern PostgreSQL and SQLite3
dbus - A dumb message bus for sharing data between microservices in a relatively decoupled mechanism
verk - A job processing system that just verks! 🧛
amqp - Idiomatic Elixir client for RabbitMQ
broadway - Concurrent and multi-stage data ingestion and data processing with Elixir
elixir_nsq - An NSQ client for Elixir and Erlang, written in Elixir.
toniq
honeydew - Job Queue for Elixir. Clustered or Local. Straight BEAM. Optional Ecto. 💪🍈