title: Reduce the use of feign calls in micro-services architecture
body: <p>So far I've been studying micro-services architecture and decoupling a monolithic monster.<br>
  I'm currently using feign clients in order to make easy the conversation between micro-services.<br>
  As I'm neck level immersed in the code of my monolithic application, I found that I’m using way too much feign calls, the thing that is compromising my dream of a totally decoupled application with independent micro-services.</p>
  
  <p>So my question is about gathering ideas or just opinions; because on the internet it's just rainbows and flowers about feign, no one is noticing that after all, it's coupled, because micro-service A won't deliver any answer unless it receives data from B. </p>
  
  <p>So can you think of any way that maybe reduces feign calls? Or do you even see it as a drawback to micro-services architecture ?</p>