resin alternatives and similar packages
Based on the "Framework Components" category.
Alternatively, view resin alternatives based on common mentions on social networks and blogs.
-
-
-
-
-
-
-
-
-
-
-
-
dayron
A repository `similar` to Ecto.Repo that maps to an underlying http client, sending requests to an external rest api instead of a database -
-
-
rummage_phoenix
Full Phoenix Support for Rummage. It can be used for searching, sorting and paginating collections in phoenix. -
phoenix_token_auth
Token authentication solution for Phoenix. Useful for APIs for e.g. single page apps. -
-
-
-
access pass
provides a full user authentication experience for an API. Includes login,logout,register,forgot password, forgot username, confirmation email and all that other good stuff. Includes plug for checking for authenticated users and macro for generating the required routes. -
-
Votex
Implements vote / like / follow functionality for Ecto models in Elixir. Inspired from Acts as Votable gem in Ruby on Rails -
plug_canonical_host
PlugCanonicalHost ensures that all requests are served by a single canonical host. -
trailing_format_plug
An elixir plug to support legacy APIs that use a rails-like trailing format: http://api.dev/resources.json -
InfluxDB - Power Real-Time Data Analytics at Scale
Do you think we are missing an alternative of resin or a related project?
Popular Comparisons
README
Resin
A very viscous liquid, will make your Plug-based application sluggish.
Resin is a plug that will add a configurable delay to every request that's passing through it, unless run in production.
This is basically a completely useless plug, unless your PM/boss/whoever insists that your project is too snappy and wants a more "realistic" demo...
Usage
Given the example in [SimpleApp](examples/simple_app/lib/simple_app.ex):
defmodule SimpleApp do
use Plug.Router
use Resin, enterpriseyness: 1_000
plug :match
plug :dispatch
get "/hello" do
conn
|> send_resp(200, "That sure was slo^H^H^Henterprisey, right?\n")
end
match _ do
conn
|> send_resp(404, "nope")
end
def start do
Plug.Adapters.Cowboy.http SimpleApp, [], port: 4000
end
def stop do
Plug.Adapters.Cowboy.shutdown SimpleApp.HTTP
end
end
Then just run SimpleApp.start in your iex and start cURLing
localhost:4000/hello and feel the enterpriseyness:
$ time curl localhost:4000
nope
curl localhost:4000 0.01s user 0.01s system 1% cpu 1.057 total
Are your project managers complaining that your Elixir web application is unrealistically fast, and that your demos does not reflect actual production performance?
Just pour some resin into its Plug.Router and it will be noticably
slower more enterprisey!
use Resin
Did your management start believing you are faking this delay because all requests take exactly the same amount of time to complete?
Use a range for the enterpriseyness option, to make the
enterpriseyness level differ between requests, making the "performance
forecast" (thanks for that term, @DevL).
use Resin, enterpriseyness: 1_000 .. 3_000
This will make add a random number between 1000 and 3000 milliseconds of enterpriseyness.
Are you looking for a way to have delays in a specific pattern, like having every 4th request take an extra second?
Set your enterpriseyness to an array:
use Resin, enterpriseyness: [0, 0, 0, 1_000]
It even works with an array of ranges:
use Resin, enterpriseyness: [100 .. 200, 300 .. 400, 0 .. 1_000]
...or combinations:
use Resin, enterpriseyness: [0, 0, 100, 100 .. 200]
Worried that you will forget to clear out the resin before you ship to production?
No worries! Resin will detect that it's running in a production environment, and just edit itself right out of your AST.
Are you serious?
Not really.
But why?
I was bored and I wanted to build a plug.
Why the name?
Resin is a very viscous liquid.
Also, tar would just be confusing, and acts_as_enterprisey is
already an existing thing for Rails, but it would also be too obvious.
Isn't this just acts_as_enterprisey as a plug?
Yes. Cred goes out to @airblade for inspiration.