Each AWTS environment is typically standalone and independent, operating as a self-contained cluster of running modules; self-hosted on your own infrastructure. However the Mux module supports an upstreaming configuration that connects to a remote AWTS environment to access its services and/or data.

This can be used for scenarios where a powerful central cluster hosts all the market data, and each pod/trader then runs a local AWTS environment with only the specific local services they need; e.g. book, results, runner - and any new/proprietary data sources still being evaluated.

It can also be used to integrate 3rd party remotely-hosted data sets if you so wish.

In this way the heavy resource requirements of maintaining large data sets can be centralised for cost efficiency - whilst simultaneously allowing each team to operate independently and privately (!) from each other.

Setting up the central/source environment

See the Mux documentation on how to enable sharing data/services with downstream environments.

Setting up a team/local environment

Configuring a local environment to upstream to a remote central environment is a simple one-line additional parameter to Mux.

Just set the upstream configuration value (or AW_UPSTREAM env var) to the DSN of the remote AWTS environment; e.g. [email protected]:443. Multiple values should be comma separated.

All available remote services are now transparently included in your local environment, as if they were actually local.

The CLI command awts mux status includes detail on what services are available, including which are local and which are imported.