Ivan,
Yes, this approach is used by some other systems, and still, I don't like
it very much.
Let's hear more opinions.
On Sat, Oct 9, 2021 at 9:00 PM Ivan Daschinsky wrote:
> Hi.
> Pavel T., Ok, http rest dosn't have the clean design, in your opinion.
>
> But what about grpc? The same?
>
> As
I agree with Pavel. The suggested approach is indeed utilized quite
frequently, but it's inherently error-prone.
The main issue is that it creates implicit assumptions about the behavior
of both the service and the user's code. For example, if the user's code
must provide a username, what if it do
Val, Pavel both of you are right, but on the other hand there are some
other tasks
1. Distributed tracing.
2. Custom metrics/measurements
3. Auth and some related tasks (i.e. ingests full User info by calling some
auth service in middleware).
Do you both think that this is a good idea in business
+1 to have service proxy context.
> 11 окт. 2021 г., в 09:43, Ivan Daschinsky написал(а):
>
> Val, Pavel both of you are right, but on the other hand there are some
> other tasks
>
> 1. Distributed tracing.
> 2. Custom metrics/measurements
> 3. Auth and some related tasks (i.e. ingests full Use
