Event Socket Outbound alternatives and similar packages

Based on the "Actors" category.
Alternatively, view Event Socket Outbound alternatives based on common mentions on social networks and blogs.

poolboy

9.8 0.0 Event Socket Outbound VS poolboy

A hunky Erlang worker pool factory
exactor

9.0 0.0 Event Socket Outbound VS exactor

Helpers for simpler implementation of GenServer based processes

InfluxDB - Power Real-Time Data Analytics at Scale

Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

Promo www.influxdata.com

pooler

8.7 5.4 Event Socket Outbound VS pooler

An OTP Process Pool Application
Flowex

8.6 0.0 Event Socket Outbound VS Flowex

Flow-Based Programming framework for Elixir
spawn

7.7 9.7 Event Socket Outbound VS spawn

Spawn - Actor Mesh
alf

7.2 8.4 Event Socket Outbound VS alf

Flow-based Application Layer Framework
sbroker

7.1 0.0 Event Socket Outbound VS sbroker

Sojourn-time based active queue management library
exos

5.9 0.0 Event Socket Outbound VS exos

Exos is a simple Port Wrapper : a GenServer which forwards cast and call to a linked Port.
workex

5.7 0.0 Event Socket Outbound VS workex

Load control in BEAM processes.
ex_lttb

4.0 10.0 Event Socket Outbound VS ex_lttb

An Elixir downsampling library that retains the visual characteristics of your data
poolex

3.9 7.9 Event Socket Outbound VS poolex

The library for managing pools of workers. In short, this is a `poolboy` written in Elixir.
dflow

3.5 0.0 Event Socket Outbound VS dflow

Dalmatiner flow processing library.
pool_ring

1.0 0.0 Event Socket Outbound VS pool_ring

create a pool based on a hash ring
mon_handler

0.5 0.0 Event Socket Outbound VS mon_handler

Elixir GenServer used to monitor a GenEvent event handler
Director

0.2 0.0 Event Socket Outbound VS Director

moved to https://github.com/pouriya/director - Director is a production-ready supervisor and manager for Erlang/Elixir processes that focuses on speed, performance and flexibility.
Load-Balancer

0.1 0.0 Event Socket Outbound VS Load-Balancer

moved to https://github.com/pouriya/lb - Load-Balancer for spreading Erlang/Elixir messages.
SockErl

0.1 0.0 Event Socket Outbound VS SockErl

moved to https://github.com/pouriya/sockerl - Sockerl is an advanced Erlang/Elixir socket framework for TCP protocols and provides fast, useful and easy-to-use API for implementing servers, clients and client connection pools.

Do you think we are missing an alternative of Event Socket Outbound or a related project?

Add another 'Actors' Package

Popular Comparisons

README

Event Socket Outbound

EventSocketOutbound is an Elixir protocol for the FreeSWITCH's Event Socket. This protocol provides support for Outbound method of the Event Socket.

Installation

Add event_socket_outbound to your list of dependencies in mix.exs:

    def deps do
      [{:event_socket_outbound, "~> 0.5.0"}]
    end

Getting started

# In your config/config.exs file
config :event_socket_outbound, EventSocketOutbound.Call.Manager,
  call_mgt_adapter: MySample.Call

where MySample.Call will be a module that implements EventSocketOutbound.CallMgmt behaviour and logic for controlling the call. By default EventSocketOutbound uses EventSocketOutbound.ExampleCallMgmt module which answers the call and play a welcome message.

Usage

Start EventSocketOutbound without options.

>Application.start(:ranch)
:ok
>EventSocketOutbound.start
{:ok, #PID<0.172.0>}

Start EventSocketOutbound with options.

>Application.start(:ranch)
:ok
>EventSocketOutbound.start port: 8090, acceptors: 50
{:ok, #PID<0.174.0>}

Add the child specs to your supervision tree, using EventSocketOutbound.Protocol as protocol. For more info, refer to ranch docs.

child_spec = :ranch.child_spec(ref, :ranch_tcp, %{num_acceptors: acceptors, socket_opts: [{:port, port}]}, EventSocketOutbound.Protocol :ranch)

Copyright and License

EventSocketOutbound source code is licensed under the [MIT License](LICENSE.md).

*Note that all licence references and agreements mentioned in the Event Socket Outbound README section above are relevant to that project's source code only.