Publish-Subscribe Pattern: In this pattern, a microservice publishes a message to a topic, and any other microservices that have subscribed to that topic receive the message. The response may include the requested data or an error message if the request cannot be fulfilled. Request-Response Pattern: In this pattern, a microservice sends a request message to another microservice and waits for a response message. You can use queues for many things, rabbitmq gives you AMQP, which is the bedrock of how microservices talk to each other. This isn't a large implementation, and it won't grow - so the ins/outs are fairly known/estimateable. Right now, just exploring options between MQ and DB is where I am at. Thank you all for the suggestions - I will take a look into RabbitMQ and MassTransit.Īs for the DB comments, there is no DB currently in place, and using a DB is not out of the question. But that does incurr additional overhead for message management.Īnyone have any reliable suggestions for message queueing? Of course, using a database to log and control is always an option. The largest complaint I've seen is that the queue(s) may go down/stop responding without notice. I have been doing some research, and it seems like folks are split on using Microsoft Message Queues. Thus, the use of a message queue would help alleviate having lost messages. NET endpoints), but those systems may or may not answer at a given time (due to system instability, etc.). I have a situation where I need to be able to pass messages between systems (using.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |