Platform Enterprise Reframing Platform Engineering to Accelerate Software Delivery (2026-04-09 Early Release) (Lesley Cordero)（Z-Library）

📄 File Format: PDF

💾 File Size: 3.2 MB

📖 Read Online ⬇️ Download

Registered users can read the full content for free

Register as a Gaohf Library member to read the complete e-book online for free and enjoy a better reading experience.

📄 Page 1

(This page has no text content)

📄 Page 2

Platform Enterprise Reframing Platform Engineering to Accelerate Software Delivery 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. Lesley Cordero

📄 Page 3

Platform Enterprise by Lesley Cordero Copyright © 2027 Cordero Solutions. All rights reserved. Published by O’Reilly Media, Inc., 141 Stony Circle, Suite 195, Santa Rosa, CA 95401. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (https://oreilly.com). For more information, contact our corporate/institutional sales department: 800-998-9938 or corporate@oreilly.com. Acquisitions Editor: Louise Corrigan Development Editor: Shira Evans Production Editor: Clare Laylock Interior Designer: David Futato Interior Illustrator: Kate Dullea December 2026: First Edition Revision History for the Early Release 2026-04-09: First Release See https://oreilly.com/catalog/errata.csp?isbn=9798341643451 for release details. The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. Platform Enterprise, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. The views expressed in this work are those of the author(s) and do not represent the publisher’s views. While the publisher and the author(s) have

📄 Page 4

used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the author(s) disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with such licenses and/or rights. 979-8-341-64340-6 [LSI]

📄 Page 5

Brief Table of Contents (Not Yet Final) Part 1: Sociotechnical Foundations Chapter 1: Framing Enterprises as Sociotechnical Platforms (available) Chapter 2: Organizational Structures and People (available) Chapter 3: Translating Principles To Practice With Governance Processes (unavailable) Chapter 4: Applying Governance Processes To Technology Platforms (unavailable) Part 2: Development Platforms Chapter 5: Version Control and Artifact Storage (unavailable) Chapter 6: Command Line Interfaces (CLIs) (unavailable) Chapter 7: Service Frameworks, Libraries, and Templates (unavailable) Chapter 8: Design Systems and Component Libraries (unavailable) Part 3: Delivery Platforms Chapter 9: Infrastructure Platforms (unavailable) Chapter 10: Software Release Pipelines (unavailable) Chapter 11: Test Platforms (unavailable) Part 4: Reliability Platforms Chapter 12: Observability Platforms (unavailable) Chapter 13: Monitoring and Alerting Platforms (unavailable) Chapter 14: Resilience Testing Platforms (unavailable) Part 5: Domain-Specific Platforms

📄 Page 6

Chapter 15: Product Monorepo Platforms (unavailable) Chapter 16: Technical Expertise Platforms (unavailable) Chapter 17: Identity Platforms (unavailable) Chapter 18: Payment Platforms (unavailable) Part 6: Platform Formation Cycle Chapter 19: Complementary Platform Components (unavailable) Chapter 20: The Platform Formation Cycle (unavailable) Chapter 21: Applying To Technical Scenarios (unavailable)

📄 Page 7

Chapter 1. Framing Enterprises as Sociotechnical Platforms 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 1st 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 sevans@oreilly.com. Becoming and remaining a competitive business is a constant tension for enterprise organizations building new products and services that extend their existing footprint. In a digital economy defined by rapid change, enterprise engineering organizations must be built to support adaptability and long-term resilience in response to the complexity of enterprise organizations. This means not only being able to withstand change but also to embrace it through experimentation, at the same time mitigating risk that hinders the prospect of a durable and sustainable future. The difficulty of this challenge lies in the inherent complexity of enterprise organizations. Enterprise engineering organizations cannot operate as purely technical systems; they must also consider both the social and organizational implications of what it means to build and operate software for enterprise audiences. This is where sociotechnical theory and its practices can enable technology leaders to deliver on its goal to build resilient, adaptable engineering organizations that can thrive amid constant change. At their

📄 Page 8

core, enterprise organizations are sociotechnical systems. They’re an ecosystem composed of people, structures, processes, and technologies that are deeply interconnected (Figure 1-1). These components cannot evolve independently of one another; instead, they shape and constrain one another as the organization grows, reorganizes, and adapts. Figure 1-1. Visual representation of a sociotechnical system, including how it is influenced by an external environment. Within the sociotechnical system, it is composed of four components: 1) structure 2) technology, 3) people, and 4) process Sociotechnical theory emphasizes that success depends on how well its components are aligned and managing that alignment is a practice referred to as joint optimization (Figure 1-2).

