We are starting to explore gRPC as a replacement o...
# generalé
Édouard Lopez
09/15/2022, 8:55 AMWe are starting to explore gRPC as a replacement of HTTP REST in my company, some developers argues that contract testing isn't necessary anymore. What value does pact bring in such situation?
t
Timothy Jones
09/15/2022, 9:23 AMSchemas are not contract tests
Timothy Jones
09/15/2022, 9:26 AMI’ll let someone else take this one though
Timothy Jones
09/15/2022, 9:26 AMReally the question is: why do they think it wouldn't bring value?
m
Matt (pactflow.io / pact-js / pact-go)
09/15/2022, 10:23 AM
You should watch my talk on this, I literally spoke on it yesterday at API Days in Melbourne 😆
❤️ 2
🙏 1
Matt (pactflow.io / pact-js / pact-go)
09/15/2022, 10:24 AM
Schemas are not contracts: https://pactflow.io/blog/schemas-are-not-contracts/
Why gRPC is not inherently safe: https://pactflow.io/blog/the-case-for-contract-testing-protobufs-grpc-avro/
s
Slackbot
09/15/2022, 10:24 AMm
Matt (pactflow.io / pact-js / pact-go)
09/15/2022, 10:25 AM
We do have a gRPC and Protobufs plugin (see #CEQBDD5U4 if you’re interested, but it is still in beta support as we iron things out) which should help. It doesn’t currently cover the forwards compatibility case where a provider adds a new required field. But we have some ideas on how to address that too
👀 1
é
Édouard Lopez
09/15/2022, 12:06 PM@Matt (pactflow.io / pact-js / pact-go) Thanks for the links.
What' the title of your conf? seems it's not published yet
m
Matt (pactflow.io / pact-js / pact-go)
09/15/2022, 12:34 PM
Yep should be up the next few days I hope. I'll publish when it is.
It's "schemas are not contracts: why contract testing matters in the age of gRPC, Kafka and Graphql"
🙏 1
s
Slackbot
09/15/2022, 12:34 PMé
Édouard Lopez
09/15/2022, 4:00 PMI think you have a typo in the article:
m
Matt (pactflow.io / pact-js / pact-go)
09/16/2022, 11:45 AM
Ah thanks, I'll look next week when back!