Aerospike (database)
{{Short description|Open source NoSQL database}}
{{Infobox software
| name = Aerospike Database
| logo = Aerospike logo 2012.svg
| logo alt = Aerospike
| developer = Aerospike
| released = {{Start date and age|2010|df=yes}}
| latest release version = 8.0.0.7
| latest release date = {{release date and age|2025|04|26}}
| programming language = C
| operating system = Linux
| genre = Distributed Database, key-value database
| license = AGPL
| website = {{URL|https://www.aerospike.com/}}
}}
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.{{ cite web | url = http://www.forrester.com/pimages/rws/reprints/document/118782/oid/1-S3R21U | title = NoSQL Key-Value Databases, Q3 2014 | publisher = Forrester Research | date = 15 October 2014 | access-date = 29 November 2014 | author = Yuhanna, Noel }}
History
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.{{Cite web|url=http://www.dbms2.com/2012/08/27/aerospike-the-former-citrusleaf/|title=Aerospike, the former Citrusleaf|date=August 27, 2012|publisher=DBMS2|access-date= 17 May 2013 }} 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.{{Cite web|url=http://www.wordiq.com/definition/Aerospike |title= Definition of Aerospike engine |publisher=Wordiq |access-date=17 May 2013 |url-status=dead |archive-url=https://web.archive.org/web/20041224150845/http://www.wordiq.com/definition/Aerospike |archive-date=24 December 2004 }} In 2012, Aerospike acquired AlchemyDB, and integrated the two databases' functions, including the addition of a relational data management system.{{cite news |title=Grim And Gritty Startup Reboot: NoSQL Company Citrusleaf Changes Name And Acquires AlchemyDB |author=Klint Finley |work=TechCrunch |date=August 28, 2012 |access-date=November 25, 2014 |url=https://techcrunch.com/2012/08/28/nosql-company-citrusleaf-lands-series-b-funding-changes-name-and-acquires-alchemydb/}} 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.{{cite web |title=Aerospike: Thanks for that $20m, VCs ... next we'll OPEN SOURCE our NoSQL database |author=Jack Clark |website=The Register |date=June 24, 2014 |access-date=November 25, 2014 |url=https://www.theregister.co.uk/2014/06/24/aerospike_database_open_source/}}{{ cite web | url = http://siliconangle.com/blog/2014/06/24/aerospike-bets-on-end-users-to-monetize-subscriptions/?angle=silicon | title = Aerospike open sources NoSQL database in bid to expand customer ranks | author = Rachel Schramm | work = Silicon Angle | date = 24 June 2014 | access-date = 30 July 2014}}{{ cite web | url = http://www.infoq.com/news/2014/06/aerospike-open-source | title = Aerospike Open Sources Their In-memory NoSQL Database | author = Abel Avram | work = InfoQ | date = 24 June 2014 | access-date =30 July 2014}}
=Release history=
Features
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.{{Cite web|url=https://www.aerospike.com/docs/architecture/assets/vldb2016.pdf|title=Aerospike: Architecture of a Real-Time Operational DBMS|access-date=16 Feb 2021|orig-date=2016}}
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.{{cite web|title=Enhanced Persistent Memory Support and Compression|url=https://www.aerospike.com/blog/aerospike-4-8-intel-pmem-support-b/|date=December 19, 2019|access-date=2021-02-16}} 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. 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.
Aerospike provides single-record ACID transactions.{{cite web |title=CAP and ACID {{!}} Aerospike |url=https://www.aerospike.com/docs/architecture/acid.html |website=www.aerospike.com |access-date=18 February 2021}} 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. 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.{{cite web |last1=Kingsbury |first1=Kyle |title=Jepsen: Aerospike 3.99.0.3 |url=https://jepsen.io/analyses/aerospike-3-99-0-3 |website=jepsen.io |access-date=18 February 2021 |date=2018-03-07}}{{cite web |title=Strong Consistency mode {{!}} Aerospike |url=https://www.aerospike.com/docs/architecture/consistency.html |website=www.aerospike.com |access-date=18 February 2021}}
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. The clustering is done using heartbeats and Paxos based gossip protocol algorithm.{{cite web|title=Clustering {{!}} High-speed Distributed Cluster Formation|url=https://www.aerospike.com/docs/architecture/clustering.html#high-speed-distributed-cluster-formation|access-date=2021-02-16|website=www.aerospike.com}}
The software employs two sub-programs that are codenamed Defragmenter and Evictor.{{Cite web|url=http://www.aerospike.com/blog/super-storm-sandy-and-100-uptime-2/ |title=CTO Panel on Super Storm Sandy and 100% Uptime |date=December 14, 2012 |access-date=17 May 2013 |url-status=dead |archive-url=https://web.archive.org/web/20130303004951/http://www.aerospike.com/blog/super-storm-sandy-and-100-uptime-2/ |archive-date=3 March 2013 }} Defragmenter removes data blocks that have been deleted, and Evictor frees RAM space by removing references to expired records.{{Cite web|title=Documentation {{!}} Aerospike|url=https://www.aerospike.com/docs/operations/manage/storage/|access-date=2020-07-28|website=www.aerospike.com}}
References
{{reflist}}
External links
- {{Official website|https://www.aerospike.com/}}
Category:Client-server database management systems
Category:Distributed data stores
Category:Distributed computing architecture
Category:Document-oriented_databases
Category:Free database management systems
Category:Software using the GNU Affero General Public License