Installatin Steps

wget -O aerospike.tgz ''
tar -xvf aerospike.tgz
cd aerospike-server-community-*-ubuntu12*
sudo ./asinstall # will install the .rpm packages
sudo service aerospike start

Write Key Value

ascli put

ns the namespace for the record being written.
The set is the set for the record being written.
The key is the key for the record being written. It can be either an > integer or string.
The record is a JSON object representing the record to be written. The JSON object’s keys are the bin names and the value are bin values.

Reading Key Value

ascli get

Reading All Values

  1. Enter aql command in terminal
  2. Enter bellow query
select * from

Start, Stop and Restart aerospike service

sudo service aerospike start
sudo service aerospike stop
sudo service aerospike restart

Data Storage

after restart service, all stored data will be cleaned.

Reserved TCP Ports

Name Default Port Description
Service 3000 Application, Tools, and Remote XDR use the Service port for database operations and cluster state.
Fabric 3001 Intra-cluster communication port. Replica writes, migrations, and other node-to-node communications use the Fabric port.
Mesh Heartbeat 3002 Heartbeat protocol ports are used to form and maintain the cluster. (Only one heartbeat port may be configured.)
Multicast Heartbeat 9918 Heartbeat protocol ports are used to form and maintain the cluster. (Only one heartbeat port may be configured.)
Info 3003 Telnet port that implements a plain text protocol for administrators to issue info commands. For more information, see asinfo documentation.
XDR Service1 3004 (Optional) Port to query health state of the Cross Datacenter Replication (XDR) client.


Aerospike Install
Aerospike Networks

  1. Ensure that all Application and XDR nodes can communicate to the service port on all Aerospike nodes. Also ensure that each node can communicate over the configured heartbeat and fabric ports. 
Reading time: 1 min
Name Aerospike Redis MongoDB Neo4j
Description Flash-optimized In-memory NoSQL Database In-memory data structure store, used as database, cache and message broker One of the most popular document stores Open source graph database
Database model Key-value store Key-value store Document store Graph DBMS
License Open Source – Apache and AGPL Licenses; open sourced in June 2014; commercial Enterprise Edition available Open Source – BSD 3-Clause, commercial license available Open Source – AGPL version3, Commercial Licence available Open Source – AGPL version3, Commercial Licence available
Implementation language C C C++ Java
Server operating systems Linux BSD, Linux, OS X, Windows Linux, OS X, Solaris, Windows Linux, OS X, Windows
Data scheme schema-free schema-free schema-free, Although schema-free, documents of the same collection often follow the same structure schema-free
Typing yes partial => Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes yes => string, integer, double, boolean, date, object_id yes
Secondary indexes yes no yes yes => pluggable indexing subsystem, by default Apache Lucene
SQL no no no no
APIs and other access methods proprietary protocol proprietary protocol using JSON Cypher query language, Java API, RESTful HTTP API
Supported programming languages C, C#, Erlang, Go, Java, JavaScript (Node.js), Lua, Perl, PHP, Python, Ruby C,C#,C++,Clojure,Crystal,D,Dart,Elixir,Erlang,Fancy,Go,Haskell,Haxe,Java,JavaScript (Node.js),Lisp,Lua,MatLab,Objective-C,OCaml,Perl,PHP,Prolog,Pure Data,Python,R,Rebol,Ruby,Rust,Scala,Scheme,Smalltalk,Tcl Actionscript, C, C#, C++, Clojure, ColdFusion, D, Dart, Delphi, Erlang, Go, Groovy, Haskell, Java, JavaScript, Lisp, Lua, MatLab, Perl, PHP, PowerShell, Prolog, Python, R, Ruby, Scala ,Smalltalk .Net, Clojure, Go, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby, Scala
Server-side scripts user defined functions Lua JavaScript yes
Triggers no no no yes
Partitioning methods Sharding Sharding Sharding none
Replication methods selectable replication factor Master-slave replication Master-slave replication Master-slave replication
Consistency concepts Eventual Consistency in cross-datacenter configuration and Immediate Consistency in local cluster configuration Eventual Consistency Eventual Consistency, Immediate Consistency Eventual Consistency configurable in High Availability Cluster setup, Immediate Consistency
In-memory capabilities yes yes yes no
Durability (data storage) yes yes => Configurable mechanisms for persistence via snapshots and/or operations logs yes => optional yes
Horizontal salable yes yes Yes, with sharding No (Community), Yes (Enterprise)
Data storage RAM,SSD Volatile memory, File System Volatile memory, File System local (community), Data,Persisted to Disk,Volatile memory,Memory-Mapped File (Enterprise)
Memory minimum 2 GB 3 GB depends on several factors 2 GB (Enterprise)
Value size max. 1 MB 512 MB 16 MB 34 B(comunity), 1 TB (Enterprise)
Reading time: 2 min