Review: Aerospike kicks scale-out NoSQL into high gear

Aerospike Server leverages memory and SSDs to bring extremely high throughput to a flexible, scalable key-value database

At a Glance
  • Aerospike Server 3.4.1

In this new world of scale-out, clustered NoSQL databases that process thousands -- even millions -- of transactions per second, good cache management is critical for good performance. Service I/O requests from RAM whenever you can; service I/O requests from spinning disks only when you must.

Aersospike takes this principle to its logical extreme -- service all requests from RAM -- and even goes a step further: By leveraging the benefits of SSDs, Aerospike amplifies the performance and scalability of an otherwise all-RAM database. Aerospike does not completely ignore the utility of spinning disks, but "traditional" hard disks do not participate in the moment-to-moment activity of an Aerospike cluster. Instead, they serve as backup media for data protection in the event of catastrophic failure.

Aerospike is an open source, in-memory NoSQL database that is fundamentally a key-value store. It'snamed after a kind of rocket engine whose principal advantage is that it uses less fuel at lower altitudes, as compared to a conventional engine. There are currently no Aerospike rocket engines in use; the same is not true of the database.

Aerospike is available in a free community edition and in a paid-for enterprise edition. The cost of the enterprise edition depends on the amount of data stored. (For details, see Aerospike's products page.) The main difference between the two editions -- other than that the community edition is without 24-7 customer support -- is the cross-data center replication provided in the enterprise edition, a process that executes in parallel with the core Aerospike engine to replicate data between clusters.

aerospike dashboard2

The Aerospike Management Console dashboard provides an overview of cluster statistics, real-time displays of read and write throughput, a detailed view of individual nodes, and a view into cluster namespaces.

To continue reading this article register now