By and big, if you need to have a databases, you can get to for one particular of the huge names—MySQL/MariaDB, PostgreSQL, SQLite, MongoDB—and get to perform. But in some cases the one particular-dimension-matches-all tactic does not in shape all. Each now and then your use circumstance falls down concerning barstools, and you need to have to get to for a little something a lot more specialized. In this article are 9 offbeat databases that operate the gamut from in-memory analytics to crucial-price merchants and time-sequence systems.


The phrase “SQL OLAP system” frequently conjures images of data-crunching monoliths or sprawling data warehouse clusters. DuckDB is to analytical databases what SQLlite is to MySQL and PostgreSQL. It isn’t built to operate at the similar scale as whole-blown OLAP alternatives, but to give speedy, in-memory analytical processing for nearby datasets.

Quite a few of DuckDB’s characteristics are counterparts to what is uncovered in larger OLAP solutions, even if smaller in scale. Data is saved as columns instead than rows, and question processing is vectorized to make the best use of CPU caching. You will not come across considerably in the way of indigenous connectivity to reporting alternatives like Tableau, but it should not be complicated to roll this sort of a resolution manually. Aside from bindings for C++, DuckDB also connects natively to two of the most frequent programming environments for analytics, Python and R.


“Edge” is a expression made use of in graph databases to refer to the link or relationship concerning two entities or nodes (this sort of as concerning a buyer and an buy, or concerning an buy and a solution, and many others.) of a very connected dataset. EdgeDB uses the PostgreSQL main and all the qualities it gives (like ACID transactions and industrial-power reliability) to develop what its makers phone an “object-relational database” with solid industry varieties and a SQL-like question language. 

Thus EdgeDB combines NoSQL-like ease of use and immediacy, the relational modeling ability of a graph databases, and the guarantees and regularity of SQL. Even nevertheless EdgeDB is not formally a document databases, you can use it to retail store data that way. And you can use the GraphQL question language to quickly retrieve data from EdgeDB, just as you can with indigenous graph databases this sort of as Neo4j.


An open source task spearheaded by Apple, FoundationDB is a “multi-model” databases that merchants data internally as crucial-price pairs (fundamentally the NoSQL design), but can be organized into relational tables, graphs, files, and several other data buildings. ACID transactions ensure data integrity, and horizontal scaling and replication are both equally readily available out of the box. FoundationDB’s layout comes with some rigid constraints, nevertheless: keys, values, and transactions all have challenging dimension limits, and transactions have challenging time limits as very well.


The intention guiding HarperDB is to give a solitary databases for managing structured and unstructured data in an enterprise—somewhere concerning a multi-design databases like FoundationDB and a data warehouse or OLAP resolution. Ingested data is deduplicated and made readily available for queries by means of the interface of your selection: SQL, NoSQL, Excel, and many others. BI alternatives like Tableau or Power BI can integrate specifically with HarperDB with no the data needing to be extracted or processed. Equally business and group editions are readily available.

[ Also on InfoWorld: How to opt for the correct databases for your application ]


As popular and highly effective as Redis is, the in-memory crucial-price retail store has been criticized for slipping quick in threaded efficiency and ease of use. KeyDB is protocol-suitable with Redis, so can be made use of as a fall-in alternative. But KeyDB adds some nifty under-the-hood enhancements, chiefly multithreading for network I/O operations and question parsing. Strategies for the following edition of Redis, Redis 6, consist of threaded I/O as very well, but KeyDB is readily available now.


A solution of Uber’s inside engineering staff, M3DB is a distributed time-sequence databases that is made use of in Uber’s metrics system (fundamentally as a data retail store for Prometheus). Borrowing suggestions from Apache Cassandra and a Facebook task named “Gorilla,” M3DB lets arbitrary time precision, out-of-buy insertions, and configurable levels of replication and examine regularity. However, the creators take note that M3DB could not be ideal for all time-sequence databases use scenarios. For occasion, M3DB can not insert data out of buy past a specified time window (the default is two hrs), and it is primarily optimized for storing and retrieving 64-little bit floats instead than other types of data.


The identify implies a fusion of the Redis in-memory crucial-price retail store and SQL question abilities, and that’s exactly what RediSQL is — precisely, a Redis module that embeds a SQLite databases. Data is saved transparently in Redis, so Redis handles persistency and in-memory processing. Each individual databases is associated with a Redis crucial, so you can have several SQL databases on a solitary Redis occasion. Queries to individuals databases are typical SQL, passed via the typical Redis API. You can also create and precompile statements (fundamentally saved processes) in RediSQL to velocity up question execution. Equally business and open source editions are readily available.


SQLite is a minimal miracle: an embeddable open source databases that is lightning-speedy and extremely-trusted. SQLite would make a excellent default selection whenever you need to have a databases in a solitary-consumer application, but SQLite situations are limited to a solitary node.

RQLite builds on SQLite to create a distributed databases procedure. Setting up several nodes is simple, and data instantly replicates across individuals nodes using the Raft consensus algorithm. RQLite also gives encryption concerning nodes and a discovery support that would make it simple to insert nodes instantly. But RQLite also has a several disadvantages: Write speeds are slower than in SQLite, and only deterministic SQL functions—i.e., individuals guaranteed to create the similar end result on just about every node—are safe to use.


Most large-conclusion databases these times have some sort of in-memory performance, even if it entails a little something like desk pinning (e.g., SQL Server). UmbraDB, an analytics databases that can operate as a fall-in alternative for PostgreSQL, is built to use in-memory processing whenever it can. When it can not, it makes use of a novel variable-dimension page mechanism for paging data from storage. Long-functioning queries are optimized for execution with LLVM. 

Copyright © 2020 IDG Communications, Inc.