Below is an overview of the server components in Motionite:
(View as PDF for more detail)
Exchanges and Settlement Systems
At the top of this diagram are shown exchanges and settlement systems which Motionite can connect to. With Feed Servers and Trading Adapters, Motionite can easily be connected to any exchange or data source.
Backend components are not directly accessible from the internet. The reside on servers with private IP addresses.
The OMS components (hub, event store database, bridge), provide all the handling to place, amend and cancel orders. They also flow Order Execution Reports back to the Trading Agent.
Most settlements system need a Trade Feed to close orders. The Trading Monitor component generates trade feeds suitable for settlement systems.
The Trading Agent orchestrates order requests. When an order request is to be placed, the Trading Agent collects all the information required to vet the order request and then passes it to the Vetting component. If the request is approved, then the Trading Agent forwards it to the OMS Hub. The Trading Agent also maintains a full picture of all orders, holdings and balances on an account basis.
Fetch collects, enhances and distributes data. It used to collect data from external sources (eg. start of day from settlement), and generate reports.
MView is the administration and operations component for all of Motionite.
All access to Motionite from the internet are via the frontend components.
The internal components generally communicate with each other using HTTP requests. However the Proxy component(s) communicate between themselves and with Feed Servers and Trading Agent using Motionite’s Interlink communications protocol. Interlink is highly optimised for streaming data.