hltech / judge-d-contract-publisher-core Goto Github PK

What
Provide gRPC expectations reader

Background
gRPC uses protobuf to define structure of messages that are exchanged between services. The messages structure, requests and responses are defined in .proto file which is used by both consumer and provider. Nevertheless .proto files may differ resulting in communication breakdown between services. On contrary messages fields may have the same indexes and type, which will still work, but may have different meaning to this defined primarily. To ensure contract is not broken there is need to publish gRPC expectations.

Assumptions
jude-d is able to publish JMS and REST expectations, likewise it may provide contract for gRPC protocol.

Acceptance Criteria
GIVEN service has .proto file with defined requests and responses
WHEN Contract publisher receives request to publish expectations for an gRPC protocol
THEN Contract publisher generates gRPC expectations for given service

What
Provide gRPC capabilities reader

Background
gRPC uses protobuf to define structure of messages that are exchanged between services. The messages structure, requests and responses are defined in .proto file which is used by both consumer and provider. Nevertheless .proto files may differ resulting in communication breakdown between services. On contrary messages fields may have the same indexes and type, which will still work, but may have different meaning to this defined primarily. To ensure contract is not broken there is need to publish gRPC capabilities.

Assumptions
jude-d is able to publish JMS and REST capabilities, likewise it may provide contract for gRPC protocol.

Acceptance Criteria
GIVEN service has .proto file with defined requests and responses
WHEN Contract publisher receives request to publish capabilities for an gRPC protocol
THEN Contract publisher generates gRPC capabilities for given service