# Using Nameko without built-in service registration, rpc, or amqp?

**URL:** <https://discourse.nameko.io/t/using-nameko-without-built-in-service-registration-rpc-or-amqp/348>\
**Category:** Uncategorized\
**Created:** [September 27, 2018, 6:09pm UTC](https://discourse.nameko.io/t/using-nameko-without-built-in-service-registration-rpc-or-amqp/348 "2018-09-27T18:09:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielrs](https://avatars.discourse-cdn.com/v4/letter/d/3da27b/32.png) [@danielrs](https://discourse.nameko.io/u/danielrs)\
**Post date:** [September 27, 2018, 6:09pm UTC](https://discourse.nameko.io/t/using-nameko-without-built-in-service-registration-rpc-or-amqp/348/1 "2018-09-27T18:09:13Z")

</div>

I’m about to start a new project that is gonna be based in micro-services.

They idea is that the micro-services are gonna be running in a k8s cluster, with different micro-services written in different languages. I like the way Nameko thinks about micro-services, about organizing the entry-points and dependencies explicitly.

However, there’s already a message queue + api libraries in place, so replacing them with Nameko’s built-in is not an option (we would be writing our own entry-points/dependency providers for those).

It it possible to run Nameko services without having them connected to a rabbitmq server (hence disabling built-in RPC + amqp support). Since they are gonna be running in a k8s cluster, the services would be able to find each other using the URLs generated for them.

Best regards.

---

<div class="post-metadata">

**Author:** ![David\_Szotten](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.nameko.io/david_szotten/32/6_2.png) [@David\_Szotten](https://discourse.nameko.io/u/David_Szotten)\
**Post date:** [September 27, 2018, 8:28pm UTC](https://discourse.nameko.io/t/using-nameko-without-built-in-service-registration-rpc-or-amqp/348/2 "2018-09-27T20:28:52Z")

</div>

Whilst nameko includes extensions for rpc over amqp (along with a few others), no particular extension is required to build or run nameko services. you pick and choose, build your own, and plug in what you want.