exq
Job processing library for Elixir - compatible with Resque / Sidekiq (by akira)
aws-elixir
AWS clients for Elixir (by aws-beam)
Our great sponsors
exq | aws-elixir | |
---|---|---|
4 | 2 | |
1,475 | 513 | |
- | 2.3% | |
3.8 | 9.2 | |
2 months ago | 8 days ago | |
Elixir | Elixir | |
Apache License 2.0 | Apache License 2.0 |
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.
aws-elixir
Posts with mentions or reviews of aws-elixir.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-11-15.
-
Complete, Production-Ready Phoenix Reference Applications
AWS: I don't have a definitive answer for you on AWS. I've used ex_aws a good bit, and it's reasonably solid. aws-elixir also seems to be actively maintained.
- Official SDK for Elixir
What are some alternatives?
When comparing exq and aws-elixir you can also consider the following projects:
oban - 💎 Robust job processing in Elixir, backed by modern PostgreSQL and SQLite3
ex_aws - A flexible, easy to use set of clients AWS APIs for Elixir
verk - A job processing system that just verks! 🧛
filtrex - A library for performing and validating complex filters from a client (e.g. smart filters)
broadway - Concurrent and multi-stage data ingestion and data processing with Elixir
libcluster - Automatic cluster formation/healing for Elixir applications
toniq
amqp - Idiomatic Elixir client for RabbitMQ
phoenix-apps
honeydew - Job Queue for Elixir. Clustered or Local. Straight BEAM. Optional Ecto. 💪🍈
pow - Zero-configuration Rack server for Mac OS X