DBMS > EJDB vs. Faircom EDGE vs. Geode

System Properties Comparison EJDB vs. Faircom EDGE vs. Geode

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Primary database model

Document store

Key-value store
Relational DBMS

Key-value store

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Website

github.com/Softmotions/ejdb

www.faircom.com/products/faircom-edge

geode.apache.org

Technical documentation

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

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

geode.apache.org/docs

Developer

Softmotions

FairCom Corporation

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Initial release

2012

1979

2002

Current release

V3, October 2020

1.1, February 2017

License

Commercial or Open Source

Open Source

GPLv2

commercial

Restricted, free version available

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

ANSI C, C++

Java

Server operating systems

server-less

Android
Linux

ARM, x86
Raspbian
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes, ANSI Standard SQL Types

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

yes

ANSI SQL queries

SQL-like query language (OQL)

APIs and other access methods

in-process shared library

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

Supported programming languages

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

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

.Net
All JVM based languages
C++
Groovy
Java
Scala

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning

Customizable business rules for partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Synchronous and asynchronous realtime replication based on transaction logs

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Eventual Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

when using SQL

Transaction concepts

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

ACID

yes, on a single node

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

across SQL and NoSQL

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

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Access rights per client and object definable

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

Recent citations in the news

FairCom kicks off new era of database technology USA - English
10 November 2020, PR Newswire

Winners of the 2021 IoT Evolution Product of the Year Awards Announced
6 July 2021, IoT Evolution World

Trend-Setting Products in Data and Information Management for 2023
8 December 2022, Database Trends and Applications

How To Collect, Store, and Query IoT Data With MQTT + SQL
16 June 2022, IoT For All

Trend-Setting Products in Data and Information Management for 2024
6 December 2023, Database Trends and Applications

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Share this page