StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. In-Memory Databases
  4. In Memory Databases
  5. LokiJS vs MemSQL

LokiJS vs MemSQL

OverviewComparisonAlternatives

Overview

MemSQL
MemSQL
Stacks86
Followers184
Votes44
LokiJS
LokiJS
Stacks43
Followers57
Votes3
GitHub Stars6.8K
Forks483

LokiJS vs MemSQL: What are the differences?

Developers describe LokiJS as "In-memory JavaScript Datastore with Persistence". 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. On the other hand, MemSQL is detailed as "Database for real-time transactions and analytics". 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.

LokiJS and MemSQL belong to "In-Memory Databases" category of the tech stack.

LokiJS is an open source tool with 4.95K GitHub stars and 389 GitHub forks. Here's a link to LokiJS's open source repository on GitHub.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

MemSQL
MemSQL
LokiJS
LokiJS

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.

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.

ANSI SQL Support;Fully-distributed Joins;Compiled Queries; ACID Compliance;In-Memory Tables;On-Disk Tables; Massively Parallel Execution;Lock Free Data Structures;JSON Support; High Availability; Online Backup and Restore;Online Replication
-
Statistics
GitHub Stars
-
GitHub Stars
6.8K
GitHub Forks
-
GitHub Forks
483
Stacks
86
Stacks
43
Followers
184
Followers
57
Votes
44
Votes
3
Pros & Cons
Pros
  • 9
    Distributed
  • 5
    Realtime
  • 4
    Columnstore
  • 4
    Concurrent
  • 4
    Sql
Pros
  • 3
    Can query the objects directly
Integrations
Google Compute Engine
Google Compute Engine
MySQL
MySQL
QlikView
QlikView
Node.js
Node.js
NativeScript
NativeScript
Apache Cordova
Apache Cordova
PhoneGap
PhoneGap

What are some alternatives to MemSQL, LokiJS?

Redis

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

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.

Aerospike

Aerospike

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.

Apache Ignite

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

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

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

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

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

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.

BuntDB

BuntDB

BuntDB is a low-level, in-memory, key/value store in pure Go. It persists to disk, is ACID compliant, and uses locking for multiple readers and a single writer. It supports custom indexes and geospatial data. It's ideal for projects that need a dependable database and favor speed over data size.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase