Ringbahn v0.1.0 Ringbahn
Main Supervision tree populates the worker structure and launches it.
Every worker can contain multiple routes.
Each server
worker has their own unique ref
and working under the same supervisor.
Every server
worker fires up Ringbahn.Server instance with different ports
and every server
has its own route registry
worker which is basically managing an ETS table.
Ports are dynamically generated with the worker_count
in the config.
Every Ringbahn.Server
instance handles approx ~16500 simultaneous conns.
From the concurrency point of view mongrel2 do not go even there…
Example worker structure is like this:
children = [ worker(Cachex, [:route_registry_0], worker(Cachex, [:route_registry_1],
… more ETS table workers …
worker(Ringbahn.Server, [
[:"/banner", [recv_ident: "blabla1", recv_port: 10371,
recv_spec: "tcp://127.0.0.1",
send_ident: "blabla1", send_port: 10370,
send_spec: "tcp://127.0.0.1", port: 4001]
...,
...,
], id: :server_uuid1),
worker(Ringbahn.Server, [
[:"/banner", [recv_ident: "blabla2", recv_port: 10371,
recv_spec: "tcp://127.0.0.1",
send_ident: "bblabla2", send_port: 10370,
send_spec: "tcp://127.0.0.1", port: 4002],
...,
...,
], id: :server_uuid2)
]
Summary
Functions
Called when an application is started
Functions
Called when an application is started.
This function is called when an the application is started using
Application.start/2
(and functions on top of that, such as
Application.ensure_started/2
). This function should start the top-level
process of the application (which should be the top supervisor of the
application’s supervision tree if the application follows the OTP design
principles around supervision).
start_type
defines how the application is started:
:normal
- used if the startup is a normal startup or if the application is distributed and is started on the current node because of a failover from another mode and the application specification key:start_phases
is:undefined
.{:takeover, node}
- used if the application is distributed and is started on the current node because of a failover on the nodenode
.{:failover, node}
- used if the application is distributed and is started on the current node because of a failover on nodenode
, and the application specification key:start_phases
is not:undefined
.
start_args
are the arguments passed to the application in the :mod
specification key (e.g., mod: {MyApp, [:my_args]}
).
This function should either return {:ok, pid}
or {:ok, pid, state}
if
startup is successful. pid
should be the pid of the top supervisor. state
can be an arbitrary term, and if omitted will default to []
; if the
application is later stopped, state
is passed to the stop/1
callback (see
the documentation for the stop/2
callback for more information).
use Application
provides no default implementation for the start/2
callback.
Callback implementation for Application.start/2
.