Aerospike (database)

Open source NoSQL database From Wikipedia, the free encyclopedia

Aerospike Database is a real-time, high performance NoSQL database. Designed for applications that cannot experience any downtime and require high read & write throughput. Aerospike is optimized to run on NVMe SSDs capable of efficiently storing large datasets (Gigabytes to Petabytes). Aerospike can also be deployed as a fully in-memory cache database. Aerospike offers Key-Value, JSON Document, Graph data, and Vector Search models. Aerospike is an open source distributed NoSQL database management system, marketed by the company also named Aerospike.[1]

Quick Facts Developer(s), Initial release ...
Aerospike Database
Developer(s)Aerospike
Initial release2010; 15 years ago (2010)
Stable release
7.1.0.0 / May 15, 2024; 11 months ago (2024-05-15)
Repository
Written inC
Operating systemLinux
TypeDistributed Database, key-value database
LicenseAGPL
Websitewww.aerospike.com
Close

History

Summarize
Perspective

Aerospike was first known as Citrusleaf. In August 2012, the company - which had been providing its database since 2010 - rebranded both the company and software name to Aerospike.[2] The name "Aerospike" is derived from the aerospike engine, a type of rocket nozzle that is able to maintain its output efficiency over a large range of altitudes, and is intended to refer to the software's ability to scale up.[3] In 2012, Aerospike acquired AlchemyDB, and integrated the two databases' functions, including the addition of a relational data management system.[4] On June 24, 2014, Aerospike was opensourced under the AGPL 3.0 license for the Aerospike database server and the Apache License Version 2.0 for its Aerospike client software development kit.[5][6][7]

Release history

More information Version, First Release Version ...
VersionFirst Release VersionFirst Release DateLatest VersionRelease dateFeaturesRef
Old version, not maintained: 3.13.1.3January 2, 20143.1.14February 25, 2014

[8]

Old version, not maintained: 3.23.2.0March 19, 20143.2.9May 12, 2014

[8]

Old version, not maintained: 3.33.3.5June 9, 20143.3.26December 3, 2014

[8]

Old version, not maintained: 3.43.4.0December 8, 20143.4.1January 12, 2015

[8]

Old version, not maintained: 3.53.5.2February 13, 20153.5.15July 15, 2015

[8]

Old version, not maintained: 3.63.6.0August 31, 20153.6.4November 10, 2015

[8]

Old version, not maintained: 3.73.7.0December 10, 20153.7.5.1March 31, 2016

[9] [8]

Old version, not maintained: 3.83.8.1April 15, 20163.8.4June 17, 2016
  • Secondary Index on List, Map & Geospatial

[10] [8]

Old version, not maintained: 3.93.9.0July 11, 20163.9.1.1September 2, 2016
  • Rapid Rebalance

[11] [8]

Old version, not maintained: 3.103.10.0.3October 21, 20163.10.1.5January 13, 2017
  • Durable Delete
  • Support IPv6

[12] [8]

Old version, not maintained: 3.113.11.0January 5, 20173.11.1.1February 15, 2017

[13] [8]

Old version, not maintained: 3.123.12.0March 15, 20173.12.1.3July 31, 2017
  • Predicate Filters

[14] [8]

Old version, not maintained: 3.133.13.0.1May 30, 20173.13.0.11April 26, 2018
  • Clustering Layer refactoring
  • Required "Jump" Release before 3.14

[15] [8]

Old version, not maintained: 3.143.14.0June 6, 20173.14.1.10April 26, 2018
  • Clustering Layer refactoring pt. 2

[15] [8]

Old version, not maintained: 3.153.15.0.1October 3, 20173.15.1.4January 3, 2018

[8]

Old version, not maintained: 3.163.16.0.1February 21, 20183.16.0.6March 2, 2018

[8]

Old version, not maintained: 4.04.0.0.1March 7, 20184.0.0.6September 6, 2018

[16] [17]

Old version, not maintained: 4.14.1.0.1May 10, 20184.1.0.6September 6, 2018

[18] [17]

Old version, not maintained: 4.24.2.0.2May 31, 20184.2.0.10August 10, 2018
  • Increase maximum object size to 8MB

[19] [17]

Old version, not maintained: 4.34.3.0.2August 1, 20184.3.1.14April 26, 2019
  • All Flash Namespaces

[20] [17]

