DBMS > Graphite vs. PostGIS vs. SAP HANA vs. Solr vs. Sqrrl

System Properties Comparison Graphite vs. PostGIS vs. SAP HANA vs. Solr vs. Sqrrl

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Spatial extension of PostgreSQL

In-memory, column based data store. Available as appliance or cloud service

A widely used distributed, scalable search engine based on Apache Lucene

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Relational DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

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

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

github.com/graphite-project/graphite-web

postgis.net

www.sap.com/products/hana.html

solr.apache.org

sqrrl.com

Technical documentation

graphite.readthedocs.io

postgis.net/documentation

help.sap.com/hana

solr.apache.org/resources.html

Developer

Chris Davis

SAP

Apache Software Foundation

Amazon

originally Sqrrl Data, Inc.

Initial release

2006

2005

2010

2006

2012

Current release

3.4.2, February 2024

2.0 SPS07 (April 4, 2023), April 2023

9.6.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL v2.0

commercial

Open Source

Apache Version 2

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Python

Java

Server operating systems

Linux
Unix

Appliance or cloud-service

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

schema-free

Typing

predefined data types such as float or date

Numeric data only

yes

supports customizable data types and automatic typing

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

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

HTTP API
Sockets

JDBC
ODBC

Java API
RESTful HTTP/JSON API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

yes

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on PostgreSQL

yes

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

locking

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

yes

based on PostgreSQL

yes

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.