Order History Storage: Schema, Optimization, Pipeline

After a year of active trading, you notice: queries to order history slow down, full table scans take minutes, and generating a P&L report for the last quarter is painful. We design a storage that solves this problem once and for all. It handles 10,000 events per second and answers analytical queries in milliseconds. This is the foundation for execution quality analysis, backtesting, commission calculation, tax reporting, and trading strategy audits.

How to Choose a Database Schema for Orders?

An order in a trading system is not just a record "buy 1 BTC at 50000". The full model includes several event types. Storing these events separately (Event sourcing) gives full reproducibility: you can always restore the state of any order at any point in time. For time series of orders, TimescaleDB or ClickHouse are optimal.

TimescaleDB is a good choice if you already use PostgreSQL. It automatically partitions tables by time (hypertables), supports continuous aggregates and compression policies. Below is an example schema for an order events table.

CREATE TABLE order_events (
    event_id        UUID DEFAULT gen_random_uuid(),
    event_time      TIMESTAMPTZ NOT NULL,
    order_id        UUID NOT NULL,
    exchange        VARCHAR(32) NOT NULL,
    symbol          VARCHAR(32) NOT NULL,
    event_type      VARCHAR(32) NOT NULL,
    side            VARCHAR(8),
    order_type      VARCHAR(16),
    price           NUMERIC(24, 8),
    quantity        NUMERIC(24, 8),
    filled_qty      NUMERIC(24, 8),
    avg_fill_price  NUMERIC(24, 8),
    commission      NUMERIC(24, 8),
    commission_asset VARCHAR(16),
    client_order_id VARCHAR(64),
    strategy_id     VARCHAR(64),
    metadata        JSONB
);

SELECT create_hypertable('order_events', 'event_time',
    chunk_time_interval => INTERVAL '1 day');

How to Optimize Queries to Order History?

Restoring order state is a frequent operation. Instead of recomputing from events every time, maintain a materialized table orders with the current state. Update this table on each new event via a trigger or application-side logic.

Analytical queries typically aggregate by strategy, instrument, and period. Example P&L query by strategy:

SELECT
    strategy_id,
    symbol,
    SUM(CASE WHEN side = 'BUY' THEN -filled_qty * avg_fill_price ELSE filled_qty * avg_fill_price END) as realized_pnl,
    SUM(total_commission) as total_fees,
    COUNT(*) as order_count
FROM orders
WHERE created_at BETWEEN CURRENT_DATE - INTERVAL '1 year' AND CURRENT_DATE
  AND status = 'FILLED'
GROUP BY strategy_id, symbol
ORDER BY realized_pnl DESC;

TimescaleDB continuous aggregates allow pre-computing these aggregations and updating them incrementally.

Storing Fills Separately

For detailed execution quality analysis, it is critical to store individual fills separately from orders. This allows calculating execution VWAP, comparing with mid-price at execution time (market impact), and analyzing maker/taker ratio by strategy.

Retention Policies and Archiving

Hot data is stored without compression for maximum write and read speed. Older data is compressed. TimescaleDB compression achieves 10–20x size reduction for time series with repeating values. Data older than 2 years can be exported to Parquet files on S3 using pg_parquet or a custom ETL, preserving historical analysis capability via Athena or ClickHouse.

Ingestion Pipeline

High-frequency writes require batching. Instead of INSERT per event, use COPY for bulk inserts — 10–50x faster. Accumulate events in memory (100ms or 1000 events) and write with a single COPY. Unlogged tables for intermediate buffer avoid WAL writes, significantly speeding up inserts. Connection pooling via PgBouncer allows serving thousands of clients.

ALTER TABLE order_events SET (
  timescaledb.compress,
  timescaledb.compress_segmentby = 'exchange, symbol',
  timescaledb.compress_orderby = 'event_time DESC'
);

SELECT add_compression_policy('order_events', INTERVAL '30 days');

Monitoring and Alerts

Key metrics for storage monitoring:

Order loss is a critical incident. The system must have a reconciliation mechanism: periodically compare local history with exchange data via REST API and fill gaps.

Replication and Fault Tolerance

The production storage runs PostgreSQL streaming replication: primary for writes, replica for analytical queries. On primary failure, failover through Patroni with automatic switchover. RPO with proper synchronous_commit settings is zero. TimescaleDB Documentation recommends this configuration for critical systems. Our team has 10 years in blockchain development and has implemented similar solutions for funds with $1B+ turnover. With over 5 years on the market and 50+ successfully delivered projects, we guarantee a robust and scalable solution.

