Popularity
5.6
Stable
Activity
0.0
Stable
46
2
23
Monthly Downloads: 4
Programming language: Elixir
License: MIT License
Tags:
Framework Components
Latest version: v0.0.1
phoenix_pubsub_rabbitmq alternatives and similar packages
Based on the "Framework Components" category.
Alternatively, view phoenix_pubsub_rabbitmq 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 -
trailing_format_plug
An elixir plug to support legacy APIs that use a rails-like trailing format: http://api.dev/resources.json -
plug_canonical_host
PlugCanonicalHost ensures that all requests are served by a single canonical host.
WorkOS - The modern identity platform for B2B SaaS
The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Promo
workos.com
Do you think we are missing an alternative of phoenix_pubsub_rabbitmq or a related project?
README
Phoenix Pubsub - RabbitMQ Adapter
RabbitMQ adapter for the Phoenix framework PubSub layer.
Usage
Add phoenix_pubsub_rabbitmq
as a dependency in your mix.exs
file.
def deps do
[{:phoenix_pubsub_rabbitmq, "0.0.1"}]
end
You should also update your application list to include :phoenix_pubsub_rabbitmq
:
def application do
[applications: [:phoenix_pubsub_rabbitmq]]
end
Edit your Phoenix application Endpoint configuration:
config :my_app, MyApp.Endpoint,
...
pubsub: [name: MyApp.PubSub,
adapter: Phoenix.PubSub.RabbitMQ,
options: [host: "localhost"]
The following options are supported:
* `host` - The hostname of the broker (defaults to \"localhost\");
* `port` - The port the broker is listening on (defaults to `5672`);
* `username` - The name of a user registered with the broker (defaults to \"guest\");
* `password` - The password of user (defaults to \"guest\");
* `virtual_host` - The name of a virtual host in the broker (defaults to \"/\");
* `heartbeat` - The connection hearbeat interval in seconds (defaults to `0` - turned off);
* `connection_timeout` - The connection timeout in milliseconds (defaults to `infinity`);
* `pool_size` - Number of active connections to the broker
Notes
- An Exchange is declared with the name of the Phoenix PubSub server (example: MyApp.PubSub)
- When subscribing to a topic:
- a Queue with a server assigned name is declared;
- the Queue is bound to the Exchange using the
topic
as routing key; - a consumer process is started. The consumer will ack each message in the Queue as it sends the payload to the subscriber pid;
- Can be used when distributed Erlang is not an option (like when deploying to Heroku); when RabbitMQ is already a dependency (instead of Redis);
- Uses RabbitMQ routing mechanism, delivering a message directly to a consumer process