Difference between Valentina Server and YugabyteDB

1. YugabyteDB :
It is 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. It is distributed and developed as an Apache 2.0 open source project.

2. Valentina Server :
It is an Object-relational database and reports server and fast object-relational database server. It includes integrated database servers, Valentina Database Server, and SQLite Database Server. It is a full-featured, standards-compliant multi-user access SQLite based database server.

Difference between Valentina Server and YugabyteDB :

Valentina Server	YugabyteDB
It is developed by Paradigma Software and initially released on 1994.	It is developed by Yugabyte Inc. and initially released on 2017 and current release on March 2020.
Its server operating systems of Valentina Server is Linux, OS X, Windows.	Its server operating systems of YugabyteDB is Linux, OS X.
Its primary database model is Relational DBMS.	Its primary database model is Relational DBMS.
Absence of Secondary database models in Valentina Server	Secondary database models of YugabyteDB is Document store and Wide column store
It supports .Net, C, C#, C++, Objective-C, PHP, Ruby, Visual Basic, Visual Basic.NET, programming languages.	It supports C, C#, C++, Go, Java, JavaScript (Node.js), Python, Ruby programming languages.
APIs and other access methods of Valentina Server is ODBC.	It supports YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language.
It has Data Schema.	Data scheme of YugabyteDB is depending on used data model.
It doesn’t has Implementation language-C# .	Implementation language of YugabyteDB is C and C++.
Absence of Transaction concepts in Valentina Server.	Its Transaction concepts is Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.
Absence of Replication methods.	Replication methods of YugabyteDB is based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability.
It doesn’t hold Consistency concept.	It has strong consistency on writes and tunable consistency on reads.