News & Notes
Longer-form pieces, field notes, and curated insights on Aeron performance — things that don’t fit neatly into the reference sections.
Recently updated
Section titled “Recently updated”The twelve most recently updated pages across the whole site, newest first. Dates come from each page’s last git commit, captured at build time.
- Performance Tuning Aeron® Cluster Snapshot Performance: A Matching-Engine Case Study From a snapshot that failed above 16 resting orders to a 5M-order take in 179 ms under ZGC, then a 3-node cluster where the Archive's per-block fsync, not encoding, sets the client pause.
- Operations & Resilience Tuning Cluster Failover Time How to reason about Aeron® Cluster leader failover time — the detection + election budget, which timeouts to turn, and the trade-off between fast recovery and self-inflicted false failovers. With measured results and a recommended sweet spot.
- Performance Tuning NAK Timer Tuning (Lever B) How to derive aeron.nak.multicast.max.backoff, group.size, and retransmit linger from RTT and receiver count — with measured results: a 79× tail collapse under seeded loss.
- Performance Tuning Bandwidth Delay Product (BDP) How BDP determines minimum buffer sizing for sustained throughput across CPG, same-AZ, cross-AZ, and cross-region round-trip latencies.
- Performance Tuning The Four Receive-Path Buffers The four nested buffers a packet traverses on the receive path — ENA RX ring, OS socket buffer, Aeron term buffer, and the flow-control window — their constraints, and how to size them as a consistent stack.
- Operations & Resilience Archive Retention and Purge: How Much Log Can You Delete? The position algebra that decides whether a node can restart or must be rebuilt, the two retention models to choose between, and a detach-validate-delete purge workflow that keeps every recovery path intact.
- Operations & Resilience Aeron® Cluster and Raft Consensus Cluster design principles, the two Raft RPCs, Aeron's canvass/parallel-replication improvements, and the five Raft safety guarantees.
- Operations & Resilience Snapshot Failure and Recovery in Aeron® Cluster What happens when a cluster node is killed or throws mid-snapshot, the correct recovery procedure case by case (restart, invalidate-latest-snapshot, wipe-and-replay), and how OSS and Premium differ.
- Monitoring Monitoring Aeron®: Metrics and Alerting for Your Observability Platform How to get Aeron and Aeron Cluster telemetry out of the CnC file and into Prometheus/Grafana/Datadog, the counters that matter mapped to failure modes, and the alert conditions to wire up — OSS DIY exporter vs Premium Aeron Insights.
- Operations & Resilience Aeron® Cluster Placement: Choosing an AZ Topology Multi-AZ vs primary+standby vs single-AZ for a matching-engine Raft cluster — the latency-vs-blast-radius trade-off, scored on seven dimensions, plus two hybrids: the stretched 2+1 local-majority cluster and the single-AZ-plus-cross-AZ-standby middle ground most exchanges actually land on.
- OMS / Matching Engine Best Practices Choosing an Order-Book Data Structure How to pick the structure at the heart of a matching engine — price-indexed arrays, balanced trees, skip lists, linked levels, hash+heap, and adaptive radix trees — judged by hot-path latency, cache behavior, liquidity profile, and the cancel-heavy order flow they must survive.
- Operations & Resilience Migrating a Live Aeron® Cluster Across Regions Node-by-node vs whole-cluster swap for moving a running matching-engine cluster from Region A to Region B — measured downtime, the DNS/JVM-cache hazard, and how a graceful leader step-down makes the one unavoidable leader crossover sub-second.
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.