This topic defines common words used in the Gable application and documentation. While many of these words may be familiar to you, in some cases they have nuances specific to Gable.

​
Definitions

The following definitions may be useful as you work in Gable:
  • CI/CD Check: Controlled integration refers to a systematic and controlled approach to integrating software components or modules within a larger system. It involves carefully orchestrating the integration process to ensure that individual components work together effectively and that any potential issues or conflicts are identified and resolved. During controlled integration, Gable performs a check to verify the compatibility and functionality of changes to data systems. The purpose of this check is to identify any violations to the contract and eliminate communication failures, data inconsistencies, or functional gaps.
  • Contract Violation: A data contract violation occurs when the constraints defined in the contract are not met once validations are performed in either CI/CD or after-the-fact.
  • Data Asset: A data asset refers to a data artefact which contains metadata. Data assets might be a source of information, the destination of information, or both. Common asset types include database tables, event streaming topics, or S3 buckets.
  • Data Contract: In Gable, a data contract is a YAML file that details the attributes, semantic definitions, constraints, SLAs, and owners of a respective data asset. These contracts are then used by the Gable platform to automatically enforce these constraints at scale.
  • Data Consumer: A data consumer refers to an individual at the company that leverages data to solve a business problem.
  • Data Producer: A data producer refers to an individual at the company that generates or creates data.
  • Data Product: A Data Product is a production-grade application of a data asset. Data producers have clear business value and are supported by data contracts.
  • Gable: Gable is a data collaboration platform that protects your most important data pipelines via data contracts. Through this platform, data producers and consumers determine the most important data assets and workflows, establish agreed upon constraints for a data asset, and receive meaningful notifications when a contract is about to be violated with the goal of preventing backwards incompatible changes upstream.