History[03][01]

HyPer is a DBMS project from the Technical University of Munich (TUM) database group. In the beginning, their objective was to build a hybrid in-memory database; during the process of developing HyPer, they published lots of paper about different parts of the system. HyPer is not open source, but it provides a WebInterface (http://hyper-db.de/interface.html) where we could execute queries on the HyPer system. HyPer is still in active development and the next big step of the HyPer group is to extend the functionality of HyPer to "exploratory workflows that are deeply integrated into the database kernel".

Checkpoints[04]

HyPer creates consistent backups and checkpoints by taking efficient snapshots.

Concurrency Control[05][06]

HyPer used MVCC scheme to handle both OLTP and OLAP queries.

Data Model[07][06]

HyPer is not a non-relational database (a.k.a NoSQL database) like MongoDB which is document-oriented database or HBase which uses column family; instead, HyPer is a relational database; however, the relations are not always maintained as arrays of entire records; the table layout in HyPer would change according to the workload, so HyPer is also the so-called New-SOL database.

Foreign Keys[05]

No documentations from HyPer specifically state that HyPer supports foreign key constrains, but in their fast serializable MVCC paper, they mentioned a senario where an transacion deletes a primary key and another concurrent transacion inserts a foreign key which refers to that primary key.

Indexes[08][09]

The adaptive radix tree (ART) index is the default indexing structure in HyPer. Two important features of ART are adaptive node structure and path compression.

Isolation Levels[04][05]

HyPer supports a novel serializability validation mechanism which is adapted from precision locking. Instead of tracking dependencies like the Serializable Snapshot Isolation (SSI) implemented in PostgreSQL, HyPer would "read predicates and validate the predicates against the undo log entries".

Joins[10][11]

It's positive that HyPer supports sort-merge joins; as for the hash join, they implemented a NUMA-aware hash join algorithm, but they didn't mentioned whether they have integrated hash join into HyPer or not.

Logging[04]

HyPer uses physical logging to support data durability.

Query Compilation[12][13]

HyPer uses Just-In-Time (JIT) code compilation to compile transacions and queries into efficient LLVM assembly code.

Query Execution[12]

Query Interface[14][15]

HyPer uses SQL or a PL/SQL-like scripting language to execute queries

Storage Architecture[06]

As described in the HyPer homepage, "HyPer is a main-memory-based relational DBMS for mixed OLTP and OLAP workloads."

Storage Model[07]

In HyPer, the storage layout would change according to the access patterns; for OLTP workload, it uses row store approach by organizing relations as arrays of entire records; as for the OLAP workload, it uses column store approach by partitioning relations into vactors of attribute values.

Stored Procedures[04]

The stored procedures in HyPer are written in a custom, iterator-free language called HyPerScript.

System Architecture[16]

ScyPer (Scaled-out HyPer) is a version of HyPer, which horizontally scales out on shared-nothing commodity hardware

Views[04]

HyPer supports normal views where a query would define a virtual table.