DBMS > GridGain vs. Microsoft SQL Server vs. Solr vs. SWC-DB

System Properties Comparison GridGain vs. Microsoft SQL Server vs. Solr vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GridGain is an in-memory computing platform, built on Apache Ignite

Microsofts flagship relational DBMS

A widely used distributed, scalable search engine based on Apache Lucene

A high performance, scalable Wide Column DBMS

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Search engine

Wide column store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Spatial DBMS

Time Series DBMS

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

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	44.28
Rank	#24	Overall
	#3	Search engines

Score	0.01
Rank	#387	Overall
	#13	Wide column stores

Website

www.gridgain.com

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

solr.apache.org

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

www.gridgain.com/docs/index.html

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

solr.apache.org/resources.html

Developer

GridGain Systems, Inc.

Microsoft

Apache Software Foundation

Alex Kashirin

Initial release

2007

1989

2006

2020

Current release

GridGain 8.5.1

SQL Server 2022, November 2022

9.5.0, February 2024

0.5, April 2021

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache Version 2

Open Source

GPL V3

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

Java, C++, .Net

C++

Java

C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

Solr Parallel SQL Interface

SQL-like query language

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

Java API
RESTful HTTP/JSON API

Proprietary protocol
Thrift

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

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

Java plugins

Triggers

yes (cache interceptors and events)

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

yes, but depending on the SQL-Server Edition

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

yes

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.