Platform Enterprise

Chapter 4. Applying Governance to Technology Platforms With Domain Driven Design

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 4th chapter of the final book. Please note that 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 [e-mail].

Architecting effective platforms is crucial to the longevity of supporting dependent teams and services effectively. There are many design tensions that you’ll encounter when building platforms. Keeping these tensions in mind when making technical decisions requires a careful approach when defining platform requirements.

This chapter extends on Chapter 3 to define concrete platform requirements, both functional and non-functional ones. In this chapter, we’ll focus on architectural principles and requirements that are shared across all core platforms, regardless of their specific focus. Parts 2–5 break down requirements further to reflect tailored technical subdomains. Because Platform Engineering heavily depends on the practice of enterprise governance, is applied throughout the entire development cycle, and extends so many technical domains and subdomains, this chapter will define platform requirements through ...