HighlightPact Foundation

Pact contract tests: verify service messages without burning the house down

Pact introduction: code-first contract testing for HTTP and message integrations between services.

Pact is a code-first tool for testing HTTP and message integrations with contract tests. Contract tests check that messages between applications match a shared understanding documented in a contract, as an alternative to expensive, brittle end-to-end integration tests. The approach fits especially well when many services must communicate.

Based on: Introduction | Pact Docs · Pact Foundation

Highlightdbt Labs

dbt model contracts: build-time guarantees on column shape before consumers break

dbt Labs docs on model contracts—upfront shape guarantees verified at build, plus governance caveats and support limits.

A dbt model contract is a set of upfront guarantees on the shape of a model’s dataset. At build time dbt checks that the transformation matches the contract or fails. Governance features add trust but can harden rollbacks if adopted too early, and contracts apply only to supported SQL materializations—not Python models, ephemeral models, or several other resource types.

Based on: Model contracts | dbt Developer Hub · dbt Labs

HighlightConfluent

Compatibility types that keep producers and consumers in sync as schemas change

Confluent Schema Registry docs on schema evolution and backward, forward, full, and transitive compatibility modes.

Schema evolution means changing schemas over time while keeping producers and consumers compatible. Schema Registry compares new versions to prior ones using configurable compatibility types, with BACKWARD as the default. Rules differ by format (Avro, Protobuf, JSON Schema) and by how fields were originally defined.

Based on: Schema Evolution & Compatibility Types | Backward, Forward, Full, Transitive | Confluent Documentation · Confluent