DBMS > Bangdb vs. Linter vs. SiteWhere vs. SQLite

System Properties Comparison Bangdb vs. Linter vs. SiteWhere vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

RDBMS for high security requirements

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Graph DBMS
Time Series DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.16
Rank	#338	Overall
	#47	Document stores
	#32	Graph DBMS
	#31	Time Series DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

bangdb.com

linter.ru

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

docs.bangdb.com

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

Sachin Sinha, BangDB

relex.ru

SiteWhere

Dwayne Richard Hipp

Initial release

2012

1990

2010

2000

Current release

BangDB 2.0, October 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

BSD 3

commercial

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C, C++

C and C++

Java

Server operating systems

Linux

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

Linux
OS X
Windows

server-less

Data scheme

schema-free

yes

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

yes

not rigid because of 'dynamic typing' concept.

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

yes

SQL-92 is not fully supported

APIs and other access methods

Proprietary protocol
RESTful HTTP API

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

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Java
Python

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

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

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes, Notifications (with Streaming only)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

none

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Source-replica replication

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

via file-system locks

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

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

yes, run db with in-memory only mode

yes

User concepts

Access control

yes (enterprise version only)

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.