Riak vs FoundationDB | What are the differences?

Overview

Riak

Stacks104

Followers137

Votes44

GitHub Stars4.0K

Forks535

FoundationDB

Stacks34

Followers79

Votes21

FoundationDB vs Riak: What are the differences?

FoundationDB: Multi-model database with particularly strong fault tolerance, performance, and operational ease. FoundationDB is a NoSQL database with a shared nothing architecture. Designed around a "core" ordered key-value database, additional features and data models are supplied in layers. The key-value database, as well as all layers, supports full, cross-key and cross-server ACID transactions; Riak: A distributed, decentralized data storage system. Riak is a distributed database designed to deliver maximum data availability by distributing data across multiple servers. As long as your client can reach one Riak server, it should be able to write data. In most failure scenarios, the data you want to read should be available, although it may not be the most up-to-date version of that data.

FoundationDB and Riak belong to "Databases" category of the tech stack.

"ACID transactions" is the top reason why over 2 developers like FoundationDB, while over 9 developers mention "High Performance " as the leading cause for choosing Riak.

Riak is an open source tool with 3.24K GitHub stars and 530 GitHub forks. Here's a link to Riak's open source repository on GitHub.

🔥 Trending in Databases on StackShare

pgvector Databases

Open-source vector similarity search for Postgres

Try it View Docs Alternatives

Try

189

7

Advice on Riak, FoundationDB

Karan

Senior Software Developer at Shyplite

Jan 13, 2022

Decided

So, we started using foundationDB for an OLAP system although the inbuilt tools for some core things like aggregation and filtering were negligible, with the high through put of the DB, we were able to handle it on the application. The system has been running pretty well for the past 6 months, although the data load isn’t very high yet, the performance is fairly promising

40.9k views40.9k

Comments

Detailed Comparison

Riak	FoundationDB
Riak is a distributed database designed to deliver maximum data availability by distributing data across multiple servers. As long as your client can reach one Riak server, it should be able to write data. In most failure scenarios, the data you want to read should be available, although it may not be the most up-to-date version of that data.	FoundationDB is a NoSQL database with a shared nothing architecture. Designed around a "core" ordered key-value database, additional features and data models are supplied in layers. The key-value database, as well as all layers, supports full, cross-key and cross-server ACID transactions.
-	Multiple data models;Full, multi-key ACID transactions;No locking;Bindings available in Python, Ruby, Node, PHP, Java, Go, and C
Statistics
GitHub Stars 4.0K	GitHub Stars -
GitHub Forks 535	GitHub Forks -
Stacks 104	Stacks 34
Followers 137	Followers 79
Votes 44	Votes 21
Pros & Cons
Pros 14 High Performance 11 High Availability 9 Easy Scalability 5 Flexible 1 Distributed	Pros 6 ACID transactions 5 Linear scalability 3 Key-Value Store 3 Multi-model database 3 Great Foundation

What are some alternatives to Riak, FoundationDB?

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.