0

We're using Flask and nameko with RabbitMQ in our project setup. We use this for multiple projects (we've started 2 months ago), and we have issue with service names when developing.

We have two projects - A and B, and both of them has UserService (with different functions):

class UserService:
    name = 'user_service'
    ...

Problem is when we need to run both of projects on same machine one user service is not working. Well to be precise, both are working, but all requests are handled by one of them, and as their structure is different we got errors.

First idea was to add project prefix to service names, something like A_user_service, but that is really ugly solution (in rpc part we then need to call something like rpc.A_user_service and that is terrible). Is there any kind of namespaces for nameko projects? We've tried to set rpc_excange parameter in config to be different per project, but that is not solving issue we have.

Aleksandar Varicak
  • 928
  • 9
  • 23

1 Answers1

1

I guess it sort of depends on how you define "project". The service name is the main namespace, so if there's any chance these two user services are ever going to co-exist, they should probably use different (perhaps more specific) service names.

If they are completely separate (e.g. developed for two separate clients), then maybe using separate rabbitmq vhosts would solve your problem? That way you'd end up running two separate "clusters" of services, where nothing in vhost a can see or talk to anything in vhost b (of course you could run instances of service x in both if you want, e.g. for services that would be running on both client sites/networks)

second
  • 28,029
  • 7
  • 75
  • 76
  • Although this is acceptable solution, I need to know if there is way to do this with nameko configuration. If I don't manage to do it that way, I'll accept this answer. – Aleksandar Varicak Dec 30 '16 at 23:34
  • maybe i'm misunderstanding, but the `vhost` _is_ part of nameko configuration, via the `AMQP_URI` – second Dec 31 '16 at 09:21
  • yes, my bad. RabbitMQ vhost will solve the issue definitely. Thanks. – Aleksandar Varicak Dec 31 '16 at 12:12
  • @second I'm strugling to executre inegration tests using Nameko and pyTest, I'm not able to connect to RabbitMQ broker, I tried to use container Ip address but still does not work, any suggestion please – Smaillns Oct 29 '21 at 11:13