DBMS > Lovefield vs. Microsoft Azure AI Search vs. Postgres-XL vs. Snowflake vs. TerarkDB

System Properties Comparison Lovefield vs. Microsoft Azure AI Search vs. Postgres-XL vs. Snowflake vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Embeddable relational database for web apps written in pure JavaScript

Search-as-a-service for web and mobile app development

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Cloud-based data warehousing service for structured and semi-structured data

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Vector DBMS

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	5.52
Rank	#59	Overall
	#6	Search engines

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

google.github.io/lovefield

azure.microsoft.com/en-us/services/search

www.postgres-xl.org

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

learn.microsoft.com/en-us/azure/search

www.postgres-xl.org/documentation

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

Microsoft

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2014

2015

2014

since 2012, originally named StormDB

2014

2016

Current release

2.1.12, February 2017

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Mozilla public license

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

hosted

Linux
macOS

hosted

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

XML type, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

distributed, parallel query execution

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

JavaScript

C#
Java
JavaScript
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

Triggers

Using read-only observers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

User concepts

Access control

yes

using Azure authentication

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.