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:
- Depends on your risk appetite
- 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
- The API design is final now
- 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.
- You should ideally use Nameko 3.0 for new development, but see also this thread: Roadmap to nameko 3.0.0. Nameko-grpc may need some small tweaks to work with 3.0 but IIRC the upgrade path for extensions is pretty simple.