Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Driving Data Quality with Data Contracts

You're reading from   Driving Data Quality with Data Contracts A comprehensive guide to building reliable, trusted, and effective data platforms

Arrow left icon
Product type Paperback
Published in Jun 2023
Publisher Packt
ISBN-13 9781837635009
Length 206 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Andrew Jones Andrew Jones
Author Profile Icon Andrew Jones
Andrew Jones
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Part 1: Why Data Contracts?
2. Chapter 1: A Brief History of Data Platforms FREE CHAPTER 3. Chapter 2: Introducing Data Contracts 4. Part 2: Driving Data Culture Change with Data Contracts
5. Chapter 3: How to Get Adoption in Your Organization 6. Chapter 4: Bringing Data Consumers and Generators Closer Together 7. Chapter 5: Embedding Data Governance 8. Part 3: Designing and Implementing a Data Architecture Based on Data Contracts
9. Chapter 6: What Makes Up a Data Contract 10. Chapter 7: A Contract-Driven Data Architecture 11. Chapter 8: A Sample Implementation 12. Chapter 9: Implementing Data Contracts in Your Organization 13. Chapter 10: Data Contracts in Practice 14. Index 15. Other Books You May Enjoy

Introducing Data Contracts

In the previous chapter, we looked at the problems we need to solve, and why it requires a new kind of data architecture. In this chapter, we’ll introduce data contracts as our solution. We’ll provide a definition and explore exactly what it is and how it solves those problems.

One of the best analogies for data contracts is that they act as APIs for your data. That sounds simple, but it’s a fundamental change in how we build our data architecture. As we’ll see later in this chapter, by thinking about providing an API for data, you’ll start defining expectations around that API and consider the ownership and responsibilities. People often refer to an API as a contract between the provider and consumer, and it’s that idea that eventually led to me calling them data contracts.

But an API is just one example of an interface, and really, it’s interfaces that are the key to designing and implementing an architecture...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image