History[02]

Vetica was founded by Michael Stonebraker and Andrew Palmer in 2015. It is derived from C-Store, which is a prototype developed by MIT, Brown, and few other universities. It was acquired by Hewlett Packard in 2011 and joined Micro Focus in 2017 due to the merger between Micro Focus and HP.

Checkpoints[03][04]

In Vertica, each node maintains checkpoints and transaction logs separately. The synchronization duration can be tuned by users as well. For a single-node failure, it can be from other nodes. If all nodes fail, it can be recovered to the earliest checkpoints when all nodes are good. new transaction log cannot be appended, if a new checkpoint starts.

Compression[05]

Both Run-Length Encoding and Delta encoding are used in Vertica. RLE encoding is only used when the number of repetition is large. Delta encoding works for INTEGER/DATE/TIME/TIMESTAMP/INTERVAL type, where the variations from the smallest value are stored instead of the real values.

Concurrency Control[06][07]

Vertica supports MVCC to achieve data consistency. Both current and previous status are stored and visible to transactions. Transaction isolations can be achieved since no conflict between the read and write operations exist. A shared-nothing MPP architecture is used in Vertica, which can prevent the overheads caused by locks.

Data Model[08]

Columnar store is used in Vertica to improve the performance of sequential access by sacrificing the performance of single record. Compared with row-oriented databases which scan the whole table, only few columns are retrieved based on given queries in Vertica, which can improve throughput by reducing disk I/O costs.

Foreign Keys[09]

Vertica allows users to use foreign key constraints. Foreign keys should be defined when tables are created or using "ALTER TABLE".

Isolation Levels[10]

Read Committed and Serializable are used in Vertica. Read Committed is the default isolation level. Read Uncommitted and Repeatable Read are treated automatically as Read Committed and Serializable respectively.

Joins[11]

Both merge join and hash join are supported in Vertica. Merge Join is faster in general and requires less memory, but pre-sorted data is required.Hash join requires more memory, but it is faster if the inner table can fit in the memory.

Query Compilation

Query Interface

Storage Architecture[12]

Hybrid data store are supported in Vertica. Write Optimized Store(WOS) is about storing data in memory, which does not support compression and indexing. Read Optimized Store(ROS) is about storing data on disk, where data is sorted and segmented.

Storage Model[12]

Data is stored in Vertica in column format to improve the performance of read operations, since a lot of amount of disk I/O can be prevented.

Storage Organization[13]

Containers are used in Vertica to store data. And WOS (Write Optimized Storage) and ROS (Read Optimized Storage) are two existing types.

Stored Procedures[14]

System Architecture[08][15]

Shared-nothing architecture is used in Vertica, where all nodes don't share anything in terms of memory and disk storage. Shared-nothing architecture are easier to scale, since there is no race or contention between nodes. Moreover, massively Parallel Processing (MPP) architecture is used in Vertica to improve the throughput of joins requiring multiple machines together.

Views[04]

The projections in Vertica are similar to materialized view in other databases. Projections can be created on the same table so that some optimizations such as pre-storing required data can be done for some specific queries.