Skip to content
p50 p99 p99.9

LowLatencyOps

A field guide to running Aeron® in production — tuning, benchmarking, monitoring, and surviving the bad days.

Performance Tuning

The levers that move p50, p99, and throughput — BDP and receive-path buffers, NAK timers, batching and idle strategy, core pinning, NUMA, and when the DPDK media driver pays off.

Open the tuning guide →

Benchmarking

How to read published Aeron numbers without being fooled by the burst knob, why steady-state TPS misses micro-bursts, and how injected loss moves p50 and p99.

Open benchmarking →

Monitoring

Getting counters out of the CnC file into Prometheus or Datadog, the alerts to wire up, and capturing hot-path latencies without adding jitter.

Open monitoring →

Operations & Resilience

Cluster Standby, disaster recovery, backup strategies, and a failure-mode runbook: node, network, disk, snapshot, and human-error scenarios.

Open operations →

OMS / ME Best Practices

Building an exchange on Aeron Cluster: sharding the OMS by user and the matching engine by symbol, rolling upgrades, and choosing an order-book data structure.

Open OMS / ME best practices →

  1. Security & Supply Chain 0 vs 382: Third-Party Code in Your Messaging Stack Third-party runtime dependencies, client and server, for 15 messaging stacks from Aeron® to Kafka, Pulsar and AutoMQ, at their latest stable releases.
  2. OMS / Matching Engine Best Practices Rolling Upgrade of Cluster Member Nodes Upgrading Aeron Cluster members one node at a time: quorum math, follower-first ordering, catch-up checks with cluster counters, leader handoff, and versioning a deterministic state machine with log-position feature flags.
  3. OMS / Matching Engine Best Practices Sharding an OMS by the Actor Pattern Scaling a matching engine past a single deterministic state machine by partitioning the instrument universe into single-threaded actors — shard keys, routing, cross-shard coordination, and how it maps onto Aeron Cluster.
  4. Operations & Resilience Backups and Disaster Recovery DR scenarios by severity and the OSS Cluster Backup versus Premium Cluster Standby comparison for recovery speed, data loss, and mechanism.
  5. Operations & Resilience Client-Cluster Communication Flow How clients connect, get redirected to the leader, and the full ingress-consensus-service-egress message sequence that provides ordering and replication.
  6. Operations & Resilience Failure-Mode Runbook: Clients, Ops, and Resources Client reconnect and idempotency, operational and human errors, and resource exhaustion from OOM, file descriptors, CPU starvation, and thread starvation.

All recent updates →

This site is not affiliated with, endorsed by, or sponsored by Adaptive Financial Consulting Limited or the Aeron project. Aeron is a registered trademark of Adaptive Financial Consulting Limited.

Aeron is a trademark of Adaptive Financial Consulting Limited in the United Kingdom and other countries.