NATS provides a built-in load balancing feature, called distributed queue. Using the subscriber queue balance between a set of messaging subscribers, these subscribers may be used to provide fault-tolerant applications and extensions workloads.
To create a queue subscription, subscribers will registration queue name. All subscribers with the same queue name constitutes queues. It requires no configuration. When you publish a message registered topic, one randomly selected members of the group to receive messages. Although a plurality of subscriber queues, each message is only used by one.
Queue group name follows the same naming convention theme. Most importantly, they are case-sensitive, can not contain spaces. Consider the use of layering of the queues. Some server functions can use wildcard matching on them.
An important feature of NATS is set by the application queue and queue subscriber defined, rather than the configuration defined by the publisher.
Queue Subscribers are ideal for extended services. Extended service and running another application as simple, narrow and clear operation request is signaled to terminate the application. This flexibility and does not require any configuration changes to make to become an excellent service NATS communications technology, can work with all platform technology.
By reading queuing the Tutorial , using real-time queue server attempts to self-NATS subscription.
