For example, for local testing, in our Quick Start docs section, we have info for: mac/linux, involving just downloading and unpacking the release and you should be good to go; for local docker, you can download our control script; for k8s download our sample yml.
Finally, for non-local testing, we have a Deploy > Manual Deployment section, highlighting the 3 steps for downloading YugaByte, bringing up Masters (metadata nodes) and then Tservers (data nodes).
Note: I work at YugaByte.
With YugaByteDB: I needed to think about master and tserver nodes, to run them and connect them separately. There was no clear guide that had "run these three docker command on the three different nodes" and be done with it.
Note: I run everything is in simple docker images (and not compose, not swarm, not kubernates, just plain docker images).
Most other databases insist on multiple layers and dependencies which only shifts more work onto developers who have to install and maintain it.
> People are begging for a good and easy psql HA cluster setup for ages
I've been using Stolon in production for a bit, and while not a native solution- it works quite well.
To use a solution like Stolon would require changes in the core logic to dynamically re-configure whatever sharing plugin you use.
I doubt that the same will be done with PostgreSQL or MariaDB anytime soon. People are begging for a good and easy psql HA cluster setup for ages, and it is just not happening (yeah, they are getting closer and closer), while such DBs fill a need with good results.