Skip to content ReleaseVezual Beta is in the Plugins Console

OriginChainDB vs Aerospike

Aerospike or
OriginChainDB?

Aerospike offers a distributed record store and a graph service. OriginChainDB offers SQL, vector, graph and full-text queries. Compare how each fits your app.

A task to try
Find accounts linked to the same device.

Start here

Which fits your app?

Our view: choose based on what your app needs to do.

Consider Aerospike when

Your app relies on Aerospike clients, record lookups or Gremlin graph queries.

Read the docs
Consider OriginChainDB when

You need SQL, search and relationships in one database, using separate calls.

Explore the database

Side by side

Compare the basics.

Features from the linked docs. Test speed and cost with your own data.

Scroll sideways to compare both databases.

Aerospike and OriginChainDB capabilities
What to compareAerospikeOriginChainDB
Stored data

Records have unique keys and named fields, grouped into sets and namespaces.

Source: Aerospike database architecture

Store structured records and use their IDs to link search results and relationships.

Relationships

Aerospike Graph uses Gremlin queries over data stored in Aerospike Database.

Source: Aerospike Graph architecture

Follow relationships through the graph API. SQL and search use separate calls.

Connecting your app

Aerospike clients find the cluster nodes that hold each record.

Source: Aerospike database architecture

Use HTTP APIs, SDKs or supported PostgreSQL-compatible operations.

Try it with your data

Find accounts that share a device.

Try the same task in both systems. Use the same data and judge the full result.

The question

Which accounts used this device?

  1. 01

    Find the event

    Load the account and event. Use the same data in both tests.

  2. 02

    Follow the links

    Find the linked accounts. Include devices used by many accounts.

  3. 03

    Show the evidence

    Return the related records and their IDs. Check who is allowed to see them.

What to check

Response time

Measure the whole request, from lookup to final result.

Data changes

Add and remove links while the app is running.

Recovery

Test retries, maintenance and restoring data.

Before you move data

Plan your move.

Copy the data. Then check your queries, access rules and updates before switching.

  1. Map your data

    Match records, fields and expiry rules to the new schema. Preserve IDs.

  2. Update your queries

    Review Aerospike client code and Gremlin queries. The APIs are different.

  3. Try a small sample

    Compare records and links before switching. Keep a way to switch back.

Common questions.

Is Aerospike just a key-value database?

No. Aerospike also supports document data and a graph service. Compare the services your app needs.

Does OriginChainDB replace an Aerospike client directly?

No. You will need to review your schema, queries and client code. OriginChainDB does not implement Aerospike or Gremlin protocols.

Build with OriginChainDB

Let's look at what your app needs.