ratx alternatives and similar packages
Based on the "Miscellaneous" category.
Alternatively, view ratx alternatives based on common mentions on social networks and blogs.
-
-
-
ex_rated
ExRated, the Elixir OTP GenServer with the naughty name that allows you to rate-limit calls to any service that requires it. -
-
ecto_autoslug_field
Automatically create slugs for Ecto schemas. -
gen_task
Generic Task behavior that helps encapsulate errors and recover from them in classic GenStage workers. -
exprint
A printf / sprintf library for Elixir. It works as a wrapper for :io.format. -
countriex
All sorts of useful information about every country. A pure elixir port of the ruby Countries gem -
Jisho-Elixir
A Japanese dictionary API; a wrapper around Jisho's API (http://jisho.org) -
egaugex
A simple egauge parser to retrieve and parse data from egauge devices -
presentex
Elixir -> HTML/JavaScript based presentation framework intended for showing Elixir code -
mixstar
Elixir Mix task to starring GitHub repository with `mix deps.get`ting dependent library -
Elixir and Phoenix Application Security Platform
Do you think we are missing an alternative of ratx or a related project?
|
Learn Elixir in as little as 12 Weeks
sponsored
learn-elixir.dev
|
Popular Comparisons
|
Access the most powerful time series database as a service
sponsored
www.influxdata.com
|
README
Ratx
The Ratx Erlang application provides overload protection for Erlang systems. It provides queueing facilities for tasks to be executed so their concurrency can be limited on a running system.
Inspiration
Ratx owes its inspiration to Ulf Wigers jobs framework and
Jesper Louis Andersen safetyvalve, but it is a different
implementation and a different approach as well.
The main difference and goal is to try to eliminate the one gen_server
process to handle all requests. And, the same as safetyvalve to
have one process per queue, which can be supervised(and restarted,
if something go wrong).
ets:update_counter/3 seems the best options and natural to try, and
heavily used in production for such use cases with good effort.
Due to this change, the queue process should only handle all done-s,
and dropping of entries in a queue after timeout. If queue is full, no
messages or calls will be sent to a queue process, that is a protection
for a process on big birsts.
Using
Example of using
ratx:start_link(test_queue, [{limit, 10}, {queue, 100}, {queue_timeout, 1000}]),
Action = fun(I, Time) -> io:format("~p..", [I]), timer:sleep(Time) end,
[spawn(fun() -> ratx:run(test_queue, fun() -> Action(I, 40) end) end) || I <- lists:seq(1, 30)], ok.