DBMS > Brytlyt vs. Google Cloud Bigtable vs. OpenEdge vs. SQLite

System Properties Comparison Brytlyt vs. Google Cloud Bigtable vs. OpenEdge vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Application development environment with integrated database management system

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store
Wide column store

Relational DBMS

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

brytlyt.io

cloud.google.com/bigtable

www.progress.com/openedge

www.sqlite.org

Technical documentation

docs.brytlyt.io

cloud.google.com/bigtable/docs

documentation.progress.com/output/ua/OpenEdge_latest

www.sqlite.org/docs.html

Developer

Brytlyt

Google

Progress Software Corporation

Dwayne Richard Hipp

Initial release

2016

2015

1984

2000

Current release

5.0, August 2023

OpenEdge 12.2, March 2020

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Public Domain

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

C, C++ and CUDA

Server operating systems

Linux
OS X
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

SQL-92 is not fully supported

APIs and other access methods

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

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C#
C++
Go
Java
JavaScript (Node.js)
Python

Progress proprietary ABL (Advanced Business Language)

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Internal replication in Colossus, and regional replication between two clusters in different zones

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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

Users and groups

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.