Using gRPC for server client communication in a java desktop app

[Rohm]

Hello, I would like to hear what you people think about approach mentioned in the title in general.

Also: 

- Is a combination of gRPC and protobuf a feasible technology for an app that runs on a single server and sends updates to clients within the same network (Usually used by 2 to 30 users at the same time)? 

- Would you implement the client side in a similiar manner to a client that consumes a RESTful service or are there any huge differences?

- In a small team: Do you think it is possible maintain the services in a way, that clients won't have to updated everytime the server is updated? (e.g. clients that use api.v1 can still operate with a server that is on api.v2)  

Thank you for your insights.

[Eric Anderson]

On Tue, Jun 21, 2022 at 4:51 AM Rohm <r.hamm...@isp-insoft.de> wrote:

Hello, I would like to hear what you people think about approach mentioned in the title in general.

Nothing is strange about this use-case. gRPC would be fine. REST and gRPC are very similar for this use case, from a networking perspective.

- In a small team: Do you think it is possible maintain the services in a way, that clients won't have to updated everytime the server is updated? (e.g. clients that use api.v1 can still operate with a server that is on api.v2)  

The normal thing to do is not create a v2 unless you really have to. You are free to add new fields to existing services without breaking existing clients. If you do make a v2 and you want to support v1 clients, the server will need to have a v1 service implementation.