Old version, not maintained: 4.44.4.0.4November 19, 20184.4.0.15April 26, 2019
  • Change notification Framework - connectors for Apache Kafka and JMS
  • Rack aware reads

[21] [17]

Old version, not maintained: 4.54.5.0.1December 12, 20184.5.3.22July 7, 2020

[22] [17]

Old version, not maintained: 4.64.6.0.2August 9, 20194.6.0.21September 18, 2020
  • Added bitwise BLOB operations
  • Nested Collection Data Type API support

[17]

Old version, not maintained: 4.74.7.0.2September 30, 20194.7.0.26November 25, 2020
  • ADQ Support

[23] [17]

Old version, not maintained: 4.84.8.0.1December 12, 20194.8.0.31March 29, 2021
  • Support for client/server compression
  • Support for Intel Persistent Memory for storing data

[24] [17]

Old version, still maintained: 4.94.9.0.3April 8, 20204.9.0.36October 25, 2021
  • Added support for HyperLogLog (HLL) data types
  • Improve Scans for non key value access
  • Modify Eviction/Expiration (TTL) Default behavior
  • Required "Jump" Release before 5.0 (LTS)

[25] [17]

Old version, not maintained: 5.05.0.0.3May 14, 20205.0.0.38July 19, 2021
  • Refactor cross datacenter replication (XDR)
  • Strong consistency multi site clustering

[26] [17]

Old version, not maintained: 5.15.1.0.3July 31, 20205.1.0.42September 20, 2021

[27] [17]

Old version, not maintained: 5.25.2.02October 1, 20205.2.0.37October 30, 2021
  • Redesigned predicate expressions

[28] [17]

Old version, still maintained: 5.35.3.0.2December 10, 20205.3.0.27October 30, 2021
  • Added expression filtering for XDR
  • Expanded Multi-Site Clustering

[29] [17]

Old version, still maintained: 5.45.4.0.1January 13, 20215.4.0.22October 30, 2021
  • Added bin level convergence for active-active XDR scenarios

[30] [17]

Old version, still maintained: 5.55.5.0.2February 5, 20215.5.0.20October 30, 2021

[17]

Old version, still maintained: 5.65.6.0.3May 10, 20215.6.0.14October 30, 2021
  • Aerospike Expressions
  • Set Indexes
  • Per-user quotas
  • Boolean datatype

[31] [17]

Old version, still maintained: 5.75.7.0.7September 27, 20215.7.0.9December 10, 2021
  • Improved memory footprint and garbage collection for secondary indices
  • Support for PKI authentication

[32] [17]

Latest version: 6.06.0.0.0April 27, 20226.0.0.0April 27, 2022
  • Storing, Indexing and Querying JSON Documents
  • Partitioned Secondary Index Queries

[33] [17]

Legend:
Old version, not maintained
Old version, still maintained
Latest version
Close

Features

Summarize
Perspective

Aerospike Database is modeled under the shared-nothing architecture and written in C. It operates in three layers: a data storage layer, a self-managed distribution layer, and a cluster-aware client layer.[34]

Aerospike uses hybrid memory architecture: the database indices are stored fully in main random-access memory, while the data is stored on a persistent device using the data layer. The data layer stores the data in solid-state drive, NVMe or Persistent memory.[35] Reading the data is done using a direct access to the record position on disk using a direct pointer from the primary index, and data writes are optimized through large block writes to reduce latency.[34] This architecture to fetch all records from the persistent device and void the use of data cache. Aerospike also provides the ability to store the data fully in RAM, thus acting as an in-memory database. In that case, data would be persisted to either SSD, NVMe, PMEM or traditional rotational media.[2]

Aerospike provides single-record ACID transactions.[36] The distribution layer is responsible to replicate the data across nodes to ensure the durability and immediate consistency properties of the transaction. This allows the database to remain operational even when an individual server node fails or is manually removed from the cluster.[34] Since version 4.0 (2018), Aerospike Database can be configured both as Available and Partition-tolerant (AP) or Consistent and Partition-tolerant (CP) under the CAP theorem.[37][38]

The client cluster-aware layer is used to track the cluster configuration in the database, and manages client direct communications to all the nodes in the cluster.[34] The clustering is done using heartbeats and Paxos based gossip protocol algorithm.[39]

The software employs two sub-programs that are codenamed Defragmenter and Evictor.[34][40] Defragmenter removes data blocks that have been deleted, and Evictor frees RAM space by removing references to expired records.[34][41]

References

Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.