By “fast HTTP” I guess you mean highly concurrent HTTP, as in making or servicing lots of requests at the same time. Nameko can certainly do that.
Do you want the Nameko service to be the client or the server?
As a server – you will get good performance out of Nameko’s HTTP decorator as long as you increase the default worker pool size. Set the
max_workers config key to something large.
As a client – Eventlet has excellent support for making concurrent web requests. See https://eventlet.net/doc/examples.html#web-crawler for a simple example. Again you’ll want to set the pool size to something suitable.
I don’t know about the performance characteristics of
aiohttp vs Nameko. A bare
aiohttp implementation is probably faster in terms of the CPU cycles it spends processing a single request, but perhaps not enough to matter, depending on your use case.