# Why nameko did not use something like JSON RPC for serialization?

**URL:** <https://discourse.nameko.io/t/why-nameko-did-not-use-something-like-json-rpc-for-serialization/312>\
**Category:** Github Issues\
**Created:** [August 13, 2018, 9:33am UTC](https://discourse.nameko.io/t/why-nameko-did-not-use-something-like-json-rpc-for-serialization/312 "2018-08-13T09:33:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [September 22, 2018, 10:45pm UTC](https://discourse.nameko.io/t/why-nameko-did-not-use-something-like-json-rpc-for-serialization/312/3 "2018-09-22T22:45:39Z")

</div>

There’s nothing beyond a partial proof of concept at the moment.

I have a [hyper-h2](https://github.com/python-hyper/hyper-h2) HTTP2 server extension running in Nameko, and I’m attempting to hook up the GRPC components. It’s really just an experiment at this point because I am new to both GRPC and HTTP2.

I want the eventual API to look something like:

```auto
class Service:

    @grpc(GreeterStub.SayHello)
    def say_hello(self, request, context):
        return HelloReply(message="Hello, %s!" % request.name)

```

---

_[View the full topic](https://discourse.nameko.io/t/why-nameko-did-not-use-something-like-json-rpc-for-serialization/312)._