2
votes
Accepted
GRPC over internet
There is nothing technicaly wrong with using gRPC to expose your service to the outside world.
But consumers are unused to having to consume gRPC. REST is much more common and expected.
The reason ...
- 38.2k
1
vote
Accepted
Where is the advantage to use Auth0 with gRPC?
Where is the security in this case?
In how you:
Keep appsettings.json secret and not accessible
Keep appsettings.json away from SCM (source code repositories)
Inject this file or the values of the ...
- 15k
1
vote
adding optional code for bad protocol state check
The offerResult method seems like an implementation detail that should be hidden from clients of the API. Your API needs control of the compute-logic-offer result workflow. You only need to ...
- 46.1k
1
vote
adding optional code for bad protocol state check
With the trend for stateless calls no-one will expect a method call to require closing. But a "Connection" is expected to have state, open, close etc
I would rename stuff to lean into that ...
- 84.4k
1
vote
Single Gateway for multiple gRPC Services
Not sure if this should be an answer, or just a comment but here goes.
Internally, gRPC uses HTTP/2, and at least nginx supoprts being a reverse proxy in front of your server. The clients see a single ...
- 575
Only top scored, non community-wiki answers of a minimum length are eligible