Chapter 3. The Challenges of Scaling Data Infrastructure
In this chapter we’ll dive further into the challenges of the everyday workflows of data producers and consumers in building and maintaining complex software and data systems. Furthermore, we’ll elaborate on how data development is different from software development, and the implications of these differences on our ability to drive value with data in an organization. Being aware of these challenges will equip you to understand how data contracts fit within the workflows of developers, what problems they mitigate, and how you can help developers understand their role within a data contract architecture.
How Data Development Is Not Like Software Development
As mentioned in Chapter 1, data development best practices preceded software development by decades. Previously, a set of best practices, design philosophies, and management methodologies existed wholly separate from the software engineering workflows that came after. Naturally, there are unique differences between data development and software development that prevent one from being a carbon copy of the other in terms of tools or processes. It is useful to walk through these flows to better understand why data requires a similar but unique paradigm for managing scale.
Perhaps the largest of these differences can be found when comparing pre-development patterns. Pre-development refers to engineering time spent on a project outside of writing code. In software engineering, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access