# Who is using on production

**URL:** <https://discourse.nameko.io/t/who-is-using-on-production/178>\
**Category:** googlegroup\
**Created:** [March 20, 2017, 11:28am UTC](https://discourse.nameko.io/t/who-is-using-on-production/178 "2017-03-20T11:28:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mattbennett](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.nameko.io/mattbennett/32/13_2.png) [@mattbennett](https://discourse.nameko.io/u/mattbennett)\
**Post date:** [March 20, 2017, 5:59pm UTC](https://discourse.nameko.io/t/who-is-using-on-production/178/2 "2017-03-20T17:59:46Z")

</div>

Great question! Would love to see this thread grow.

I can kick it off --

We've been using Nameko in production at Student.com \<[http://student.com/&gt](http://student.com/&gt); for  
~2 years.

In our setup we have:

\* Domain services, which look after the data and logic related to specific  
domains in our business (we do student accommodation, so one service  
manages properties and rooms, another handles prices and availability, and  
so on)  
\* Facade services, which aggregate several domain services into APIs for a  
specific customer (e.g. there is a facade for our website, another for our  
content management system)

Facade APIs all RESTful HTTP, and they call the domain services over RPC.

There's a fledgling example that shows this pattern  
here: [GitHub - nameko/nameko-examples: Nameko microservices example](https://github.com/nameko/nameko-examples) (note the "gateway"/facade  
service still in a PR).

For auth, there are two approaches I've taken in the past:

1. Authenticate at the boundary (i.e. facade) and have domain services just  
trust their callers (simple, but weak security)  
2. Also generate a JWT that contains permissions/roles for that identity,  
and pass that along with every call so each downstream service can perform  
its own authorization checks.

We should try to add auth into the example app. The JWT approach sounds  
complex but it's actually quite simple.

I've already written about our ops/hosting in this  
thread [Redirecting to Google Groups](https://groups.google.com/forum/#!topic/nameko-dev/Sfvm9xY6MHE)

Hope that helps. I'd love to see some other folks adding their experiences  
here too.

> **···**
>
> On Monday, March 20, 2017 at 11:28:36 AM UTC, abhinav...@gmail.com wrote:
> 
> > Hi All,
> > 
> > We have a Django monolith and planning to move to microervices  
> > architecture. We came across Nameko and found it interesting.  
> > Is there list of projects using nameko in production or case studies/  
> > articles.
> > 
> > It would be great if any of you can share your experience with Nameko. How  
> > you have architect it? How have you done authentication? etc.
> > 
> > Thanks  
> > Abhi

---

_[View the full topic](https://discourse.nameko.io/t/who-is-using-on-production/178)._