Difference Between ToroDB and YugabyteDB
Last Updated :
27 Jul, 2020
1. ToroDB :
It is a MongoDB-compatible JSON document store, built on top of PostgreSQL and it is a technology designed to fulfill the gap between document oriented and SQL databases. It is an open source NoSQL database that runs on top of a RDBMS which is compatible with MongoDB protocol and APIs. ToroDB is an open source project that reads a NoSQL document, automatically infers its structure, and transforms it into a set of tables and columns that represent the data into a relational form.
2. YugabyteDB :
It is a high-performance, cloud native and open source distributed SQL database globally-distributed document store. YugabyteDB aims to make applications agile. Yugabyte is headquartered in Sunnyvale, CA. It is distributed and developed as an Apache 2.0 open source project .
Difference between YugabyteDB and ToroDB :
S.No. |
ToroDB |
YugabyteDB |
1 |
Developed by 8Kdata and initially released on 2016. |
Developed by Yugabyte Inc. and initially released on 2017. Current release on March 2020. |
2 |
All OS with a Java 7 VM is server, operating systems of ToroDB. |
Linux, OS X are server operating systems of YugabyteDB . |
3 |
Primary database model is Document store. |
Primary database model is Relational DBMS. |
4 |
Absence of Secondary database models in ToroDB . |
Secondary database models is Document store and Wide column store. |
5 |
Absence of any supported programming languages. |
C, C#, C++, Go, Java, JavaScript (Node.js), Python, Ruby are supporting programming languages. |
6 |
Absence of APIs and other access methods in ToroDB. |
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language, APIs and other access methods. |
7 |
It has schema-free Data Schema. |
Data scheme is depending on used data model. |
8 |
Its Implementation language is Java. |
Implementation language of YugabyteDB is C and C++. |
9 |
Absence of Transaction concepts in ToroDB. |
Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture is Transaction concepts. |
10 |
Master-slave replication methods in ToroDB. |
Replication methods is based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability. |
11 |
It has Eventual Consistency and Immediate Consistency concept. |
Strong consistency on writes and tunable consistency on reads is consistency concept in YugabyteDB. |
12 |
It has no concept of Foreign keys. |
But it has concepts of Foreign keys. |
Like Article
Suggest improvement
Share your thoughts in the comments
Please Login to comment...