📄 Page 9

(This page has no text content)

📄 Page 10

Figure 1-2. The social and technical subsystems joined together, where the overlap of the two indicates joint optimization. Joint optimization asserts that with the correct structures, processes, and technologies, people are best set up for success. Translating this into an engineering enterprise setting, with the correct structures, processes, and software systems, technologists safely experiment, iterate on feedback quickly, and deliver sustainably. When these components drift out of alignment, however, the result is complexity that introduces unnecessary friction that slows the success of delivering products to their audience. In practice, organizations often struggle with this balance. It’s common for organizations to overinvest in tools and processes at the expense of team dynamics. When this happens, you build tools and processes that don’t represent the needs of users and processes that hinder software delivery. Another common problem is dysfunctional organization structures that lack clarity over ownership boundaries and scope of work. It’s also very common to see organizations promoting values like collaboration and trust without putting technical systems in place to reinforce them. In this scenario, your technical systems incentivize teams to make decisions that optimize for their team instead of the overall organization. Thinking about a sociotechnical system helps us understand that all these components depend on each other, and we can’t be successful unless we invest in all of them in a holistic, strategic way that ensures the components will have the expected outcome in the wider enterprise environment Distributed systems have increasingly been used to unlock both technical and organizational challenges by providing architectural patterns that enable teams to work autonomously at scale without sacrificing quality of service. That said, building these systems is often approached through a short-term mentality that neglects the importance of building them sustainably. So while distributed systems have unlocked extensive opportunities to build technology in growing organizations with evolving products, the consequence is that these organizations become susceptible to complexity that makes understanding organizational and technical context more difficult.

📄 Page 11

Similar to how we’ve evolved the way we build and architect applications to embrace different distributed system patterns, we must evolve the way we operate and support the development and delivery of these applications. If these new architectural patterns are a solution to the technical complexity of scaling and evolving our applications, Platform Engineering is a sociotechnical solution to the organizational complexity of scaling our applications. This chapter begins laying out how sociotechnical theory can be applied to platform engineering organizations in enterprise settings. We’ll elaborate on the four components introduced in Figure 1-1 and the specific technical, social, organizational challenges platform engineering is positioned to address. Defining Platform Engineering “Sometimes organizations have Platform Engineering teams but no Platform, and vice versa.” — DORA Community Group, 2/14/2025 Platform Engineering is a sociotechnical engineering practice that spans many technical and business domains. These sociotechnical solutions are largely influenced by DevOps and Site Reliability Engineering; instead of thinking of them as completely independent, however, we should think of platform engineering as the set of practices, processes, toolchains and culture that are always evolving as our context changes – whether that be in terms of scale, priorities, or organizational structure. By framing platform engineering as a sociotechnical solution, we acknowledge that sustainable organizations require thought about how the way we build and the way we work as teams enable long-term success. Organizations need to be sustainable in order to grow their business, and being a sustainable organization ultimately comes down to being resilient to change. It’s important to note that Platform Engineering is not equal to DevOps, Infrastructure, or Infrastructure platforms. Instead, it’s the application of

📄 Page 12

