Microservices: REST vs Messaging : <p>I heard Amazon uses HTTP for its microservice based architecture. An alternative is to use a messaging system like RabbitMQ or Solace systems. I personally have experience with Solace based microservice architecture, but never with REST. <br>
Any idea what do various big league implementations like Amazon, Netflix, UK Gov etc use?<br>
Other aspect is, in microservices, following things are required (besides others):<br>
* Pattern matching<br>
* Async messaging.. receiving system may be down<br>
* Publish subscribe<br>
* Cache load event.. i.e. on start up, a service may need to load all data from a couple of other services, and should be notified when data is completely loaded, so that it can 'know' that it is now ready to service requests
<br>
These aspects are naturally done with messaging rather than REST. Why should anyone use REST (except for public API). Thanks.</p>
