Skip to main content

NATS messaging system client using Twisted #microservices

Project description

License MIT

NATS Documentation

HOW TO microservice communication.

How do I get my services to talk to each other with out registering each one in a directory?

How do I scale a back end service and allow front end services to use all of them quickly?

How do I have a fast, scalable, resilient communication service with out a lot of headaches?

A good answer to all of these is to use NATS. NATS is a masterpiece protocol designed with the cloud in mind. HTTP was good, but it was designed for servers sending single resources to clients on an uncontrolled network.

Install dependencies

I suggest creating a virtualenv.

$ make deps

Try the demo:

$ make prepare-example

Open two extra terminal windows and from one run:

$ ./example/

from the other run:

$ ./example/

Then from the first window run:



Make a subject subscriber.

for full context see

First, define a message handler for a subscription:

def on_happy_msg(nats_protocol, sid, subject, reply_to, payload):
    print "got message", sid, subject

Then in create the endpoint, nats protocol instance and connect them:

point = TCP4ClientEndpoint(reactor, "", 4222)

nats_protocol =
    on_connect=lambda np: np.sub("happy", "6", on_msg=on_happy_msg))

connecting = connectProtocol(point, nats_protocol)

When a message comes in for the subject “happy” on_happy_msg will be called.

Make a subject responder.

The only difference from a subscriber is that the on_msg function will publish a message to the reply_to subject of the message:

def respond_on_msg(nats_protocol, sid, subject, reply_to, payload):
    if reply_to:, "Roger, from {}!".format(responder_id))


nats_protocol =
    on_connect=lambda np: np.sub("get-response", "6", on_msg=respond_on_msg))

For full context see

Distribute the responder load.

To distribute the load: subscribe with a queue-group and any message will go to one of the responders:

nats_protocol =
    on_connect=lambda np: np.sub("get-response", "6",

However many processes you have subscribed to this subject and queue group will have the messages sent to only one of them. If there are four running, and 100 messages are sent on the “get-response” subject, each one should only have to respond to 25, distributing the work load.

For full context see and something that will make a bunch of requests on that subject.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

txnats-0.7.5.tar.gz (15.6 kB view hashes)

Uploaded source

Built Distributions

txnats-0.7.5.macosx-10.10-x86_64.exe (82.1 kB view hashes)

Uploaded any

txnats-0.7.5-py3.5.egg (38.0 kB view hashes)

Uploaded 3 5

txnats-0.7.5-py2.7.egg (37.1 kB view hashes)

Uploaded 2 7

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page