Hello, I have a question (and I don't know if this is the right place to ask it). if in my service architecture we are working with gRPC-protobuf, and the services (providers and consumers) consume the same proto files, this makes the protos the contract itself, rigth?... That said, *what would be the advantage of using PACT in this kind of architecture? (taking into account that you are already working on supporting gRPC communication)*

Hello! See https://pactflow.io/blog/the-case-for-contract-testing-protobufs-grpc-avro/

Thank you!

Welcome - hope it’s helpful 🙂

Hello @Matt (pactflow.io / pact-js / pact-go) how are you? This link that you shared inform that pactflow isn't supported contract tests for grpc and protobuffs yet: "Whilst Pact doesn't (yet) currently officially support these technologies, we're currently building the plugin infrastructure in Pact to enable gRPC and Protobufs to be tested in this fashion." However, is it the current state yet, or have we more news about it? And for avro? I saw a post related to contract avro implementation but I don't if it's already supported officially/ Thanks a lot!!!