DBMS > jBASE vs. Lovefield vs. PostGIS

System Properties Comparison jBASE vs. Lovefield vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	jBASE  Xexclude from comparison	Lovefield  Xexclude from comparison	PostGIS  Xexclude from comparison
Description	A robust multi-value DBMS comprising development tools and middleware	Embeddable relational database for web apps written in pure JavaScript	Spatial extension of PostgreSQL
Primary database model	Multivalue DBMS	Relational DBMS	Spatial DBMS
Secondary database models			Relational DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart	Score 1.71 Rank #136   Overall #3   Multivalue DBMS	Score 0.23 Rank #286   Overall #134   Relational DBMS	Score 31.68 Rank #28   Overall #1   Spatial DBMS
Website	www.jbase.com	google.github.io/­lovefield	postgis.net
Technical documentation	docs.zumasys.com/­jbase	github.com/­google/­lovefield/­blob/­master/­docs/­spec_index.md	postgis.net/­documentation
Developer	Zumasys	Google
Initial release	1991	2014	2005
Current release	5.7	2.1.12, February 2017	3.2.1, February 2022
License Commercial or Open Source	commercial	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		JavaScript	C
Server operating systems	AIX Linux Windows	server-less, requires a JavaScript environment (browser, Node.js) tested with Chrome, Firefox, IE, Safari
Data scheme	schema-free	yes	yes
Typing predefined data types such as float or date	optional	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.	yes	no	yes
Secondary indexes		yes	yes
SQL Support of SQL	Embedded SQL for jBASE in BASIC	SQL-like query language via JavaScript builder pattern	yes
APIs and other access methods	JDBC ODBC Proprietary protocol RESTful HTTP API SOAP-based API
Supported programming languages	.Net Basic Jabbascript Java	JavaScript
Server-side scripts Stored procedures	yes	no	user defined functions
Triggers	yes	Using read-only observers	yes
Partitioning methods Methods for storing different data on different nodes	Sharding	none	yes based on PostgreSQL
Replication methods Methods for redundantly storing data on multiple nodes	yes	none	yes based on PostgreSQL
MapReduce Offers an API for user-defined Map/Reduce methods	no	no	no
Consistency concepts Methods to ensure consistency in a distributed system			Immediate Consistency
Foreign keys Referential integrity	no	yes	yes
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	ACID	ACID	ACID
Concurrency Support for concurrent manipulation of data	yes	yes	yes
Durability Support for making data persistent	yes	yes, by using IndexedDB or the cloud service Firebase Realtime Database	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	yes	yes using MemoryDB	no
User concepts Access control	Access rights can be defined down to the item level	no	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
	jBASE	Lovefield	PostGIS
DB-Engines blog posts