DBMS > Faircom DB vs. Google Cloud Datastore vs. Pinecone

System Properties Comparison Faircom DB vs. Google Cloud Datastore vs. Pinecone

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A managed, cloud-native vector database

Primary database model

Key-value store
Relational DBMS

Document store

Vector DBMS

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

Score	0.18
Rank	#314	Overall
	#45	Key-value stores
	#141	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	3.02
Rank	#87	Overall
	#3	Vector DBMS

Website

www.faircom.com/products/faircom-db

cloud.google.com/datastore

www.pinecone.io

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

cloud.google.com/datastore/docs

docs.pinecone.io/docs/overview

Developer

FairCom Corporation

Google

Pinecone Systems, Inc

Initial release

1979

2008

2019

Current release

V13, July 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

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

ANSI C, C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

hosted

Data scheme

schema free, schema optional, schema required, partial schema,

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes, details here

String, Number, Boolean

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.

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

SQL-like query language (GQL)

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Python

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication using Paxos

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

DB-Engines blog posts

Vector databases
2 June 2023, Matthias Gelbmann

show all

Recent citations in the news

Best cloud storage of 2024
13 September 2024, TechRadar

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
30 July 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Google App Engine
26 April 2024, TechTarget

17 Top Cloud Storage Companies to Know
9 April 2024, Built In

provided by Google News

Using the Pinecone vector database in .NET
12 September 2024, InfoWorld

Pinecone serverless goes multicloud as vector database market heats up
27 August 2024, VentureBeat

Pinecone launches its serverless vector database out of preview
21 May 2024, TechCrunch

Pinecone launches serverless vector database on Azure, GCP
27 August 2024, TechTarget

Pinecone vector database available on AWS, Azure, and Google clouds
27 August 2024, Blocks & Files

provided by Google News

Share this page