

MechWarrior 2: 31st Century Combat
It had an archive in the game. It detailed the social structure, military structure, customs, and history of the Clans, which you play as a member of, from an outside perspective. I was only 8, but I read through the whole thing, end-to-end. I put an album of it on Facebook for posterity when I was in high school.
I decided I wanted to be like them when I read it. I have a much better understanding of them now, and I do not agree with everything. The concepts behind some core tenants still stand for me. Individuals are valued within the context of the Clan. One’s value is based on their contribution to society, but society must value them in order to expect their contribution. If a leader acts in their own interest and not that of the Clan, their subordinates are obligated to challenge them. If the conflict stands, they face in a Circle of Equals. Generally, personal disputes are delayed and adjudicated, but there is a Trial of Grievance if the parties can conduct if they cannot delay. In the real world, I translate these to a value in community, a mandate to not tolerate poor leadership, and good practice in letting cooldown time followed by direct dispute resolve conflict.
Of course, there are questionable things. A caste system, though some Clans allow more mobility than others. Eugenics based on combat prowess for the warrior caste. Promotion by combat for the warrior caste. Poor military strategy based on the concept of honor.
I still consider myself a Clanner, to some degree. Sometimes I try to see if others took it as much to heart as I did, but I am afraid of rejection. I do not know if I could pass various Trials. I know I am too old, now, or at the very least, approaching that. Maybe someday, I will find other children of Kerensky.
I’ve worked with Swarm in a startup setting. It was an absolute nightmare. We eventually gave up and moved to Kubernetes.
That said, your use case does sound simpler. As I recall, we had to set up service discovery (with Hashicorp Consul) and secret management (with Hashicorp Vault) ourselves. I believe we also used Traefik for load balancing. There were other components as well, but I don’t remember it all. This was over 5 years ago, though.
The difficulty wasn’t configuring each piece but getting them to work together. There was also the time burned learning all the different tools. Kubernetes is great because everything is meant to work together.
But if it’s just two machines with separate configuration, do you even need orchestration? Is there a lot of overhead to just manage them individually?
Unfortunately, it was too long ago to remember the details of differences between compose and swarm. I do remember it was a very trivial conversion.