DevOps principles and practices across all phases of developer or user experience journeys. While this book will not go as deeply into the applications of DevOps in end-user experience journeys, which we refer to as business platforms, its application is nevertheless relevant. That said, similar to sociotechnical systems, Platform engineering is the supporting structure, processes, culture, and set of technologies that enable this wider organizational sustainability. It does this by building supporting technology that’s responsive to the evolving needs of its wider engineering organization. When we think about what it means to be a sustainable organization, we can think of it as stability among the four components you saw in Figure 1-1. 1. Structure: the organizational patterns and practices that inform how we work 2. Technology: the architecture and infrastructure that comprises our platforms 3. Processes: the operations and processes that enable our platform 4. People: the people and teams who collaborate on these efforts. The stability of these components is best facilitated by an organization committed to building sustainable practices and technology that best matches the set of risks (upside and downside) faced by the organization. Throughout this book, we will make frequent reference to each of these four components since they represent the makeup of sociotechnical systems. While we just briefly introduced the components, we’ll elaborate on them further in the rest of this section: PEOPLE The first component of a system encompasses the individual people operating with and within it. This includes individual contributors, managers, decision-makers, and other stakeholders who interact with the system. People bring

📄 Page 13

their knowledge and skills, expectations and experiences, and values to the system, all of which shape how the system functions. They are often the most flexible but unpredictable component of a sociotechnical system since they’re highly capable of adapting to change but prone to error or misjudgment. People do not exist in a vacuum; their behavior is strongly influenced by the three other components, which together create a system of incentives. Leaders are best situated to influence the impact these components have on incentives and behavior, a dynamic we’ll explore further in Chapter 2. STRUCTURE Structure components are the formal and informal organizational units of a system, whether that is the formal company organization chart with reporting lines and teams, or informal structures like communities of practice and cross-team networks that shape how work is coordinated and how information flows. There are certainly different types of structures, particularly when you consider how structures overlap with the other components. For example, a community can surely serve as an organizational structure – and we will discuss the role of communities in enterprise platforms, but it is a people- centric structure. PROCESS Process components translate goals into action by providing repeatable and reliable routines, workflows, or rituals that can be leveraged by other other components of the system, whether that is planning cycles leveraged by managers and leaders, agile ceremonies leveraged by teams, or delivery platforms leveraged by pipelines.

📄 Page 14

TECHNOLOGY Technology components include the tools, infrastructure, and software systems that enable execution. Since this book is tailored to engineering leaders, these components will make up the majority of the content in this book. The final part of the sociotechnical system is the External Environment. While there might be opportunities for indirect influence here, they are much harder to change and generally represent the constraints an organization needs to operate under. Some examples of this include policy and law, the landscape of leverageable open source solutions, or competing solutions. For platform engineering organizations, the external environment also includes other functional areas of the entire enterprise.

📄 Page 15

Platform Engineering for Enterprise Tech As Enterprise organizations grow, they not only get bigger, but they become systems of systems: each team, department, or platform can be thought of as its own sociotechnical system, with its own people, processes, tools, and structures. At the enterprise scale, these systems are layered and interdependent; the complexity is not just in the parts, but in how they interact. Decisions made in one part of an organization can cascade through others in unexpected ways, which is why designing for alignment across sociotechnical systems becomes so important. Entire books can be written on the idea of Systems Thinking; Learning Systems Thinking by Diana Montalion takes readers through the journey of learning how to think differently. Whereas the default framework for thinking tends to be linear in nature, Systems Thinking emphasizes it is inherently non-linear. This framework of understanding and approaching problems is particularly essential for highly complex ones. This is where platform engineering plays a unique role: it’s one of the few functions tasked with enabling coherence across this complexity. By building shared infrastructure, conventions, and processes that help distributed teams stay connected and resilient as the system evolves, platform engineering can enable organizations to build sustainable organizations. In this context sustainability refers to the continuous practice of operating in a way that enables short-term growth opportunities while enabling long-term success. Sustainability is particularly difficult in highly complex systems, both to maintain and to define in the first place. When we think about sociotechnical sustainability through the lens of social, technical, and organizational sustainability, however, we gain a more structured and holistic way of identifying what needs to be sustained, the impact of it, and what mechanisms are required to support it in the long-term. The three dimensions we’ll review in this section are deeply interdependent: social sustainability ensures the well-being and growth of the people who build and use systems; technical sustainability ensures that