What's Included in the Work

• Documentation of the data schema and pipeline architecture.
• Code for TimescaleDB/ClickHouse schema, triggers, compression policies.
• Configured ingestion pipeline with batching and connection pooling.
• Migration and deployment scripts (CI/CD).
• Monitoring dashboards (Grafana + Prometheus).
• Runbook and training for your team (2–3 sessions).
• Post-release support for 2 weeks.

How We Develop the Storage

1. Load analysis — profile existing traffic, determine RPS and typical queries.
2. Schema design — choose between TimescaleDB and ClickHouse, design hypertables and indexes.
3. Pipeline implementation — configure batching, connection pooling, unlogged tables.
4. Compression and retention setup — define policies for hot and cold data.
5. Replication and monitoring — deploy Patroni, configure alerts and dashboards.
6. Load testing — simulate 50,000 events/s and verify p99 latency.
7. Documentation and training — hand over code, schemas, and runbook to your team.

Project Assessment

We'll assess your project for free within 2 business days. We'll send architecture recommendations and a quote in person-months. Contact us — we'll discuss your use cases and help design a reliable storage that won't let you down. Typical cost savings of 40% on storage costs compared to traditional solutions. For a mid-sized trading firm, this translates to annual savings of over $45,000. Get a consultation today.

Why exchange development requires deep domain expertise

We develop exchanges — not 'chart sites,' but matching engines that process thousands of orders per second without delay, route liquidity between pools, and guarantee that no user gains access to others' funds. Teams that start with the UI and postpone the engine 'for later' end up rewriting everything in six months in 90% of cases.

Order Book vs AMM: where most projects break

Centralized exchanges (CEX) are built around an order book + matching engine. Decentralized exchanges (DEX) either also use an order book (dYdX on StarkEx, Serum/OpenBook on Solana) or an AMM with concentrated liquidity (Uniswap v3/v4, Curve, Balancer). A classic mistake when developing a CEX is implementing the matching engine on top of a relational database with transactions for each match. PostgreSQL handles ~500 RPS without special effort, but at peak loads of 5,000–10,000 orders per second, it turns into a deadlock nightmare. The correct architecture: in-memory order book (Redis Sorted Sets or custom C++/Rust structure), asynchronous writing of matches to PostgreSQL via a queue (Kafka/RabbitMQ), and a separate settlement service that finally updates balances.

For DEX, the most painful problem is sandwich attacks and MEV. A pool with a plain xy=k AMM without slippage protection becomes a target for MEV bots within hours of launch. Uniswap v2 lost hundreds of millions of dollars in user liquidity. Solutions: integration with Flashbots Protect, a commit-reveal scheme for orders, or switching to TWAMM (Time-Weighted AMM) for large trades.

Concentrated liquidity and impermanent loss

Uniswap v3 introduced concentrated liquidity – LPs choose a price range in which to provide liquidity. Capital efficiency increased 4,000x compared to v2 for stable pairs. But implementing this mechanism correctly is non-trivial. The Uniswap v3 liquidity contract uses tick-based accounting: the price space is divided into discrete ticks (tick = log₁.0001(price)), each tick stores accumulated fee growth and liquidity delta. When creating a position, the lower and upper ticks are computed, and the contract recalculates all active positions at each swap. Storage layout is critical here – incorrect variable packing in slots easily adds 40–60% to swap gas cost.

We implemented a Uniswap v3 fork for a client on Polygon with a custom fee tier system. The initial version consumed 180k gas for a swap across 2 ticks. After slot packing of variables in Tick.Info and inlining several internal calls, it dropped to 112k gas. This reduced gas costs by 38% and saved the client substantial costs on fees monthly. The techniques applied are described in the Uniswap v3 Whitepaper and confirmed by our audit experience.

How a matching engine delivers performance

A production-ready matching engine is built according to the following scheme:

• Order ingestion layer – WebSocket gateway (Go or Rust), accepts orders, validates signature, checks balance via Redis, queues them. Latency at this level must be <1ms.
• Matching core – single-threaded event loop (eliminates race conditions without mutexes). In memory, we hold two Sorted Sets for each trading instrument: bids and asks. FIFO matching for limit orders, immediate-or-cancel for market orders. Throughput with a proper Rust implementation – 500k–1M matches per second on a single core.
• Settlement service – reads matches from Kafka, atomically updates balances in PostgreSQL (UPDATE accounts SET balance = balance - $1 WHERE id = $2 AND balance >= $1). Optimistic locking via row versioning.
• Withdrawal pipeline – separate service with cold/hot wallet architecture. The hot wallet holds 5–10% of total deposits, the rest is cold storage with multi-sig (Gnosis Safe or custom HSM). Automatic withdrawals only from hot wallet, large amounts require manual authorization.

