Realm vs Redis

Overview

Redis

Stacks61.9K

Followers46.5K

Votes3.9K

GitHub Stars42

Forks6

Realm

Stacks279

Followers441

Votes16

Realm vs Redis: What are the differences?

Introduction

In the realm of database management systems, two popular choices that are often compared are Realm and Redis. These systems offer distinct features and functionalities that cater to different needs and use cases. Let's explore the key differences between Realm and Redis.

Data Model: Realm is an object-oriented database that stores data as objects with properties and relationships, making it easier to work with data in an application. On the other hand, Redis is a key-value store that operates with simple data structures like strings, lists, sets, and hashes.
Persistence: Realm offers built-in support for offline data synchronization, meaning data can be stored locally and then synced with a server when a connection is available. Redis, on the other hand, is an in-memory database that can optionally persist data to disk.
Scalability: Redis is known for its high performance and scalability, making it a preferred choice for applications requiring fast read and write operations. Realm, on the other hand, may not be as performant as Redis in scenarios where massive scalability is required.
Data Querying: Redis supports various data querying options through its powerful set of commands, making it suitable for scenarios that require complex data manipulation and analysis. Realm, on the other hand, may be more suitable for simpler data querying needs within the context of an application.
Deployment: Redis is often used as a standalone server or as a cluster for high availability and scalability. Realm, on the other hand, is typically integrated within the application codebase, simplifying deployment but potentially limiting scalability options.
Use Cases: Realm is commonly used in mobile and IoT applications where offline capabilities are vital, while Redis is often implemented in high-performance scenarios like caching, session management, real-time analytics, and message queues.

In Summary, Realm and Redis differ in their data models, persistence mechanisms, scalability, querying capabilities, deployment options, and target use cases.

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)

Manual

Detailed Comparison

Redis	Realm
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.	The Realm Mobile Platform is a next-generation data layer for applications. Realm is reactive, concurrent, and lightweight, allowing you to work with live, native objects.
-	Feels like Home - Realm’s data structures look like the Objects and Arrays of your language, but provide additional features such as: querying, relationships & graphs, thread safety, and more.;Memory-Efficient - Realm is not built on SQLite. Instead, a custom C++ core is used to provide memory-efficient access to your data by using Realm objects, which usually consume less RAM than native objects.;F-F-Fast! - Realm offers extraordinary performance compared to SQLite and other persistence solutions.
Statistics
GitHub Stars 42	GitHub Stars -
GitHub Forks 6	GitHub Forks -
Stacks 61.9K	Stacks 279
Followers 46.5K	Followers 441
Votes 3.9K	Votes 16
Pros & Cons
Pros 888 Performance 542 Super fast 514 Ease of use 444 In-memory cache 324 Advanced key-value cache Cons 15 Cannot query objects directly 3 No secondary indexes for non-numeric data types 1 No WAL	Pros 7 Good 3 Elegant API 3 Cloud Syncing 2 React Native Support 1 Strong Adoption Growth Cons 1 No offline support for web till now

What are some alternatives to Redis, Realm?

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 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.

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.

Related Comparisons

Realm vs Redis: What are the differences?

Introduction

Data Model: Realm is an object-oriented database that stores data as objects with properties and relationships, making it easier to work with data in an application. On the other hand, Redis is a key-value store that operates with simple data structures like strings, lists, sets, and hashes.
Persistence: Realm offers built-in support for offline data synchronization, meaning data can be stored locally and then synced with a server when a connection is available. Redis, on the other hand, is an in-memory database that can optionally persist data to disk.
Scalability: Redis is known for its high performance and scalability, making it a preferred choice for applications requiring fast read and write operations. Realm, on the other hand, may not be as performant as Redis in scenarios where massive scalability is required.
Data Querying: Redis supports various data querying options through its powerful set of commands, making it suitable for scenarios that require complex data manipulation and analysis. Realm, on the other hand, may be more suitable for simpler data querying needs within the context of an application.
Deployment: Redis is often used as a standalone server or as a cluster for high availability and scalability. Realm, on the other hand, is typically integrated within the application codebase, simplifying deployment but potentially limiting scalability options.
Use Cases: Realm is commonly used in mobile and IoT applications where offline capabilities are vital, while Redis is often implemented in high-performance scenarios like caching, session management, real-time analytics, and message queues.

In Summary, Realm and Redis differ in their data models, persistence mechanisms, scalability, querying capabilities, deployment options, and target use cases.

Realm vs Redis

Overview

Realm vs Redis: What are the differences?