​

⚡ Edge-First Architecture

​

🏎️ The Physics of Latency: Why Traditional VPS Bots Fail

​

The VPS Bottleneck (200ms+ slippage)

1. Signal Generation: A TradingView alert fires in London.
2. Network Transit: The alert travels across the Atlantic to your Virginia VPS (~85ms).
3. Execution Delay: The VPS boots a heavy Node/Docker runtime to process the signal (~10ms).
4. Exchange Transit: The order travels from Virginia to Bybit’s API servers in Tokyo or Frankfurt (~110ms).
5. Total Transit Latency: 205ms before the exchange matches your order.

[London Alert] ── (85ms) ──> [Virginia VPS] ── (110ms) ──> [Frankfurt Bybit] = 205ms Latency

​

The Hoox Edge Path (Under 15ms latency)

1. Signal Generation: A TradingView alert fires in London.
2. Edge Ingestion: The alert hits Cloudflare’s nearest London Point of Presence (PoP) in 1.8ms.
3. V8 Isolate Processing: A sandboxed V8 isolate processes and validates the order instantly (<3ms).
4. Smart Placement Routing: The internal service binding transfers compute to the edge node geographically closest to Bybit’s servers (Frankfurt) within 8ms.
5. Total Edge Latency: Under 15ms total network transit time.

[London Alert] ── (1.8ms) ──> [London PoP] ── (8ms Service Binding) ──> [Frankfurt Node] ── (1ms) ──> [Bybit] = 10.8ms Latency

​

🧅 V8 Isolates vs. Traditional VMs / Containers

​

🎯 Smart Placement: Zero-Config Latency Optimizer

"placement": {
  "mode": "smart"
}

​

How Smart Placement Works

1. When you deploy trade-worker, Cloudflare monitors its network dependencies. It notices that trade-worker makes outbound signed HTTPS REST requests to Bybit’s Frankfurt server (api.bybit.com) and writes transaction rows to the d1-worker SQLite database.
2. Instead of running the worker’s CPU compute at the location where the user’s browser or alert hits (e.g. California), Smart Placement automatically shifts the compute isolate to the Cloudflare node physically closest to the Bybit servers (Frankfurt).
3. The V8 engine performs all signature calculations and database writes at the edge gateway node, reducing the final API transit time to under 2 milliseconds.

​

Latency Comparison: Real Numbers

​

⚙️ Hardware-Level Security

• Isolate Protection: Memory leaks, side-channel attacks, and adjacent tenant exploits are prevented at the V8 compiler level. Each tenant’s code runs in a completely separate memory space with zero shared state.
• Microsecond Service Bindings: Communication between workers is processed entirely inside the local V8 runtime, meaning sensitive exchange payloads and API calls never travel over the public internet. This eliminates TLS decryption overhead and packet-sniffing risks.
• No Shared Filesystem: Unlike container-based approaches, V8 isolates have no persistent filesystem access — preventing supply-chain attacks via compromised dependencies writing to disk.

​

Service Binding Architecture

[Public Request] → hoox (gateway:8787)
                    │
        ┌───────────┼───────────────┐
        │           │               │
    [SB:trade]  [SB:d1-worker]  [SB:telegram]
        │           │               │
    trade-worker  d1-worker    telegram-worker
    (port:8789)  (port:8792)   (port:8791)
        │           │
   [Exchange API]  [D1 SQLite]

​

🔗 Next Steps

• Cloudflare Services Explained — Learn how D1 SQLite databases, KV, and Queues fit together on the edge.
• AI Risk Manager — Understand how autonomous risk checks run on global cron schedules.