title: Is it alright to manually write microservice adapters in Spring?
body: <p>So I've been working on a microservice-based architecture in Spring and my prototype uses Spring's <code>WebClient</code> to explicitly send a request to a different service and await a response. Recently I've tried to migrate the project to some RPC-based service remoting technology, and I figured out that all the technologies that just work out of the box (Hessian, RMI, HTTP Method Invoker) are deprecated, and the ones that Spring encourages to use (JAX WS and Spring WS) require to learn multiple additional DSLs and spend a week trying to deeply understand their principles just to export a service to the web. Also, just using <code>WebClient</code> feels far more flexible and seems to leave a lot of room for further improvements. Will creating my own REST-like APIs for each of the microservices and then explicitly using <code>WebClient</code> to call them turn my code into instant legacy spaghetti mess or is it a normal thing to do?</p>
  <p>P.S. By &quot;more flexible&quot; I mean, for example, an ability to set up a reverse proxy load balancer with caching and different actions for different methods in between the actual microservice nodes and the requesting service, etc.</p>