2 ms·
I highly recommend using it for public endpoints too. It's much nicer than worrying about a supported up-to-date client library in your language or using yet an
by manigandham 7y ago
I highly recommend using it for public endpoints too. It's much nicer than worrying about a supported up-to-date client library in your language or using yet another variation of JSON/HTTP/REST that's unique to every API.
Some databases and queues are starting to use this now and it makes it incredibly easy to get started since we can generate our own clients and integrate at whatever level we need.
- xarope 7y agoI'm starting to steer our dev team towards this as well, would you have any good links to the gotchas involved in using grpc for public endpoints (if coming from REST as a legacy base)? e.g. for authentication and authorization, throttling etc? I looked at kong, but it seems the plugins don't apply to grpc.
- manigandham 7y agoUnfortunately no good reading I know of other than the official GRPC docs.