High Throughput, Low Latency
The Lime Brokerage Trading Server (TS) is optimized for both performance and throughput. It is capable of handling just about any order flow a client can generate.
Lime’s TS can be accessed via the FI X protocol. Clients can also use Lime’s binary trading API. Available for both C/C++ and Java, this API offers a clean trading interface for those who do not want to work with FIX. By ensuring all connectivity and protocol-level functionality, the Lime API allows clients to focus on their algorithms rather than worry about low-level details.
High performance traders can monitor their system’s activity, view P&L, and place or cancel orders via Lime’s enterprise web Portal that is fully integrate with Lime’s full-featured trading platform.
Clients have several options for physical connectivity to the Lime Brokerage Trading Server:
Proximity Hosting »
Clients can provide servers to co-locate in our datacenter, which provides 10 Gigabit Ethernet links into our network. This provides clients with a centrally located connection providing quick access to all exchanges from one single location.
Clients can provide servers to co-locate in our space at the exchanges, which provides 10 Gigabit Ethernet links into our network. This is the fastest, most reliable, and most popular choice among our ultra-low latency clients.
Encrypted Internet Access (VPN)
Lime Brokerage has fully-redundant public-facing Internet connections that are peered across network providers for the highest availability of network access. Clients can certify and trade over a secure VPN connection that delivers your orders directly into your configured TS. Lime does not control the full connectivity path over the Internet; those that require less risk of network issues including packet loss, increased latency or routing issues should refer to our other connectivity options below.
Extranet Providers »
Lime works with several providers of high-bandwidth extranet connectivity.
Clients can obtain a T1, T3, or other Point-to-Point circuit directly into our datacenters. This option is reliable, and if clients are on-net and local, fairly inexpensive. A T1 would not be enough for market data, but could be suitable for orders-only traffic, depending on your order rate. A T3 would suffice for most market data instances, unless clients plan on getting entire depth-of-book market data for all symbols across several exchanges.