Thanks for your response. Alas, Go is not an option for me ... I only have access to Java programmers. They know Spring Boot better than I do, but their systems

Thanks for your response. Alas, Go is not an option for me ... I only have access to Java programmers. They know Spring Boot better than I do, but their systems reek of complexity, and I suspect that is because there is a huge weight of enterprise practices that they feel they should conform to. For example, in a latency critical path, I identified 4 microservices in a chain; it seemed to me that all one needs in that situation -- they all have similar scaling needs -- is a simple modular structure where one module enqueues an in-memory request for the next task in the chain. No json, no network etc. Their response? "Monolith bad, microservice good". If you want microservice, spring boot it is. And they must be packaged with docker, and managed by a cluster manager. I blame the complexity of these enterprise models because they lead these engineers to believe that simple solutions are not possible.