Is it possible to implement microservices with oData.net
<p>I've been reading about the <a href="http://microservices.io/patterns/microservices.html" rel="nofollow">Microservice Architecure</a> and with the limited valuable information available on internet, I believe, I have a fair understanding of it from the theory point of view. I understand that on a high level this architecture suggests to move away from <a href="http://microservices.io/patterns/monolithic.html" rel="nofollow">monoliths</a> and have small, independent services. However, all the examples that I see on the internet are suggesting to write loosely coupled windows services (daemons in case of non MS implementations) connected to an <a href="https://en.wikipedia.org/wiki/Enterprise_service_bus" rel="nofollow">ESB</a>. I understand that writing small, loosely coupled web services that adhere to <a href="https://en.wikipedia.org/wiki/Single_responsibility_principle" rel="nofollow">SRP</a> also fits the bill of micro services.</p>

<p>That said, oData.Net services, where all oData controllers (micro services?) are deployed as a monolith, is a clear violation of the Microservices Architecure pattern. Is it a correct statement to make that oData.net is not designed to work as micro services? If your answer is no then please explain with help of a an example. Also, help me understand, how to have the API gateway pattern in the mix.</p>