In this article we'll explain you how the number of routes are being calculated within the Alumio iPaaS
A route connects an incoming and an outgoing connection.
Incoming connection: Any data that is read from any external source to the Alumio environment. Example, Data from ERP system.
Outgoing connection: Any data that is sent from the Alumio environment to an external endpoint. Example, Data to an eCommerce platform.
Connections in Alumio follow the following rules that are driven by the Actors that form the connection,
Incoming to Routes connection:
From the Incoming to the Route the connection is One to Many. That is many Routes can Read or Fetch the data from a single Incoming data connection.
Routes to Outgoing connection:
From the Routes to the Outgoing, it is a One to One connection. A route can only push the data to one destination Outgoing connection.
Outgoing Configuration (special case):
The outgoing configuration can be reused, this implies that Multiple Routes can Push the data to a common Outgoing configuration.
So if you have Incoming A, Incoming B, Outgoing A, Outgoing B the following connections can be made:
- Incoming A -> Route A -> Outgoing A
- Incoming B -> Route B -> Outgoing B
- Incoming B -> Route C -> Outgoing B
These are three routes and also three connections. But the total number of data Connections (Conn) is five:
- Incoming A [Conn-1]: Connection from the external source A to Alumio.
- Outgoing A (from Route A) [Conn-2]: Incoming data A connection to the external endpoint A passing through the Route A.
- Incoming B [Conn-3]: Connection from the external source B to Alumio.
- Outgoing B (from Route B) [Conn-4]: Incoming data B connection to the external endpoint B passing through the Route B.
- Outgoing B (from Route C) [Conn-5]: Incoming data B connection to the external endpoint B passing through the Route C.
The way to calculate this is the "number of incoming connections" + "number of routes" (2+3).
|Incoming Connectionsflow||Outgoing Connections|