👨‍🔧
The Ops Compendium
  • The Ops Compendium
  • Definitions
    • Ops Definition Comparisons
  • ML & DL Compendium
  • MLOps
    • MLOps Intro
    • MLOps Teams
    • MLOps Literature
    • MLOps Course
    • MLOps Patterns
    • ML Experiment Management
    • ML Model Monitoring & Alerts
    • MLOps Tools
    • MLOps Deployment
    • Feature Stores & Feature Pipelines
    • Model Formats
    • AI As Data
    • MLOps Interview Questions
    • ML Architecture
  • DataOps
    • SQL
    • Tools
    • Databases
    • Database Modeling
    • Data Analytics
    • Data Engineering
    • Data Pipelines
    • Data Strategy
    • Data Vision
    • Data Teams
    • Data Catalogs
    • Data Governance
    • Data Quality
    • Data Observability
    • Data Program Management
    • Data KPIs
    • Data Mesh
    • Data Contract
    • Data Product
    • Data Engineering Questions & Training
    • Data Patterns
    • Data Architecture
    • Data Platforms
    • Data Lineage
  • DevOps
    • DevOps Strategy
    • DevOps Tools
      • Tutorials
      • Continuous Integration
      • Docker
      • Kubernetes
      • Cloud Objects
      • Key Value DB
      • API Gateway
      • Infrastructure As code
      • Logs
      • ELK
      • SLO
    • DevOps Courses
  • DevSecOps
    • Definitions
    • Tools
    • Concepts
  • Architecture
    • Problems
    • Development Concepts
    • System Design
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. DataOps

Data Contract

PreviousData MeshNextData Product

Last updated 2 years ago

Was this helpful?

  1. A data contract is a formal agreement between a service and a client that abstractly describes the data to be exchanged. That is, to communicate, the client and the service do not have to share the same types, only the same data contracts. -

  2. The following is a set of articles around the topics of data product / contract etc. however the focus is about data contracts and expectations IMO, therefore I place it here. - by Chad sanderson

    4. the rise of

    6. (finally!)

    7. (good) c, also has about data-sharing agreements.

    8. (good)

    9. - swirlai

Implementation

  1. is a vocabulary that allows you to annotate and validate JSON documents, .

  2. protobuf & gRPC

    1. ,

    4. gRPC -

    5. Protobuf -

    6. (good) Intro to gRPC & Protobuf by

    7. (good) What are Protocol Buffers and why they are widely used? by

    8. by "Protocol Buffers (protobuf) is a method of serializing structured data which is particulary useful to communication between services or storing data. It was designed by Google early 2001 (but only publicly released in 2008) to be smaller and faster than XML. Protobuf messages are serialized into a format which is very compact and boosts performance."

    9. protobuf what and why? by

    10. off topic -

  3. managing proto files and other schema types such as avro or json schema, can be done in .

Microsoft
the existential threat of data quality
the death of data modeling part 1
data's collaboration problem
data contracts
production grade data products
a guide to data contracts p1
ontracts, robustness in datamesh (but not only)
from zero to hero
data contract experimentation
JSON Schema
example
Protobuf on git
google dev
what is gRPC?
what are proto buffers, what do they solve and what are the benefits?
a basic pythonic tutorial
a pythonic tutorial
Trevor Kendrick
Dineshchandgr
Understanding protobufs
Daniel Padua Ferreira
binary wire
Swaminathan Muthuveerappan
how to choose between grpc, graphql, rest
kafka's schema registry