nanoservice is a small Python library for writing lightweight networked services using nanomsg. With nanoservice you can break up monolithic applications into small, specialized services which communicate with each other.
For Gentoo use the package available in portage: dev-libs/nanomsg. There is also a Launchpad PPA with packages built for Ubuntu LTS releases: xenial, bionic, and focal.
If no packages are available for your Linux platform, install manually:
$ git clone [email protected]:nanomsg/nanomsg.git $ ./configure $ make $ make check $ sudo make install
For more details visit the official nanomsg GitHub repo.
On OS X you can also do:
$ brew install nanomsg
On Gentoo you can use this portage overlay otherwise install it from the usual Ubuntu repos (or use the PPA above for a xenial backport, still named python3-msgpack).
Note the name change upstream has a "transitional" package so when
upgrading from msgpack-0.4 or earlier, don’t do pip install -U msgpack-python.
If upgrading as above, do:
$ pip uninstall msgpack-python; pip install msgpack
Otherwise just do:
$ pip install msgpack
On Gentoo you can use this portage overlay otherwise use the PPA above for Ubuntu.
Alternatively, from the project directory:
$ make install
Or via pip:
$ pip install nanoservice (it's broken)
The service:
from nanoservice import Responder
def echo(msg):
return msg
s = Responder('ipc:///tmp/service.sock', timeouts=(None, None))
s.register('echo', echo)
s.start()
$ python echo_service.py
The client:
from nanoservice import Requester
c = Requester('ipc:///tmp/service.sock', timeouts=(None, None))
res, err = c.call('echo', 'hello world’)
print('Result is {}'.format(res))
$ python my_client.py $ Result is: hello world
To run tests, first install tox (see Testing Notes below) then run:
$ make test
To run benchmarks:
$ make bench
Check out the examples directory for more examples.
Tests using python multiprocessing have been separated out into their own directory (test2) due to sporadic failures triggering NanoMsgAPIError exceptions, Address already in use followed by Connection timed out (the unittest-based tests are still under the test directory).
Although random failures are occasionally seen in travis-ci tests, all tests should run successfully with tox and pytest on the desktop as well as package builds (ie, using FEATURES="test" in portage with -userpriv).
MIT Licensed