DBMS > Google BigQuery vs. LeanXcale vs. Linter vs. SingleStore

System Properties Comparison Google BigQuery vs. LeanXcale vs. Linter vs. SingleStore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

RDBMS for high security requirements

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.35
Rank	#283	Overall
	#41	Key-value stores
	#128	Relational DBMS

Score	0.10
Rank	#350	Overall
	#153	Relational DBMS

Score	5.91
Rank	#61	Overall
	#34	Relational DBMS

Website

cloud.google.com/bigquery

www.leanxcale.com

linter.ru

www.singlestore.com

Technical documentation

cloud.google.com/bigquery/docs

docs.singlestore.com

Developer

Google

LeanXcale

relex.ru

SingleStore Inc.

Initial release

2010

2015

1990

2013

Current release

8.5, January 2024

License

Commercial or Open Source

commercial

free developer edition 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.

SingleStoreDB Cloud: The world's fastest, modern cloud database for both operational (OLTP) and analytical (OLAP) workloads. Available instantly with multi-cloud and hybrid-cloud capabilities

Implementation language

C and C++

C++, Go

Server operating systems

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

64 bit version required

Data scheme

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

through Apache Derby

yes

but no triggers and foreign keys

APIs and other access methods

RESTful HTTP/JSON API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
Java
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

In-memory capabilities

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

yes

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Fine grained access control via users, groups and roles

More information provided by the system vendor

Specific characteristics

SingleStore offers a fully-managed , distributed, highly-scalable SQL database designed...
» more

Competitive advantages

SingleStore’s competitive advantages include: Easy and Simplified Architecture with...
» more

Typical application scenarios

Driving Fast Analytics: SingleStore delivers the fastest and most scalable reporting...
» more

Key customers

IEX Cloud : Improves Financial Data Distribution Speed 15x with Singlestore DB Comcast,...
» more

Market metrics

Customers in various industries worldwide including US and International Industry...
» more

Licensing and pricing models

F ree Tier and Enterprise Edition
» more

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.