Welcome
If you’re not yet familiar with it, Aerospike is an open source, NoSQL distributed database. From its beginning ten years ago, Aerospike was optimally designed for modern server architectures. This meant being organically a distributed system, not ad-hoc clustered using sharding, load balancers and proxies. It meant being a multi-node, multi-core, multi-threaded system that attacks its workload through massive parallelization, vertically scaling to use all the resources of each cluster node before needing to scale out. It meant being Flash native for storage, persisting and serving data directly out of SSDs or persistent memory, instead of requiring enormous amounts of DRAM to perform.
Aerospike is first of all a database, with Jepsen validated linearizable strong consistency and sequential strong consistency. Alternatively, Aerospike supports relaxed strong consistency and high availability (AP) modes. It can also be used as a cache. You can find more about the Aerospike Database on our site, in our docs, or our Developer Hub.
This publication is our space for curated, engineering focused articles about Aerospike. These articles will touch on developing applications using Aerospike as the primary data store. They will go into data modeling in Aerospike using key-value store or document store approaches. Mainly, they will present different views on how to use Aerospike to solve problems that interest developers. You can also expect articles that would be of interest to devops folks.
If you want your article to be added contact us at community@aerospike.com
Ronen
