0

Suppose there is a third-party application which offers GRPC services with authentication. You want to use these services in your web application. So you will basically use that service behind the curtains with just a few simple conversions (e.g. time is denoted in seconds in third-party, but you want hours on your side). See below 2 approaches for such infrastructure:

  1. Send http requests from web client to backend, then on backend side make all necessary conversions, prepare GRPC request, send it through the vendor and convert it back to http response.
  2. Send GRPC requests from web client and also make all necessary conversions on web frontend side. In this case backend will be like gateway from web client and the vendor.

Which one you consider the better design and why?

Elgin Cahangirov
  • 113
  • 4
  • it is http `Authorization` header. In neither case I am planning to make it public. Frontend will not be aware of this authentication, it'll be handled on backend side – Elgin Cahangirov Feb 28 '23 at 14:03
  • Is the backend a regular server-side application implementing business procedures? Or is it an infrastructure service? – Laiv Feb 28 '23 at 14:52
  • @Laiv it's a regular server-side application which includes most of the business logic – Elgin Cahangirov Mar 01 '23 at 12:10

0 Answers0