mysql replication, which fork to choose?

Question

MySQL

Good afternoon.
Problem: The geographic distribution of the mysql(master-master) database is required.
I read a lot about comparing forks for synchronous replication, and I realized that the choice is rather between percona and mariadb, since mariadb is being developed by a non-commercial organization and requires disabling selinux, all other ~ equal reviews, I would be the first to try to implement percona.
But to solve geographically distributed replication, asynchronous is needed, I think so, and on this topic I can not find a good comparison. I suspect that modified innodb repositories for forks will still give better performance and stability.
I'm more concerned about data consistency than performance. I already have a little experience in implementing asynchronous oracle mysql master-master with GTID, I set it up for experimental purposes on a project with attendance of ~ 600 uniques per day, deploying 2 database containers on one virtual machine. There are few visitors, but CMS 1C Bitrix has a frequently changed table with user sessions, and every 2-4 days I receive a letter that this table contains 1032, 1062. Consistency does not matter for this table, ok, but what will happen on the project with ~ 40t and for example tables of web forms xs.
Please share your experience of implementing asynchronous mysql. The story about the synchronous one is also welcomed separately. :)

Answer 1

I would think that if the project has not yet started working and does not have a couple of million records in the tables, PostgreSQL would be the best choice - now it is a standard that is practically not inferior to Oracle in terms of functionality