Since Grails 3 mvc binds the request/response to the controller, I/O state can't be shared with other services in a distributed microservice architecture.
How does Grails propose sharing I/O state in a distributed microservice architecture without massive duplication so that edge cases can handle functionality early and late.
For example, if the proxy wanted to do checking based on the rules for the endpoint (ie what roles are associated, what request method is associated, what data should be sent with request, etc) and reject or forward, it should be able to and also synchronize the data should changes be made at the source. Same with MQ or other services.
Also, loopbacks should be able to be done without the request having to go out and come back in to the service; there should be a level of autonomy.
How does Grails handle this?