DBMS > Amazon CloudSearch vs. EJDB vs. EXASOL vs. FatDB vs. Microsoft SQL Server

System Properties Comparison Amazon CloudSearch vs. EJDB vs. EXASOL vs. FatDB vs. Microsoft SQL Server

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

A hosted search engine service by Amazon with the data stored in Amazons cloud

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Microsofts flagship relational DBMS

Primary database model

Search engine

Document store

Relational DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

aws.amazon.com/cloudsearch

github.com/Softmotions/ejdb

www.exasol.com

www.microsoft.com/en-us/sql-server

Technical documentation

docs.aws.amazon.com/cloudsearch

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

www.exasol.com/resources

learn.microsoft.com/en-US/sql/sql-server

Developer

Amazon

Softmotions

Exasol

FatCloud

Microsoft

Initial release

2012

2000

2012

1989

Current release

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

restricted free version is available

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Server operating systems

hosted

server-less

Windows

Linux
Windows

Data scheme

yes

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

all search fields are automatically indexed

yes

SQL

Support of SQL

yes

Via inetgration in SQL Server

yes

APIs and other access methods

HTTP API

in-process shared library

.Net
JDBC
ODBC
WebSocket

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

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

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

Java
Lua
Python
R

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

yes

via applications

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

none

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

none

selectable replication factor

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

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

ACID

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.

yes

User concepts

Access control

authentication via encrypted signatures

Access rights for users, groups and roles according to SQL-standard

Can implement custom security layer via applications

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.