DBMS > Fujitsu Enterprise Postgres vs. Memcached vs. Snowflake vs. Splunk

System Properties Comparison Fujitsu Enterprise Postgres vs. Memcached vs. Snowflake vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-grade PostgreSQL-based DBMS with security enhancements such as Transparent Data Encryption and Data Masking, plus high-availability and performance improvement features.

In-memory key-value store, originally intended for caching

Cloud-based data warehousing service for structured and semi-structured data

Analytics Platform for Big Data

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.31
Rank	#285	Overall
	#129	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.postgresql.fastware.com

www.memcached.org

www.snowflake.com

www.splunk.com

Technical documentation

www.postgresql.fastware.com/product-manuals

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

PostgreSQL Global Development Group, Fujitsu Australia Software Technology

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

Splunk Inc.

Initial release

2003

2014

2003

Current release

Fujitsu Enterprise Postgres 14, January 2022

1.6.27, May 2024

License

Commercial or Open Source

commercial

Open Source

BSD license

commercial

Limited free edition and free developer edition 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

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Proprietary protocol

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

partitioning by range, list and by hash

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

yes

Multi-source replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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.

User concepts

Access control

fine grained access rights according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

100% compatible with community PostgreSQL
» more

Competitive advantages

Built-in TDE and Data Masking security. In-Memory Columnar Index, and a high speed...
» more

Typical application scenarios

Transactional payments applications, reporting and mixed workloads.
» more

Market metrics

Over 30 years experience in database technology. Over 20 years in Postgres development...
» more

Licensing and pricing models

Core based licensing
» 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.