ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #aerospike
How Aerospike’s HMA stores indexes in DRAM and records on NVMe delivers sub-millisecond latency at lower cost, with concrete sizing and hardware guidance.
Aerospike's strong-consistency mode provides linearizable reads/writes via Raft but disables XDR, secondary indexes, and makes minority partitions unavailable. Benchmark, simulate partitions, and monitor quorum latency before adopting.
A decision guide on Aerospike commit levels, comparing Async and Sync modes to balance write latency against data durability and consistency.
Aerospike's Hybrid Memory Architecture splits storage between DRAM indexes and NVMe flash data. Here is how it works, how to size it, and what to watch for.
Strong Consistency in Aerospike gives linearizable reads by requiring a quorum of replicas to agree before a read or write completes. It must be enabled at namespace creation and trades availability for consistency during partitions.
Set the ‘strong-consistency’ flag in Aerospike, verify it with asinfo and aql, and know how to roll back if write latency spikes.
Enable Aerospike Strong Consistency for financial workloads that cannot tolerate stale reads, but expect higher write latency and quorum requirements.
Enable linearizable reads and writes in Aerospike by configuring strong consistency at the namespace level and matching client policies.
Learn how to implement and manage Aerospike secondary indexes to enable non-primary key lookups without the performance penalty of full cluster scans.