Building Microservices with Go

Push messaging

Rather than using a queue, sometimes, you may want a service to act immediately on an event. Your service subscribes to receive messages from a broker such as NATS.io or SNS. When the broker receives a message, dispatched from another service, then the broker notifies all the registered services by making a call to the registered endpoint, sending it a copy of the message. The receiver will generally disconnect once the message has been received and assumes that the message processes correctly. This pattern allows the message broker extreme throughput. In the case of NATS.io, a single server instance can deliver millions of messages per second. Should the client be unable to process the message, then it must handle the logic ...