DBMS > EJDB vs. GeoMesa vs. searchxml vs. Spark SQL vs. Transbase

System Properties Comparison EJDB vs. GeoMesa vs. searchxml vs. Spark SQL vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

DBMS for structured and unstructured content wrapped with an application server

Spark SQL is a component on top of 'Spark Core' for structured data processing

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store

Spatial DBMS

Native XML DBMS
Search engine

Relational DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

github.com/Softmotions/ejdb

www.geomesa.org

www.searchxml.net/category/products

spark.apache.org/sql

www.transaction.de/en/products/transbase.html

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

www.geomesa.org/documentation/stable/user/index.html

www.searchxml.net/support/handouts

spark.apache.org/docs/latest/sql-programming-guide.html

www.transaction.de/en/products/transbase/features.html

Developer

Softmotions

CCRi and others

informationpartners gmbh

Apache Software Foundation

Transaction Software GmbH

Initial release

2012

2014

2015

2014

1987

Current release

5.0.0, May 2024

1.0

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.0

commercial

free development license

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

Scala

C++

Scala

C and C++

Server operating systems

server-less

Windows

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

in-process shared library

RESTful HTTP API
WebDAV
XQuery
XSLT

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C++

most other programming languages supported via APIs

Java
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

on the application server

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes

sychronisation to multiple collections

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

multiple readers, single writer

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write 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.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

Domain, group and role-based access control at the document level and for application services

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Use Amazon Athena with Spark SQL for your open-source transactional table formats | Amazon Web Services
24 January 2024, AWS Blog

What is Apache Spark? The big data platform that crushed Hadoop
3 April 2024, InfoWorld

Cracking the Apache Spark Interview: 80+ Top Questions and Answers for 2024
1 April 2024, Simplilearn

Performant IPv4 Range Spark Joins | by Jean-Claude Cote
24 January 2024, Towards Data Science

Run Apache Hive workloads using Spark SQL with Amazon EMR on EKS | Amazon Web Services
18 October 2023, AWS Blog

provided by Google News

Share this page