DBMS > Axibase vs. Blueflood vs. Google Cloud Datastore vs. SQLite vs. Weaviate

System Properties Comparison Axibase vs. Blueflood vs. Google Cloud Datastore vs. SQLite vs. Weaviate

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Scalable TimeSeries DBMS based on Cassandra

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Widely used embeddable, in-process RDBMS

An AI-native realtime vector database engine that integrates scalable machine learning models.

Primary database model

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

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.73
Rank	#143	Overall
	#5	Vector DBMS

Website

axibase.com/docs/atsd/finance

blueflood.io

cloud.google.com/datastore

www.sqlite.org

github.com/weaviate/weaviate
weaviate.io

Technical documentation

github.com/rax-maas/blueflood/wiki

cloud.google.com/datastore/docs

www.sqlite.org/docs.html

weaviate.io/developers/weaviate

Developer

Axibase Corporation

Rackspace

Google

Dwayne Richard Hipp

Weaviate B.V.

Initial release

2013

2008

2000

2019

Current release

15585

3.46.0 (23 May 2024), May 2024

1.19, May 2023

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

Apache 2.0

commercial

Open Source

Public Domain

Open Source

commercial license available with Weaviate Enterprise

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

Java

Server operating systems

Linux

Linux
OS X

hosted

server-less

Data scheme

yes

predefined scheme

schema-free

yes

dynamic column types

yes, maps to GraphQL interface

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

yes, details here

yes

not rigid because of 'dynamic typing' concept.

yes

string, int, float, geo point, date, cross reference, fuzzy references

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

all data objects are indexed in a semantic vector space (the Contextionary), all primitive fields are indexed

SQL

Support of SQL

SQL-like query language

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

GraphQL is used as query language

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

HTTP REST

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL query language
RESTful HTTP/JSON API

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

JavaScript / TypeScript
Python

Server-side scripts

Stored procedures

yes

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on Cassandra

Multi-source replication using Paxos

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

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 rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

API Keys
OpenID Connect Discovery

More information provided by the system vendor

Specific characteristics

Weaviate is an open source vector database that is robust, scalable, cloud-native,...
» more

Competitive advantages

Flexible deployment - Free, open source or fully-managed cloud vector database service...
» more

Typical application scenarios

As a database supporting the development of generative AI and semantic search applications...
» more

Key customers

All companies that have data.
» more

Market metrics

As of mid 2023: Over 2 million open source downloads 3500+ Weaviate Slack community...
» more

Licensing and pricing models

Weaviate is open-source, and free to use. Weaviate is also available as a fully managed...
» 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.