DBMS > FatDB vs. Google Cloud Datastore vs. Sphinx vs. STSdb

System Properties Comparison FatDB vs. Google Cloud Datastore vs. Sphinx vs. STSdb

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

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Open source search engine for searching in data from different sources, e.g. relational databases

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Key-value store

Document store

Search engine

Key-value store

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

cloud.google.com/datastore

sphinxsearch.com

github.com/STSSoft/STSdb4

Technical documentation

cloud.google.com/datastore/docs

sphinxsearch.com/docs

Developer

FatCloud

Google

Sphinx Technologies Inc.

STS Soft SC

Initial release

2012

2008

2001

2011

Current release

3.5.1, February 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

GPLv2, commercial license 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.

Implementation language

C++

Server operating systems

Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

primitive types and user defined types (classes)

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

full-text index on all search fields

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language (GQL)

SQL-like query language (SphinxQL)

APIs and other access methods

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

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Proprietary protocol

.NET Client API

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
Java

Server-side scripts

Stored procedures

yes

via applications

using Google App Engine

Triggers

yes

via applications

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Can implement custom security layer via applications

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

The DB-Engines ranking includes now search engines
4 February 2013, Paul Andlinger

show all

Recent citations in the news

Best cloud storage of 2024
29 April 2024, TechRadar

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

What Is Google Cloud Platform?
28 August 2023, Simplilearn

provided by Google News

Switching From Sphinx to MkDocs Documentation — What Did I Gain and Lose
2 February 2024, Towards Data Science

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

Perplexity AI: From Its Use To Operation, Everything You Need To Know About Googles Newest Challenger
11 January 2024, Free Press Journal

The Pirate Bay was recently down for over a week due to a DDoS attack
29 October 2019, The Hacker News

How to Build 600+ Links in One Month
4 September 2020, Search Engine Journal

provided by Google News

Share this page