I have a question howe nameko works.
We are create a nameko service as a proxy to another service that is not
using eventing (eg: we need to poll it to check status)
Since we are using polling, we initially using @timer constructor to do
this polling and firing event on this service that we are trying to
The trouble comes when our system is under stress, timer method is still
running and another timer get triggered.
In order to avoid using DB locks, we continue to use a timer method, but
use it to dispatch an event that will be consumer by another event_handler
In the event handler, we do this construct:
*@event_handler('trainproxy', 'timer_alert', handler_type=SINGLETON)*
We hope this means that only one and only one instance is handing a event.
This will be still true if we have multiple instances of the service. Is