Search Results for "so"

Exq is a job processing library compatible with Resque / Sidekiq for the Elixir language. Exq uses Redis as a store for background processing jobs. Exq handles concurrency, job persistence, job retries, reliable queueing and tracking so you don't have to. Jobs are persistent so they would survive across node restarts. You can use multiple Erlang nodes to process from the same pool of jobs. Exq uses a format that is Resque/Sidekiq compatible. This means you can use it to integrate with existing Rails / Django projects that also use a background job that's Resque compatible - typically with little or no changes needed to your existing apps. ...

Horde provides a distributed, fault-tolerant Registry and DynamicSupervisor for Elixir applications, letting you run and manage processes across clustered nodes as if they lived on a single machine. It relies on conflict-free replicated data types (CRDTs) to converge membership and process ownership without a central leader, so cluster topology can change freely as nodes join or leave. With Horde.Registry you register processes globally and look them up anywhere, while Horde.DynamicSupervisor starts and migrates children across nodes, rebalancing as capacity or health changes. Because everything runs under OTP supervision, failures are isolated and recoveries are automatic, even during network partitions or rolling deploys. ...

...Docker images are automatically built by Docker Hub. They are available at Docker Hub. One can generate it using: docker build -t local/poxa. Poxa uses gproc extensively to register websocket connections as channels. So, when a client subscribes for channel 'example-channel', the websocket connection (which is a elixir process) is "tagged" as {pusher, example-channel}. When a pusher event is triggered on the 'example-channel', every websocket matching the tag receives the event.