Hi James,
Orchestrator is written in go so might work in Windows. I know of no-one who has run it there. All the users I’m aware of (but I talk to very few) use Linux.
If you need this to work on Windows I’d bet it might fail in weird ways. By all means try that, but I suspect you may be disappointed.
Group replication is not asynchronous: the changes written to the primary will be agreed by all members before being accepted so the data on all member nodes should be the same. Depending on the exact configuration the changes made on the primary may not be committed at exactly the same time but they have been received by other nodes so should the primary fail and a new primary get elected you’ll have all the data you expect to see.
Related to orchestrator if you use it with semi-sync replication you still need to configure that and then configure the integration and failover behaviour of Orchestrator on the cluster.
The setup last time I looked was pretty well documented, Shlomi did a good job, but it is a complex piece of software to setup first time. If you want to use it take your time and I’m sure you’ll figure it out.
I’ve been using it for a very long time and am very happy with it on the systems I manage.
Hope that helps clarify you question.
Regards,
Simon