Īerospike 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. It operates in three layers: a data storage layer, a self-managed distribution layer, and a cluster-aware client layer. Storing, Indexing and Querying JSON DocumentsĪerospike Database is modeled under the shared-nothing architecture and written in C.Improved memory footprint and garbage collection for secondary indices.Added bin level convergence for active-active XDR scenarios.Strong consistency multi site clustering.Refactor cross datacenter replication (XDR).Required "Jump" Release before 5.0 ( LTS).Modify Eviction/Expiration ( TTL) Default behavior.Added support for HyperLogLog (HLL) data types.Support for Intel Persistent Memory for storing data.Nested Collection Data Type API support.Support for Intel Persistent memory for Indexing.Change notification Framework - connectors for Apache Kafka and JMS.Transport Layer Security on client-server communications.Secondary Index on List, Map & Geospatial.
#Kitematic aerospike software
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. In 2012, Aerospike acquired AlchemyDB, and integrated the two databases' functions, including the addition of a relational data management system. 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. In August 2012, the company - which had been providing its database since 2010 - rebranded both the company and software name to Aerospike.
0 kommentar(er)
