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++

C#, .NET, .NET Core, Java

C and C++

Server operating systems

FreeBSD
Linux
macOS
Windows

Linux
Windows

BSD
Linux
macOS

Data scheme

Fixed schema

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes

partial

Supported data types are Lists, Queues, Hashsets, Dictionary and Counter

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-like query syntax and LINQ for searching the cache. Cache Synchronization with SQL Server using SQL dependency.

Full-featured ANSI SQL support

APIs and other access methods

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

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

IDistributedCache
JCache
LINQ
Proprietary native API

Open binary protocol

Supported programming languages

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

.Net
.Net Core
C#
Java
JavaScript (Node.js)
Python
Scala

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

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

support for stored procedures with SQL-Server CLR

Lua, C and SQL stored procedures

Triggers

yes

Notifications

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

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

yes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

yes, but depending on the SQL-Server Edition

yes, with selectable consistency level

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency
Strong Eventual Consistency over WAN with Conflict Resolution using Bridge Topology

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

optimistic locking and pessimistic locking

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

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

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

Authentication to access the cache via Active Directory/LDAP (possible roles: user, administrator)

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

NCache has been the market leader in .NET Distributed Caching since 2005 . NCache...
» more

Competitive advantages

NCache is 100% .NET/ .NET Core based which fully supports ASP.NET Core Sessions ,...
» more

Typical application scenarios

NCache enables industries like retail, finance, banking IoT, travel, ecommerce, healthcare...
» more

Key customers

Bank of America, Citi, Natures Way, Charter Spectrum, Barclays, Henry Schein, GBM,...
» more

Market metrics

Market Leader in .NET Distributed Caching since 2005.
» more

Licensing and pricing models

NCache Open Source is free on an as-is basis without any support. NCache Enterprise...
» more

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.