You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in this comment, some services only depend on the gRPC client or server. Currently, spring-grpc only provides one starter. For these use cases, users need to manually add grpc-stub or grpc-services dependencies.
I think these are very two different use cases and it’s worth having spring-grpc provide two additional starters:
spring-grpc-client-spring-boot-starter # only client
spring-grpc-server-spring-boot-starter # only server
The existing starter should still be available, it includes both client and server starters:
I'm not convinced that the grpc-services should be included yet. Personally I always use it, but wouldn't it be better to leave it as optional? We might end up with just 2 starters that way as well - there's no need for the combo because client is a superset of server.
As mentioned in this comment, some services only depend on the gRPC client or server. Currently, spring-grpc only provides one starter. For these use cases, users need to manually add
grpc-stub
orgrpc-services
dependencies.I think these are very two different use cases and it’s worth having
spring-grpc
provide two additional starters:The existing starter should still be available, it includes both client and server starters:
The text was updated successfully, but these errors were encountered: