Universal Data Modeling

Chapter 11. Modeling for Data Management

A note for Early Release readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 11th chapter of the final book. The GitHub repo will be made active later on.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at @oreilly.com.

In the previous chapters, you have learned about the general process of data modeling. Specifically, Chapter 10 focuses on compute and storage design along with the principles of physical data modeling. You explored how architectural choices such as processing engines, storage formats, partitioning, and indexing directly affect performance, scalability, and cost. That discussion established the technical foundation required to store and process data efficiently in modern data platforms.

Modern data management is more than a technical operation. Enterprises nowadays build their data system on the foundation that focuses on the values, not the hardware and software. Instead of only asking how data is stored and processed, you now ask how data is designed, owned, and delivered as something people can actually use. That means you need to fit your data into the wider enterprise data management practices. You will build it and sell it, just like a product.

This chapter will introduce ...