The gRPC API allows anyone to interact with the People service. However, consuming and maintaing a gRPC API adds complexity:
gRPC isn't http(s) based and requires extra steps on the server side to open up.
The generated proto-buf based code is complex because it needs to process binary data.
Securing gRPC calls is non-trivial.
...
The added benefits (point-to-point real time communication, low latency / high throughput, IPC) of choosing gRPC over a classic RESTful implementation are marginal within the business case of the People service.
The goal of this epic is to replace the gRPC API with a RESTful API.
Success criteria
19
20
21
24
25
29
Implementation suggestion
The implementation should follow the same implementation details as seen in the OAI service.
Specification of the RESTful API needs to be done via OpenAPI.
Generation of the API server code needs to happen via the ogen tool.
Copy the Swagger implementation from the OAI service.
epic
The gRPC API allows anyone to interact with the People service. However, consuming and maintaing a gRPC API adds complexity:
The added benefits (point-to-point real time communication, low latency / high throughput, IPC) of choosing gRPC over a classic RESTful implementation are marginal within the business case of the People service.
The goal of this epic is to replace the gRPC API with a RESTful API.
Success criteria
19
20
21
24
25
29
Implementation suggestion
The implementation should follow the same implementation details as seen in the OAI service.