How does Go avoid getting bogged down by middleware-oriented programing in practice? I think most large-scale programming in organizations tend to converge on that because it sort of works.
Is it that people who like this kind of stuff write microservices for deployment on Kubernetes clusters?
Go itself doesn't do anything about that, nor does Java or JS dictate anything about using middleware.
I can't speak for the ecosystem / developers though; there are plenty of examples where e.g. HTTP request handlers are wrapped in several onion layers of middleware itself. But, there's also an emphasis on keeping things simple and lightweight.
What kind of middleware are you thinking of when you mention things getting bogged down?
Is it that people who like this kind of stuff write microservices for deployment on Kubernetes clusters?