elixir-boilerplate
exq
| elixir-boilerplate | exq | |
|---|---|---|
| 3 | 4 | |
| 1,101 | 1,478 | |
| 2.3% | - | |
| 8.8 | 3.8 | |
| 10 days ago | 3 months ago | |
| Elixir | Elixir | |
| BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
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.
elixir-boilerplate
-
Complete, Production-Ready Phoenix Reference Applications
Elixir Boilerplate
-
Unlock/Uninstall A Dependency
Here’s an extra tip to keep you mix.lock clean, add this to your linting rules so it gets validated automatically! It is one of the many CI checks we have for our Elixir projects at Mirego. We actually open-sourced our boilerplate project/template a few months ago if ever you are curious :
-
Is it a good idea to switch from go micro-services to elixir/pheonix ?
We do have this awesome community created template & I use it for all my projects even non graphql projects; it saves about 1-3 days of setup and configuration. https://github.com/mirego/elixir-boilerplate
exq
-
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.
What are some alternatives?
phoenix_container_example - Production-quality example for Elixir/Phoenix building, testing, and running in containers
oban - 💎 Robust job processing in Elixir, backed by modern PostgreSQL and SQLite3
filtrex - A library for performing and validating complex filters from a client (e.g. smart filters)
verk - A job processing system that just verks! 🧛
kandesk - Simple Kanban application written in elixir using phoenix liveview
broadway - Concurrent and multi-stage data ingestion and data processing with Elixir
absinthe_plug - Plug support for Absinthe, the GraphQL toolkit for Elixir
toniq
terminator - 🛡 Modern elixir ACL/ABAC library for managing granular user abilities and permissions
amqp - Idiomatic Elixir client for RabbitMQ
WebSockex - An Elixir Websocket Client
honeydew - Job Queue for Elixir. Clustered or Local. Straight BEAM. Optional Ecto. 💪🍈