How our exchange development process ensures reliability

Smart contracts and gas optimization

For EVM-based DEX (Ethereum, Arbitrum, Optimism, Polygon), the entire critical path lives in Solidity. Main contracts: Pool, Factory, Router, PositionManager (for v3-like), and Quoter for off-chain calculations. Typical mistakes we see in audits:

Reentrancy via callback. Uniswap v3 uses flash swap with a callback (uniswapV3SwapCallback). If your router lacks a nonReentrant guard and you don't check msg.sender == pool, the contract gets drained via a nested call. This is not hypothetical – several v3 forks lost funds this way.

Oracle manipulation in AMM. If your contract uses the spot price from the pool for collateral calculation, it is front-runnable. Correct: TWAP over 30+ minutes (Uniswap v3 OracleLib) or an external oracle (Chainlink).

Unbounded loops in liquidity range. If a swap crosses many ticks in a row (price impact 80%+), gas may exceed the block limit. Need MAX_TICKS_CROSSED with partial fill and returning the remainder.

For Solana DEX (Anchor framework, Rust), the architecture is fundamentally different: account-based model, Program Derived Addresses (PDA) instead of storage, Cross-Program Invocations instead of internal calls. Solana's throughput (~3,000–4,000 TPS vs 15–30 on Ethereum mainnet) allows building on-chain order books – exactly what Phoenix DEX does.

Liquidity bootstrapping and aggregator integration

Launching a pool is not enough – you need to ensure liquidity at launch. Practical mechanisms:

• Liquidity Bootstrapping Pool (LBP) – initial price is high, asset weights dynamically shift, creating selling pressure and even token distribution. Implemented in Balancer v2.
• Initial Liquidity Offering via Uniswap v3 – adding liquidity in a narrow range around the initial price, then gradually expanding as volume grows. Requires active liquidity management or integration with Arrakis/Gamma.
• Integration with 1inch, Paraswap, Li.Fi – aggregators bring traffic but require standard compliance: the pool must have correct getAmountsOut, support ERC-20 approval/permit, and not have custom transfer hooks that break the aggregator's routing.

Development process and deliverables

Analytics and design begin with choosing the architectural model: CEX with custodial storage, non-custodial DEX, or hybrid (off-chain order book + on-chain settlement, like dYdX v3). This decision determines everything – regulatory load, tech stack, team.

Development proceeds in layers: first smart contracts with full Foundry coverage (fuzzing, invariant testing), then backend services, then integration layer, and finally frontend. Testing includes fork testing on mainnet via Foundry – we reproduce real liquidity conditions, not synthetic ones.

Audit is mandatory before mainnet deployment. For DEX contracts, minimally one firm with manual review (Trail of Bits, Spearbit, Code4rena contest). For CEX custody, audit of key storage processes. We guarantee all contracts undergo formal verification and fuzzing testing (Echidna, Foundry invariant).

Estimated timelines

Cost is calculated individually after a technical briefing: chain selection, throughput requirements, custodial model. Our certified engineers with 10+ years of experience will help you choose the optimal architecture and avoid common pitfalls. Contact our team for a detailed proposal.

Pitfalls to avoid at launch

• Forgetting the price oracle in AMM. Spot price can be manipulated with a flash loan in one transaction. If your lending protocol uses the spot price from its own pool, that's a bug.
• Hot wallet without limits. A CEX without daily limits on automatic withdrawals is an invitation for attackers. Compromising one key should lose at most 10% of total funds.
• Absence of circuit breaker. A 40% price drop in 5 minutes should halt automatic liquidations or withdrawals until manual review. Without this, a cascading liquidation spiral destroys all TVL.
• Incorrect decimal handling. USDC uses 6 decimals, WBTC – 8, most tokens – 18. Mixing without normalization leads to either precision loss or overflow. Solidity has no float; we work with fixed-point using FullMath (mulDiv with overflow protection).

Want to avoid these problems? Get a consultation — we will select the architecture for your project and provide exact timelines. Order exchange development with quality guarantee and ongoing support.