Search Results for "process"

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. ...

...It mirrors the architecture of traditional LangChain frameworks by providing abstractions for chains, tools, agents, and model integrations while adapting them to Elixir’s concurrency model. This makes it particularly well-suited for building scalable, real-time AI systems that benefit from Elixir’s fault tolerance and lightweight process management. The framework supports multiple providers and includes features such as streaming responses, tool calling, and structured outputs, allowing developers to create complex AI-driven workflows.

...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. However, you can also use Exq standalone. You can also use the Sidekiq UI to view job statuses, as Exq is compatible with the Sidekiq stats format. ...

...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.