Hi @catblast, (I am the CTO of Yugabyte) Your points are all completely valid. Just wanted to add my 2 cents. With YugabyteDB specifically, we are more than j

Hi @catblast, (I am the CTO of Yugabyte) Your points are all completely valid. Just wanted to add my 2 cents. With YugabyteDB specifically, we are more than just PostgreSQL wire-compatible, we "reuse" the upper half of PostgreSQL to support almost all PG features (examples: stored procedures, triggers, partial functions, etc). So the aim is to build something that has "almost all PG features" while being able to "run cloud-native - with HA, scale and geo-distribution" - our hope is that this allows YugabyteDB to really become a viable option instead of PostgreSQL when apps are being built for the cloud. Here is a blog post on the benefits we realized reusing PostgreSQL: https://blog.yugabyte.com/why-we-built-yugabytedb-by-reusing-the-postgresql-query-layer/ https://blog.yugabyte.com/why-we-built-yugabytedb-by-reusing...