Cloud is not automatically cheaper than colocation. For a broker or prop firm, the useful question is which workload benefits from physical proximity, and which benefits more from elastic capacity, managed services or easier recovery.
These are different operating models, not opposing answers to a single architecture question. A trading stack can use both, provided the network paths, failure boundaries and ownership are explicit. Start by measuring the service that matters, rather than comparing a cloud instance with a rack on a price sheet.
Measure the path, not the platform label
Colocation means placing equipment in a data centre used by an exchange or liquidity venue, then connecting through a cross-connect or other approved network. It can reduce the physical distance between a broker's gateway and the venue. It does not guarantee a fast order acknowledgement: exchange processing, risk checks, switches, session handling and the return path all contribute.
Cloud regions offer a different set of controls. Teams can provision compute quickly, automate deployment and spread services across availability zones. But a cloud region is not necessarily inside an exchange data centre.
A private circuit may improve predictability, while public internet routing can change. A managed cloud connection also does not remove the need to test the complete path to each venue.
Define timestamps at each boundary: strategy decision, risk acceptance, gateway send, venue receipt where available, acknowledgement receipt and client update. Synchronise clocks with PTP where supported, record the clock source and monitor offset. Compare p50, p99 and p99.9, plus packet loss and reconnect behaviour. A mean latency figure hides the tail that generates complaints and operational incidents.
Make sure the comparison uses the same protocol, message size, market session and load. Report gateway-to-venue network RTT separately from application order-to-ack time. If the data comes from different timestamping points, it is not a like-for-like benchmark.
Use typical ranges as a first filter
The following are typical market ranges for network RTT, not service guarantees. Actual results vary with facility, carrier, route, equipment and venue. They describe network paths only, not the full time to validate, process and acknowledge an order.
| Deployment pattern | Typical market RTT range | Typical variability | Good initial fit |
|---|---|---|---|
| Cross-connect within the venue facility | 10-100 microseconds | Low, if the path and equipment are controlled | Latency-sensitive gateways and market-data capture |
| Private network within the same metro area | 0.2-2 milliseconds | Low to moderate, depending on carrier and route | Risk services and connected broker components |
| Cloud region to an external venue in the same metro | 1-5 milliseconds | Moderate; test the chosen connection and zone | Non-critical execution services and regional systems |
| Inter-region cloud path | 20-80 milliseconds | Moderate to high, depending on distance and routing | Recovery, reporting and asynchronous replication |
Use the ranges to decide what to test, not to approve a design. Measure at least several hours of normal traffic and a representative busy period.
Include bursts, reconnects and failover. For execution paths, capture packet-level or hardware timestamps where available; application logs alone can add scheduling and buffering noise.
Cost comparisons need the same discipline. Typical market quotes can put a small colocation footprint in the low thousands of US dollars per month, while a private cage, multiple cross-connects and diverse circuits can move into five figures. A steady cloud environment can also run from a few thousand dollars to tens of thousands monthly, depending on instance size, redundancy, storage, licences and network transfer.
These are planning ranges, not quotes. Include installation, remote hands, power, circuit commitments, support, egress and engineering time.
Place workloads by their constraints
Split the stack by the consequence of delay, the required control over hardware, and the value of elastic capacity. A simple first pass is:
- Venue-facing gateways: Put the most latency-sensitive sessions near the venue when measured RTT, jitter or route control has a material effect on the trading strategy. Keep session ownership and sequence recovery unambiguous.
- Market-data capture and normalisation: Co-locate capture where packet loss, burst handling or feed latency requires it. Replicate normalised data to cloud storage for analytics and replay, rather than sending every consumer through one constrained link.
- Pre-trade risk: Keep a synchronous risk decision on a path with a tested latency budget and a defined failure action. A remote dependency that adds several milliseconds or fails closed can change order handling during a busy market.
- Research, back-testing and batch jobs: Use cloud capacity when jobs can be queued, scaled and stopped. Put limits on instance families, storage retention and data egress. Elastic compute is useful only if idle capacity is actually released.
- Client APIs, reporting and internal tools: These often suit cloud deployment, subject to data residency, access controls and service-level requirements. Separate them from the critical execution failure domain.
Keep the critical path short and observable. If an order travels from a colocated gateway to a cloud risk service and back, the network hop is now part of the order path. Measure it under load and during route changes. If the control can run locally with synchronised limits and safe state handling, compare that design too.
A hybrid design adds boundaries to operate. Define which system owns order state, what happens when replication is delayed, and which side may accept new orders after a partition. Use fencing tokens or another explicit ownership mechanism to prevent two gateways from sending the same session's orders. For more coverage of the infrastructure choices behind trading platforms, see Trading Technology's infrastructure reporting.
Compare operating cost and failure modes
Build a three-year cost model for each deployment, using the same traffic profile and availability target. For colocation, include rack or cabinet charges, power, cross-connects, diverse circuits, hardware refresh, spares, remote hands and travel. Add the cost of maintaining staff who can diagnose a switch, NIC or cable fault outside local business hours.
For cloud, include compute at normal and peak load, reserved capacity, storage, snapshots, logging, support, private connectivity and data transfer. A recovery environment that is kept warm costs more than one that is provisioned on demand, but an on-demand build can take too long or fail during a regional incident. Test the recovery time instead of assuming that infrastructure-as-code makes it immediate.
Availability-zone redundancy is not the same as regional disaster recovery. A deployment spread across zones can still share a region, control plane or external network dependency.
Colocation sites can share a carrier, venue gateway, power utility or operational team. Draw those dependencies on the service diagram and test at least one failure in each relevant category.
Agree service objectives before moving a workload. For example, an execution service might have a 99.95% monthly availability target, with a recovery time objective of minutes and a recovery point objective of zero lost accepted orders. Those figures are design inputs, not industry guarantees. A research service may tolerate a much longer recovery time and some lost intermediate work.
Track unit costs alongside service measures: cost per million market-data messages, per active client session, or per million orders processed. Review p99 latency, dropped packets, rejected orders, queue depth and failover time on the same dashboard. A cheaper deployment that breaches the latency budget at peak load is not an optimisation.
Prove the design before shifting traffic
Run a controlled comparison with the same software build and configuration in each location. Send production-shaped traffic through test sessions or a replay harness, including burst sizes, message ordering and reconnect patterns. Test the path from the point where the application creates a message to the point where it receives the acknowledgement.
Record the baseline, the expected gain and the rollback trigger. Change one variable at a time: network route, host type, zone, kernel setting or application placement.
Keep a small canary cohort where possible. Do not move all sessions together if session migration risks sequence gaps, duplicated orders or a large client impact.
Before cutover, rehearse loss of the primary link, a host restart, a cloud-zone failure and a venue disconnect. Confirm alert delivery, escalation ownership and the procedure for reconciling order state.
Check that monitoring still works during the failure being tested. An alert routed through the component that has just failed is not a useful control.
Revisit the placement decision after material changes to venue connectivity, traffic volume, strategy requirements or cloud pricing. Keep the measurements and assumptions with the architecture record. For further platform and provider coverage, read Trading Technology.
Stop doing these things:
- Stop choosing a platform from a headline latency or compute price.
- Stop treating cloud-region RTT as equivalent to a venue cross-connect.
- Stop calling a design resilient before testing its shared dependencies.
- Stop moving critical traffic without a measured rollback trigger.
Frequently Asked Questions
Is colocation always faster than cloud for trading?
No. A cross-connect in a venue facility can have very low network RTT, but application processing and the return path still matter. Measure the full order path and its p99 behaviour against the cloud connection being considered.
Can a broker run trading infrastructure in both colocation and cloud?
Yes. A common split puts latency-sensitive gateways or market-data capture near venues, with research, reporting and recovery services in cloud. The design needs clear ownership of order state and tested behaviour during network partitions.
What should a trading team benchmark before migrating to cloud?
Measure gateway-to-venue RTT, application order-to-ack latency, jitter, packet loss and performance during bursts. Also test reconnects and failover, then compare total monthly cost including data transfer, private connectivity, storage and support.
Platforms · Software · Providers · Markets