📄 Page 16

those systems are maintainable and achievable; and organizational sustainability ensures that both are supported institutionally. Together, they offer a framework for designing competitive enterprises that are adaptable and ethically grounded in the increasingly complex world. NOTE While organizational systems might typically be considered part of the “social system,” I choose to make it its own separate system to reflect the joint optimization of the two primary systems. From a social perspective, this refers to the team structures we operate within. From the technical perspective, this refers to the architecture we build and operate. Culture is a crucial aspect that influences organizational sustainability; we’ll discuss it in more detail after we review our definition of organizational sustainability. In addition to defining and reviewing each dimension, I will contextualize our definition of sustainability for each. For each dimension, we’ll also review a framework of “needs” to provide a fuller picture of what progress looks like. Social Systems Social systems encompass the human elements of sociotechnical systems. This includes the individuals operating with and within the system, how they relate to each other as individuals and groups, and the overall culture (roles, norms, and values). Social sustainability prioritizes the well-being of both individual people and communities. Communities can take multiple forms, whether that’s in the form of a formal team or informal self-organized groups of people who contribute to the overall culture and goals of your organization. In terms of defining a mental model of what progress looks like, we’ll reference Maslow’s Hierarchy of Needs but in the context of sociotechnical social systems.

📄 Page 17

(This page has no text content)

📄 Page 18

Figure 1-3. Maslow’s Hierarchy of Needs Triangle, which encompasses five categories of needs: 1) Physiological, 2) Safety, 3) Belongingness and love, 4) Esteem, and 5) Self-actualization. Maslow’s Hierarchy of Needs was originally created in the context of articulating one’s individual needs, desires, until reaching the ultimate goal of self-actualization. A visualization of the relationship between different needs can be found in Figure 1-3. In chapter X, we’ll discuss an alternative framework to addressing needs from a community driven perspective. While the majority of this book is centered around organizational sustainability, considering how individual experiences of sustainability relate to the wider organization is important because an organization’s sustainability is directly influenced by the sustainability of its workforce. An organization’s workforce – from leaders to line level employees – ultimately power the products and services delivered to customers. While Maslow’s hierarchy encompasses five parts, they can be folded into three: 1) basic needs, 2) psychological needs, and 3) self-fullfillment needs. We’ll use this three part approach when we review technical and organizational sustainability in the two sections afterwards. These three parts are as follows: Basic needs At the foundation, an individual’s basic needs encompass physiological and safety needs. It should go without saying that employees must have reliable pay, job security, and safe working conditions because fulfilling physiological and safety needs isn’t optional – it’s a fundamental requirement. Psychological needs Once basic needs have been met, employees need a sense of belonging and esteem. This is where intentional community management comes into play. The focus on community management throughout this book is one that is both strategic and intentional. People are compelled by a sense of

📄 Page 19

belonging, and community management is crucial for driving this sense of belonging. Self-fullfillment needs The highest tier of needs is centered on growth: continuous learning, mastery, innovation, and autonomy. Cultivating a learning culture is the most sustainable advantage both for organizations and the individuals who are part of that organization. NOTE Tech companies have long since legislated and governed our lives on a global digital level. But because companies have grown so large that they resemble empires more than enterprises, they are now in the business of impacting the wider public in a way they never could before. This adds an extra layer of responsibility for enterprise organizations to consider the ways in which they impact the wider world’s sustainability. Technical Systems Technical systems encompass the technology components of sociotechnical systems. In the context of technology companies, this includes tooling components, infrastructure components, and the processes that enable social systems to build and operate these technologies. Technical sustainability prioritizes the sustainability of technical systems through explicit principles and patterns that should be applied throughout your tech stack. This includes both external and internal facing technologies since the former ensures a successful business and the latter facilitates delivering that business. Platform Hierarchy of Needs Reusing a similar model as Maslow’s hierarchy of needs, we’ll categorize aspects of sustainability by framing them as technical needs. In Chapter 3,

📄 Page 20

we will translate these needs into technical requirements. We fold those needs into three categories, shown in Figure 1-4: