DBMS > BoltDB vs. Ignite vs. PostGIS

System Properties Comparison BoltDB vs. Ignite vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	BoltDB  Xexclude from comparison	Ignite  Xexclude from comparison	PostGIS  Xexclude from comparison
Description	An embedded key-value store for Go.	Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.	Spatial extension of PostgreSQL
Primary database model	Key-value store	Key-value store Relational DBMS	Spatial DBMS
Secondary database models			Relational DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart	Score 0.57 Rank #224   Overall #34   Key-value stores	Score 6.85 Rank #62   Overall #7   Key-value stores #35   Relational DBMS	Score 30.88 Rank #28   Overall #1   Spatial DBMS
Website	github.com/­boltdb/­bolt	ignite.apache.org	postgis.net
Technical documentation		apacheignite.readme.io/­docs	postgis.net/­documentation
Developer		Apache Software Foundation
Initial release	2013	2015	2005
Current release		Apache Ignite 2.6	3.2.1, February 2022
License Commercial or Open Source	Open Source MIT License	Open Source Apache 2.0	Open Source GPL v2.0
Cloud-based only Only available as a cloud service	no	no	no
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language	Go	C++, Java, .Net	C
Server operating systems	BSD Linux OS X Solaris Windows	Linux OS X Solaris Windows
Data scheme	schema-free	yes	yes
Typing predefined data types such as float or date	no	yes	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.	no	yes	yes
Secondary indexes	no	yes	yes
SQL Support of SQL	no	ANSI-99 for query and DML statements, subset of DDL	yes
APIs and other access methods		HDFS API Hibernate JCache JDBC ODBC Proprietary protocol RESTful HTTP API Spring Data
Supported programming languages	Go	C# C++ Java PHP Python Ruby Scala
Server-side scripts Stored procedures	no	yes (compute grid and cache interceptors can be used instead)	user defined functions
Triggers	no	yes (cache interceptors and events)	yes
Partitioning methods Methods for storing different data on different nodes	none	Sharding	yes based on PostgreSQL
Replication methods Methods for redundantly storing data on multiple nodes	none	yes (replicated cache)	yes based on PostgreSQL
MapReduce Offers an API for user-defined Map/Reduce methods	no	yes (compute grid and hadoop accelerator)	no
Consistency concepts Methods to ensure consistency in a distributed system	none	Immediate Consistency	Immediate Consistency
Foreign keys Referential integrity	no	no	yes
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	yes	ACID	ACID
Concurrency Support for concurrent manipulation of data	yes	yes	yes
Durability Support for making data persistent	yes	yes	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	no	yes	no
User concepts Access control	no	Security Hooks for custom implementations	yes based on PostgreSQL
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
	BoltDB	Ignite	PostGIS
DB-Engines blog posts