Hi. My company makes very heavy use of Kafka, and ...
# pactflow-ama
s
Hi. My company makes very heavy use of Kafka, and i’ve been interested recently in bi-directional contract testing. We use Avro schemas stored in a schema registry, so i’m aware that ours isn’t a particularly common use-case for Pact. I’ve seen this on the roadmap: https://github.com/pactflow/roadmap/issues/32, so i’m curious about how i might be able to help. I’m new to Pact so I imagine getting to grips with how this works for messaging systems now is the first step?
👋 1
Where one Kafka topic typically has many consumers - the producer registers an Avro schema for their topic, but consumers also tend to define their own, which is meant to be compatible but they only find this out at runtime. If there was some way for consumers to register their own schema (with perhaps stricter logical types), this could be used to drive two way contract validation (consumer schemas and producer schemas must be compatible with each other etc)
m
Yep - that’s pretty much the problem 🙂
Supporting Avro in Pactflow via BDCT will first require support for AsyncAPI, and also support for another tool to generate a pact file with avro interactions in it. @Ali Ustek is currently investigating creating an Avro plugin for Pact, which would be one of the key components in a BDCT flow. I’d suggest joining the #C03SFK0H789 channel to see where that’s at and how you might be able to contribute to the development/requirements of that plugin
👍 1