Aerospike vs NCache | What are the differences? | StackShare

Aerospike vs NCache

Overview

Aerospike

Stacks200

Followers288

Votes48

GitHub Stars1.3K

Forks196

NCache

Stacks146

Followers38

Votes0

Aerospike vs NCache: What are the differences?

Aerospike: Flash-optimized in-memory open source NoSQL database. Aerospike is an open-source, modern database built from the ground up to push the limits of flash storage, processors and networks. It was designed to operate with predictable low latency at high throughput with uncompromising reliability – both high availability and ACID guarantees; NCache: Distributed In-Memory Datastore. It is an extremely fast and scalable distributed cache for .NET. It helps high traffic server applications remove data storage bottlenecks by caching application and linearly scale to handle extreme transaction loads without slowing down.

Aerospike and NCache belong to "In-Memory Databases" category of the tech stack.

Aerospike is an open source tool with 296 GitHub stars and 55 GitHub forks. Here's a link to Aerospike's open source repository on GitHub.

🔥 Trending in In-Memory Databases on StackShare

CursusDB In Memory Databases

An open-source in-memory document oriented database

Try it View Docs Alternatives

Try

Detailed Comparison

Aerospike	NCache
Aerospike is an open-source, modern database built from the ground up to push the limits of flash storage, processors and networks. It was designed to operate with predictable low latency at high throughput with uncompromising reliability – both high availability and ACID guarantees.	NCache is an open source distributed cache for .NET & .NET Core (Apache 2.0) by Alachisoft. NCache provides an extremely fast and linearly scalable distributed cache that caches application data and reduces expensive database trips.
99% of reads/writes complete in under 1 millisecond.;Predictable low latency at high throughput – second to none. Read the YCSB Benchmark.;The secret sauce? A thousand things done right. Server code in ‘C’ (not Java or Erlang) precisely tuned to avoid context switching and memory copies. Highly parallelized multi-threaded, multi-core, multi-cpu, multi-SSD execution.;Indexes are always stored in RAM. Pure RAM mode is backed by spinning disks. In hybrid mode, individual tables are stored in either RAM or flash.	Recovery from Split-Brain; ASP.NET Core Response Caching; .NET Core; Virtualization and Containerization; Performance & Scalability; Cache Elasticity (High Availability); Cache Topologies; WAN Replication; Cache Administration; Security & Encryption; Object Caching Features; Managing Data Relationships; Synchronization with Data Sources; Runtime Data Sharing; Search Cache (SQL-Like); Data Grouping; Read-through & Write-through; Cache Size Management; ASP.NET Support; Third Party Integrations;
Statistics
GitHub Stars 1.3K	GitHub Stars -
GitHub Forks 196	GitHub Forks -
Stacks 200	Stacks 146
Followers 288	Followers 38
Votes 48	Votes 0
Pros & Cons
Pros 16 Ram and/or ssd persistence 12 Easy clustering support 5 Easy setup 4 Acid 3 Performance better than Redis	No community feedback yet
Integrations
No integrations available	Windows Linux .NET ASP.NET

What are some alternatives to Aerospike, NCache?

Redis

Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.

Hazelcast

With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution.

MemSQL

MemSQL converges transactions and analytics for sub-second data processing and reporting. Real-time businesses can build robust applications on a simple and scalable infrastructure that complements and extends existing data pipelines.

Apache Ignite

It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale

SAP HANA

It is an application that uses in-memory database technology that allows the processing of massive amounts of real-time data in a short time. The in-memory computing engine allows it to process data stored in RAM as opposed to reading it from a disk.

VoltDB

VoltDB is a fundamental redesign of the RDBMS that provides unparalleled performance and scalability on bare-metal, virtualized and cloud infrastructures. VoltDB is a modern in-memory architecture that supports both SQL + Java with data durability and fault tolerance.

Tarantool

It is designed to give you the flexibility, scalability, and performance that you want, as well as the reliability and manageability that you need in mission-critical applications

Azure Redis Cache

It perfectly complements Azure database services such as Cosmos DB. It provides a cost-effective solution to scale read and write throughput of your data tier. Store and share database query results, session states, static contents, and more using a common cache-aside pattern.

KeyDB

KeyDB is a fully open source database that aims to make use of all hardware resources. KeyDB makes it possible to breach boundaries often dictated by price and complexity.

LokiJS

LokiJS is a document oriented database written in javascript, published under MIT License. Its purpose is to store javascript objects as documents in a nosql fashion and retrieve them with a similar mechanism. Runs in node (including cordova/phonegap and node-webkit), nativescript and the browser.