windows services - Asp.Net Web API with a message bus/queue -


i experimenting implementing micro service architecture on rest service developing. rest service communicate third party soap service , component creating perform additional business rules validation. plan split application 3 distinct components: web api clients send requests, windows service call third party soap service , windows service perform business rules validation. planning on using combination of actor model (akka.net) along message bus (nservicebus or rabbitmq + mass transit).

from understand, messaging meant fire , forget commands, cannot used web api project clients expecting response call api , not sure how await receiving message bus/queue in client request web api there need away web api listen event bus in request.

my question is, correct in understanding of how messaging queues operate? and, have use akka.net based micro service accept calls web api , return response api?

technically can use request-response, see example here. however, approach should used caution, in legacy apps or in specific situations situation requires it.

generally though benefit messaging, reliability , scalability, should redesign solution asynchronous. if need response use request-response pattern (i.e. send 2 one-way messages instead of using callbacks), or technologies such signalr. here , here webinars talking connecting front-end apps messaging in more detail, hope you'll find them helpful.


Comments

Popular posts from this blog

php - Vagrant up error - Uncaught Reflection Exception: Class DOMDocument does not exist -

vue.js - Create hooks for automated testing -

Add new key value to json node in java -