# Latest

**URL:** https://discourse.nameko.io/latest.md

[Latest](https://discourse.nameko.io/latest.md) · [Categories](https://discourse.nameko.io/categories.md)

---

## [Welcome to Nameko's Discourse](https://discourse.nameko.io/t/welcome-to-namekos-discourse/8)

<div class="topic-metadata">

**Author:** [@system](https://discourse.nameko.io/u/system)\
**Replies:** 0\
**Last updated:** [August 1, 2018, 5:13pm UTC](https://discourse.nameko.io/t/welcome-to-namekos-discourse/8 "2018-08-01T17:13:11Z")

</div>

Welcome! This is the support site for Nameko. You’ll find frequently asked questions and answers here to help you use the framework. .

---

## [Kontiki, a microservices framework in Python](https://discourse.nameko.io/t/kontiki-a-microservices-framework-in-python/820)

<div class="topic-metadata">

**Author:** [@Jpk](https://discourse.nameko.io/u/Jpk)\
**Replies:** 0\
**Last updated:** [March 19, 2026, 7:27pm UTC](https://discourse.nameko.io/t/kontiki-a-microservices-framework-in-python/820 "2026-03-19T19:27:18Z")

</div>

Hello, I’ve just released Kontiki, a Python microservices framework built on AMQP and asyncio.It is inspired by Nameko’s design principles, which I found very elegant, and aims to provide a coherent, production-usable d…

---

## [Girolle a Rust rpc lib](https://discourse.nameko.io/t/girolle-a-rust-rpc-lib/807)

<div class="topic-metadata">

**Author:** [@doubleailes](https://discourse.nameko.io/u/doubleailes)\
**Replies:** 0\
**Last updated:** [June 29, 2024, 9:20am UTC](https://discourse.nameko.io/t/girolle-a-rust-rpc-lib/807 "2024-06-29T09:20:07Z")

</div>

Hi, I start to learn Rust on my freetime since 2 years. And one of my pet project is a rust lib compliant with certain feature of Nameko, really inspire from rusty-celery. This project is Girolle. Girolle is far from be…

---

## [How to handle external websockets?](https://discourse.nameko.io/t/how-to-handle-external-websockets/352)

<div class="topic-metadata">

**Author:** [@No\_Split\_Sherlock](https://discourse.nameko.io/u/No_Split_Sherlock)\
**Replies:** 3\
**Last updated:** [June 10, 2024, 1:06pm UTC](https://discourse.nameko.io/t/how-to-handle-external-websockets/352 "2024-06-10T13:06:01Z")

</div>

Hey there! I’m quite new to microservices and Nameko. I hope someone can help me. I’m trying to open multiple websocket clients that receive external datastreams. I want to be able to (at some point) maybe interact with…

---

## [Implement reverse proxy in nameko http route](https://discourse.nameko.io/t/implement-reverse-proxy-in-nameko-http-route/797)

<div class="topic-metadata">

**Author:** [@alihossein](https://discourse.nameko.io/u/alihossein)\
**Replies:** 0\
**Last updated:** [July 1, 2023, 9:13am UTC](https://discourse.nameko.io/t/implement-reverse-proxy-in-nameko-http-route/797 "2023-07-01T09:13:42Z")

</div>

Hi. I want to implement a reverse proxy in the Nameko framework but I don’t know how I can do it. I did it in the FastApi framework: @app.get("/test") async def proxy(request: Request): try: os\_headers = \[…

---

## [Are concurrently running methods the same as workers?](https://discourse.nameko.io/t/are-concurrently-running-methods-the-same-as-workers/793)

<div class="topic-metadata">

**Author:** [@NirPisatto](https://discourse.nameko.io/u/NirPisatto)\
**Replies:** 0\
**Last updated:** [May 2, 2023, 12:28am UTC](https://discourse.nameko.io/t/are-concurrently-running-methods-the-same-as-workers/793 "2023-05-02T00:28:37Z")

</div>

As the default max\_workers is 10,Does this mean that a service class method can execute up to 10 methods at once? Since in my case, I used “nameko run” to up a service class and what I observed that only one method was …

---

## [Is it possible to dispatch event asynchronously without waiting?](https://discourse.nameko.io/t/is-it-possible-to-dispatch-event-asynchronously-without-waiting/792)

<div class="topic-metadata">

**Author:** [@NirPisatto](https://discourse.nameko.io/u/NirPisatto)\
**Replies:** 5\
**Last updated:** [April 22, 2023, 7:47pm UTC](https://discourse.nameko.io/t/is-it-possible-to-dispatch-event-asynchronously-without-waiting/792 "2023-04-22T19:47:04Z")

</div>

One of my event listening task (event\_handler) is taking long time to processing. So is there any way to emit the event and let it work as async function without await? Thank !!

---

## [How different nameko run proccesses share one listen socket?](https://discourse.nameko.io/t/how-different-nameko-run-proccesses-share-one-listen-socket/785)

<div class="topic-metadata">

**Author:** [@litmax](https://discourse.nameko.io/u/litmax)\
**Replies:** 2\
**Last updated:** [February 27, 2023, 11:30am UTC](https://discourse.nameko.io/t/how-different-nameko-run-proccesses-share-one-listen-socket/785 "2023-02-27T11:30:51Z")

</div>

Hi folks! I am trying to understand how things work behind the scene. When I run a service that uses HttpEntrypoint it binds to port 8000 and handles requests. When I start another process in my opinion it is supposed…

---

## [Service that dynamically spawns and kills managed threads?](https://discourse.nameko.io/t/service-that-dynamically-spawns-and-kills-managed-threads/787)

<div class="topic-metadata">

**Author:** [@mhirota-impinj](https://discourse.nameko.io/u/mhirota-impinj)\
**Replies:** 3\
**Last updated:** [February 26, 2023, 4:34pm UTC](https://discourse.nameko.io/t/service-that-dynamically-spawns-and-kills-managed-threads/787 "2023-02-26T16:34:13Z")

</div>

Any suggestions on creating a nameko service that allows for an RPC call to dynamically spawn, and then later, kill, a managed thread? So far, I’ve been able to spawn managed threads, but I’m looking for a way to stop t…

---

## [Nameko v3.0.0rc11: Passing config to worker\_factory](https://discourse.nameko.io/t/nameko-v3-0-0rc11-passing-config-to-worker-factory/788)

<div class="topic-metadata">

**Author:** [@sradhakrishna](https://discourse.nameko.io/u/sradhakrishna)\
**Replies:** 3\
**Last updated:** [February 8, 2023, 11:45am UTC](https://discourse.nameko.io/t/nameko-v3-0-0rc11-passing-config-to-worker-factory/788 "2023-02-08T11:45:02Z")

</div>

Hi, I am using v3.0.0rc11. My service is defined as below: import logging from nameko import config from nameko.rpc import rpc class MyService: name = config.get('SERVICE\_NAME') logger = logging.getLogger(\_\_n…

---

## [How long will it take to release 3.0?](https://discourse.nameko.io/t/how-long-will-it-take-to-release-3-0/591)

<div class="topic-metadata">

**Author:** [@bright-pan](https://discourse.nameko.io/u/bright-pan)\
**Replies:** 4\
**Last updated:** [January 12, 2023, 9:04pm UTC](https://discourse.nameko.io/t/how-long-will-it-take-to-release-3-0/591 "2023-01-12T21:04:38Z")

</div>

hi， nameko 3.0 is take so long time, from 2019, gevent backend for nameko is exciting，I hope to use it soon :stuck\_out\_tongue:

---

## [How to return ACK from consumer as soon as message is received/consumed?](https://discourse.nameko.io/t/how-to-return-ack-from-consumer-as-soon-as-message-is-received-consumed/765)

<div class="topic-metadata">

**Author:** [@aspirine](https://discourse.nameko.io/u/aspirine)\
**Replies:** 1\
**Last updated:** [November 21, 2022, 4:08pm UTC](https://discourse.nameko.io/t/how-to-return-ack-from-consumer-as-soon-as-message-is-received-consumed/765 "2022-11-21T16:08:47Z")

</div>

I am using nameko.messaging.consume for consuming messages from a queue. Here’s a sample code - from kombu import Queue from nameko.messaging import consume class Service: name = "sample\_service" QUEUE = Queue(…

---

## [Nameko shell hangs on rpc call](https://discourse.nameko.io/t/nameko-shell-hangs-on-rpc-call/774)

<div class="topic-metadata">

**Author:** [@alf](https://discourse.nameko.io/u/alf)\
**Replies:** 1\
**Last updated:** [October 25, 2022, 1:01pm UTC](https://discourse.nameko.io/t/nameko-shell-hangs-on-rpc-call/774 "2022-10-25T13:01:41Z")

</div>

Initially the nameko shell is able to communicate with the nameko service. The service is a simple hello world: class GreetingService: name = 'greeting' @rpc def hello(self): return f"{datetime.today…

---

## [About terminating asynchronous tasks](https://discourse.nameko.io/t/about-terminating-asynchronous-tasks/771)

<div class="topic-metadata">

**Author:** [@louis.wang](https://discourse.nameko.io/u/louis.wang)\
**Replies:** 0\
**Last updated:** [June 28, 2022, 9:21am UTC](https://discourse.nameko.io/t/about-terminating-asynchronous-tasks/771 "2022-06-28T09:21:47Z")

</div>

The previous project was implemented asynchronously with djang+celery. In the asynchronous task, celery can call the revoke method through the current task\_id to terminate the currently running task. Now I have used name…

---

## [Error while calling Dask cluster in Nameko worker](https://discourse.nameko.io/t/error-while-calling-dask-cluster-in-nameko-worker/758)

<div class="topic-metadata">

**Author:** [@giorgiobasile](https://discourse.nameko.io/u/giorgiobasile)\
**Replies:** 3\
**Last updated:** [May 9, 2022, 8:46pm UTC](https://discourse.nameko.io/t/error-while-calling-dask-cluster-in-nameko-worker/758 "2022-05-09T20:46:48Z")

</div>

Hi, I’m trying to use Dask within a Nameko service, but I’m running into some issues. Here is a sample code I use: from nameko.rpc import rpc from dask.distributed import Client import dask.array as da # creates a …

---

## [Unit testing without a real rabbitmq instance](https://discourse.nameko.io/t/unit-testing-without-a-real-rabbitmq-instance/743)

<div class="topic-metadata">

**Author:** [@sradhakrishna](https://discourse.nameko.io/u/sradhakrishna)\
**Replies:** 2\
**Last updated:** [April 21, 2022, 8:50am UTC](https://discourse.nameko.io/t/unit-testing-without-a-real-rabbitmq-instance/743 "2022-04-21T08:50:36Z")

</div>

Hi, I am writing pytest based unit tests for my nameko services as outlined here: Testing Services — nameko 2.12.0 documentation. I’ve been using container\_factory for testing my services for the most part. A few instan…

---

## [Retry decorater](https://discourse.nameko.io/t/retry-decorater/763)

<div class="topic-metadata">

**Author:** [@renewfrl](https://discourse.nameko.io/u/renewfrl)\
**Replies:** 0\
**Last updated:** [April 20, 2022, 11:26pm UTC](https://discourse.nameko.io/t/retry-decorater/763 "2022-04-20T23:26:15Z")

</div>

I believe there is something odd in the utils/retry.py decorator which should be put to attention. Not sure if it is intentional or not but at least I spent some time on it to discover the reason behind :wink: the issue…

---

## [Nameko/Django ORM integration](https://discourse.nameko.io/t/nameko-django-orm-integration/166)

<div class="topic-metadata">

**Author:** [@Trikster1911](https://discourse.nameko.io/u/Trikster1911)\
**Replies:** 10\
**Last updated:** [March 29, 2022, 3:03am UTC](https://discourse.nameko.io/t/nameko-django-orm-integration/166 "2022-03-29T03:03:47Z")

</div>

Hello guys, thank you for your library and your work. Here is a question: while trying to integrate Nameko into our project I've stumbled across the necessity to integrate it with Django ORM, don't you know what are th…

---

## [Config.get not work in nameko 2.14](https://discourse.nameko.io/t/config-get-not-work-in-nameko-2-14/748)

<div class="topic-metadata">

**Author:** [@devalexandre](https://discourse.nameko.io/u/devalexandre)\
**Replies:** 1\
**Last updated:** [March 23, 2022, 7:23pm UTC](https://discourse.nameko.io/t/config-get-not-work-in-nameko-2-14/748 "2022-03-23T19:23:36Z")

</div>

I try create a service for mongodb , but when I try get MONGO\_URI using COnf, display method not found.

---

## [Potential concurrency issues with pyscopg2?](https://discourse.nameko.io/t/potential-concurrency-issues-with-pyscopg2/752)

<div class="topic-metadata">

**Author:** [@checor](https://discourse.nameko.io/u/checor)\
**Replies:** 0\
**Last updated:** [March 23, 2022, 7:11pm UTC](https://discourse.nameko.io/t/potential-concurrency-issues-with-pyscopg2/752 "2022-03-23T19:11:35Z")

</div>

Hello! I found this interesting question regarding nameko, sqlalchemy and psycopg2, but unfortunately, is unanswered: python - Potential Nameko concurrency issues with pyscopg2 driver for Postgresql - Stack Overflow A …

---

## [How can I differentiate an RpcProxy call from a ClusterRpcProxy call?](https://discourse.nameko.io/t/how-can-i-differentiate-an-rpcproxy-call-from-a-clusterrpcproxy-call/744)

<div class="topic-metadata">

**Author:** [@betacar](https://discourse.nameko.io/u/betacar)\
**Replies:** 0\
**Last updated:** [March 1, 2022, 12:19pm UTC](https://discourse.nameko.io/t/how-can-i-differentiate-an-rpcproxy-call-from-a-clusterrpcproxy-call/744 "2022-03-01T12:19:23Z")

</div>

So, I’ve setup multiple nameko services, where some of them call between each other (inter-service calls), using RpcProxy. But, along with that, I’ve also setup a fastapi service that calls those services via ClusterRpcP…

---

## [How upgrade from version 2.1x to version 3](https://discourse.nameko.io/t/how-upgrade-from-version-2-1x-to-version-3/727)

<div class="topic-metadata">

**Author:** [@lockeduan](https://discourse.nameko.io/u/lockeduan)\
**Replies:** 1\
**Last updated:** [February 15, 2022, 10:46am UTC](https://discourse.nameko.io/t/how-upgrade-from-version-2-1x-to-version-3/727 "2022-02-15T10:46:01Z")

</div>

Hi, we are using nameko 2.12 on production, should we keep using 2, or should we upgrade to 3? and, is there any simple way to upgrade? Thanks

---

## [Time to go 2 -\> 3?](https://discourse.nameko.io/t/time-to-go-2-3/740)

<div class="topic-metadata">

**Author:** [@geoffjukes](https://discourse.nameko.io/u/geoffjukes)\
**Replies:** 3\
**Last updated:** [February 15, 2022, 6:58am UTC](https://discourse.nameko.io/t/time-to-go-2-3/740 "2022-02-15T06:58:14Z")

</div>

Hi, Still loving Nameko. I’ve put off the move from 2 to 3 until release - but like BOTW2, it’s in limbo. I’m starting a full refactor of the services I run that use 2, so I figure now is the best time to try out 3. A…

---

## [RPC-extension and heartbeat if my service doing long task (above 20min)](https://discourse.nameko.io/t/rpc-extension-and-heartbeat-if-my-service-doing-long-task-above-20min/248)

<div class="topic-metadata">

**Author:** [@Tsoy](https://discourse.nameko.io/u/Tsoy)\
**Replies:** 5\
**Last updated:** [January 29, 2022, 6:41pm UTC](https://discourse.nameko.io/t/rpc-extension-and-heartbeat-if-my-service-doing-long-task-above-20min/248 "2022-01-29T18:41:44Z")

</div>

The error lies in the fact that the received task from the queue returns to the queue back some time later, if you look at the logs there is an error associated with the timeouts. Here are the detailed logs and questi…

---

## [Authentication/ Authorization with Websockets](https://discourse.nameko.io/t/authentication-authorization-with-websockets/737)

<div class="topic-metadata">

**Author:** [@sradhakrishna](https://discourse.nameko.io/u/sradhakrishna)\
**Replies:** 0\
**Last updated:** [January 24, 2022, 6:55pm UTC](https://discourse.nameko.io/t/authentication-authorization-with-websockets/737 "2022-01-24T18:55:08Z")

</div>

Hi, I am looking for best practices in implementation schemes for authenticating websocket communication. At the moment, this is the workflow I am considering: Client (Web UI) gets a JWT from invoking a REST API endpo…

---

## [Nameko test: Module already imported warning](https://discourse.nameko.io/t/nameko-test-module-already-imported-warning/714)

<div class="topic-metadata">

**Author:** [@checor](https://discourse.nameko.io/u/checor)\
**Replies:** 3\
**Last updated:** [December 6, 2021, 10:01am UTC](https://discourse.nameko.io/t/nameko-test-module-already-imported-warning/714 "2021-12-06T10:01:26Z")

</div>

Hello, I’m using nameko and it’s a breeze! I have a doubt about a warning I get when I run nameko test, as the pytest warning recommends. Every time I run it, it says: =================================================…

---

## [Kombu \< 5.2.1 safety issues in dependencies. What it takes to migrate to 5.x?](https://discourse.nameko.io/t/kombu-5-2-1-safety-issues-in-dependencies-what-it-takes-to-migrate-to-5-x/722)

<div class="topic-metadata">

**Author:** [@renewfrl](https://discourse.nameko.io/u/renewfrl)\
**Replies:** 3\
**Last updated:** [December 6, 2021, 10:00am UTC](https://discourse.nameko.io/t/kombu-5-2-1-safety-issues-in-dependencies-what-it-takes-to-migrate-to-5-x/722 "2021-12-06T10:00:39Z")

</div>

The latest release of kombu contained new versions for dependencies. According to safety.py these dependencies contained security fixes (try latest sqs dependencies · celery/kombu@f3b0455 · GitHub) What does it take to…

---

## [Reloading nameko service on change](https://discourse.nameko.io/t/reloading-nameko-service-on-change/135)

<div class="topic-metadata">

**Author:** [@Jesse\_Pollak](https://discourse.nameko.io/u/Jesse_Pollak)\
**Replies:** 5\
**Last updated:** [November 12, 2021, 4:57am UTC](https://discourse.nameko.io/t/reloading-nameko-service-on-change/135 "2021-11-12T04:57:03Z")

</div>

Hi! I'm working on a system that uses a bunch of different nameko services which we run in development using docker compose and the nameko run command. Is there a recommended way to make services auto-reload on code c…

---

## [How to run nameko with sudo](https://discourse.nameko.io/t/how-to-run-nameko-with-sudo/718)

<div class="topic-metadata">

**Author:** [@antl31](https://discourse.nameko.io/u/antl31)\
**Replies:** 2\
**Last updated:** [November 11, 2021, 7:17pm UTC](https://discourse.nameko.io/t/how-to-run-nameko-with-sudo/718 "2021-11-11T19:17:54Z")

</div>

Hello, I have Ubuntu 20.04 and python 3.8 locally. I want to run nameko process with sudo. sudo nameko run sudo: nameko: command not found

---

## [One exchange per service for events](https://discourse.nameko.io/t/one-exchange-per-service-for-events/716)

<div class="topic-metadata">

**Author:** [@MahdiZareie](https://discourse.nameko.io/u/MahdiZareie)\
**Replies:** 3\
**Last updated:** [November 10, 2021, 11:24am UTC](https://discourse.nameko.io/t/one-exchange-per-service-for-events/716 "2021-11-10T11:24:13Z")

</div>

Hi I was reviewing the runtime structure of nameko. I was wondering why did you decide to create one exchange per service for events? For example, Couldn’t we have a single central exchange for all the events in the sy…

[Next page](https://discourse.nameko.io/latest.md?page=1)