DBMS > AlaSQL vs. Amazon Neptune vs. FatDB vs. Infobright

System Properties Comparison AlaSQL vs. Amazon Neptune vs. FatDB vs. Infobright

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

JavaScript DBMS library

Fast, reliable graph database built for the cloud

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Primary database model

Document store
Relational DBMS

Graph DBMS
RDF store

Document store
Key-value store

Relational DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Website

alasql.org

aws.amazon.com/neptune

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

github.com/AlaSQL/alasql

aws.amazon.com/neptune/developer-resources

Developer

Andrey Gershun & Mathias R. Wulff

Amazon

FatCloud

Ignite Technologies Inc.; formerly InfoBright Inc.

Initial release

2014

2017

2012

2005

License

Commercial or Open Source

Open Source

MIT-License

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

JavaScript

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

Knowledge Grid Technology used instead

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

Via inetgration in SQL Server

yes

APIs and other access methods

JavaScript API

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
JDBC
ODBC

Supported programming languages

JavaScript

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

selectable replication factor

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

with encyption-at-rest

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 and roles can be defined via the AWS Identity and Access Management (IAM)

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Multi faceted data exploration in the browser using Leaflet and amCharts
3 May 2020, Towards Data Science

provided by Google News

AWS announces Amazon Neptune I/O-Optimized
22 February 2024, AWS Blog

Analyze large amounts of graph data to get insights and find trends with Amazon Neptune Analytics | Amazon Web ...
29 November 2023, AWS Blog

Amazon Neptune Analytics is now generally available
29 November 2023, AWS Blog

Amazon Neptune Analytics is now available in the AWS Europe (London) Region
14 March 2024, AWS Blog

Create a Virtual Knowledge Graph with Amazon Neptune and an Amazon S3 data lake | Amazon Web Services
21 February 2024, AWS Blog

provided by Google News

Share this page