Difference between Yaacomo and YugabyteDB

1. YugabyteDB :
It is the open source, cloud native and high-performance distributed SQL database globally-distributed document store. It aims to make applications agile. Yugabyte is headquartered in Sunnyvale, CA. YugabyteDB is distributed and developed as an Apache 2.0 open source project.

Yaacomo :
It is a Relational, OpenCL based in-memory database management system for real-time analytics and big data solutions was developed as a plug-and-play solution. Yaacomo is designed for efficiently utilizing the hardware via parallel computing.

Difference between Yaacomo and YugabyteDB :

S.NO.	Yaacomo	YugabyteDB
1.	Developed by Q2WEB GmbH and initially released on 2009.	Developed by Yugabyte Inc. and initially released on 2017 and current release on March 2020.
2.	Server operating systems of Yaacomo is Android, Linux, Windows.	Server operating systems of YugabyteDB is Linux, OS X.
3.	Its primary database model is Relational DBMS.	Its primary database model is Relational DBMS.
4.	It does not support any programming languages.	YugabyteDB supports C, C#, C++, Go, Java, JavaScript (Node.js), Python, Ruby programming languages.
5.	APIs and other access methods of Yaacomo is JDBC, ODBC.	YugabyteDB supports YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language.
6.	Yaacomo has a Data Schema.	Data scheme of YugabyteDB is depending on used data model.
7.	It doesn’t has any Implementation language.	Implementation language of YugabyteDB is C and C++.
8.	Its Transaction concepts is ACID (Atomicity, Consistency, Isolation, and Durability).	Its Transaction concepts is Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.
9.	Replication methods of Yaacomo is Master-slave replication.	Replication methods of YugabyteDB is based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability.
10.	Yaacomo has Immediate Consistency concept.	YugabyteDB has strong consistency on writes and unable consistency on reads.