# What is the status of the nameko-grpc?

**URL:** https://discourse.nameko.io/t/what-is-the-status-of-the-nameko-grpc/541
**Category:** Uncategorized
**Created:** [January 16, 2020, 5:53pm UTC](https://discourse.nameko.io/t/what-is-the-status-of-the-nameko-grpc/541 "2020-01-16T17:53:32Z")
**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: [January 17, 2020, 10:38pm UTC](https://discourse.nameko.io/t/what-is-the-status-of-the-nameko-grpc/541/2 "2020-01-17T22:38:10Z")

</div>

Hi @ksimmi,

Nameko-grpc is not dead, but it’s also not been extensively used (at least that I know of). It is well tested and passes all of the interop tests that the gRPC authors use to verify other-language implementations. But there are sure to be some issues discovered if/when used in production.

On your questions:

1. Depends on your risk appetite 😉
2. gRPC is a much better RPC implementation than Nameko’s built-in one; but Nameko is a much nicer development experience than the standard gRPC one (IMO). That’s why I created nameko-grpc, to get the best of both
3. The API design is final now
4. All the other extensions are compatible. Nameko-tracer is not very useful for nameko-grpc in its current form though because it does not support streaming requests or responses.
5. You should ideally use Nameko 3.0 for new development, but see also this thread: [Roadmap to nameko 3.0.0](https://discourse.nameko.io/t/roadmap-to-nameko-3-0-0/509). Nameko-grpc may need some small tweaks to work with 3.0 but IIRC the upgrade path for extensions is pretty simple.

---

_[View the full topic](https://discourse.nameko.io/t/what-is-the-status-of-the-nameko-grpc/541)._