This is actually why I think we need more cloud and not less. The problem is poorly designed code, not monolith or microservice. For example, ValidationService

This is actually why I think we need more cloud and not less. The problem is poorly designed code, not monolith or microservice. For example, ValidationService as described above could be replaced with OpenPolicyAgent and would scale much better. That said, I could see someone pointing at OpenPolicyAgent and asking why they didn’t separate distributed updates from the policy spec as two distinct projects, this way you could re-use parts of OPA to distribute config files or feature flags. You can now too, but it requires the extra hop of compiling a function to answer. Come to think of it, distributed state updating is roughly the same general problem that Kubernetes Operator pattern solves. Another way of putting it, we have cloud primitives but not enough of them, maybe - or they aren’t well enough explained - to make the choices or restrictions of different architectures a bit more obvious? I especially look forward to a future when we get “design systems” for the programming we do with business logic in the cloud. I’m over-emphasizing cloud here. I mean code you don’t directly have to maintain and write regardless of where it runs or who wrote it.