DBMS > Graph Engine vs. Tigris

System Properties Comparison Graph Engine vs. Tigris

Please select another system to include it in the comparison.

Our visitors often compare Graph Engine and Tigris with Redis and Databricks.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Graph DBMS
Key-value store

Document store
Key-value store
Search engine
Time Series DBMS

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

Score	0.54
Rank	#240	Overall
	#21	Graph DBMS
	#33	Key-value stores

Score	0.04
Rank	#355	Overall
	#50	Document stores
	#52	Key-value stores
	#23	Search engines
	#35	Time Series DBMS

Website

www.graphengine.io

www.tigrisdata.com

Technical documentation

www.graphengine.io/docs/manual

www.tigrisdata.com/docs

Developer

Microsoft

Tigris Data, Inc.

Initial release

2010

2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2.0

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

.NET and C

Server operating systems

.NET

Linux
macOS
Windows

Data scheme

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

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

C#
C++
F#
Visual Basic

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes, using FoundationDB

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

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

Trinity
30 October 2010, microsoft.com

Preview Version of the New Microsoft Academic Search Engine is Now Online, API Also Available
29 February 2016, LJ INFOdocket

The graph analytics landscape 2019
27 February 2019, Data Science Central

IBM releases Graph, a service that can outperform SQL databases
27 July 2016, GeekWire

How Google and Microsoft taught search to “understand” the Web
6 June 2012, Ars Technica

provided by Google News

Investing in Tigris
20 February 2024, Andreessen Horowitz

provided by Google News

Share this page