Building Platforms That Scale ER – Angelo Agatino Nicolosi

This automation extends beyond just tracking to also encompass the relations between components, their specifications, and any arising error reports, all stored in a structured manner across several repository classes. We have witnessed that companies that embrace a component model for building their products organize, register, and continuously document the relationships between components and how they are assembled to form each final product. This makes it possible to trace errors on all levels.

To support the maintenance process, product and component specifications, along with error reports, can be stored in several repository classes. An example, as visualized in Figure 3.9, can be the following [CCM]: Figure 3.9 A Way to Integrate Documentation and Error Management in CBD • Customer and Product-Oriented Repository (CCRP): At the highest level, this repository focuses on storing customer reports and interactions. Its primary goal is to enable service personnel to deliver prompt and effective customer support, with information that is directly relevant to customer experiences and product performance.

• Product Maintenance Report Repository (PMR): This repository is dedicated to cataloging all known issues related to products and components. It includes detailed product structure information, illustrating the dependencies between products and components. This structure is invaluable for developers and maintenance teams, aiding them in pinpointing the source of errors at both the product and component levels • Change Repository (CR): At the lowest level, the Change Repository holds technical information related to the technical changes required to address each specific higher-level issue identified.

The process of managing complex products and maintaining multiple products through these repositories is not unique to component-based development (CBD). However, CBD introduces specific challenges and opportunities in mapping products to components and in managing error reports effectively at both levels. This dual-level error management is critical in addressing the most challenging aspects of product maintenance. By integrating the Fractal Automation Engine with such a detailed and dynamic documentation approach, organizations can create a feedback loop that directly contributes to quantifying the quality of service (QoS) for each component.

Building Platforms That Scale: A Practical Guide to Composable Platform Engineering with Fractal Architecture, 1/e Angelo Agatino Nicolosi 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.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this title, please reach out to Pearson at [email protected] 1kitap1.com/en Contents Preface Acknowledgments About the Author Part I: Fractal Architecture in Platform Engineering Chapter 1: Platform Engineering: Bridging the Gap Between Application and Infrastructure Chapter 2: Foundations of Fractal Architecture in Platform Engineering Chapter 3: The Fractal Automation Engine: Bringing Fractals to Life Part II: Landing Zones and Applications Chapter 4: Atoms for Secure Landing Zones Chapter 5: Atoms for Landing Zones: Operational Excellence Chapter 6: Live System Atoms Chapter 7: Live System Molecules and Fractals 1kitap1.com/en Table of Contents Preface Who Should Read This Book?

How Is the Book Organized?

This is a short excerpt from the opening of “” by Unknown, quoted for review and introduction purposes. All rights belong to the copyright holders.

Book Information

• Unique ID: 7ce548461ad87f2a
• File Extension: .pdf
• File Size: 17,006,600 bytes (16.219 MB)
• Title: –
• Author: Unknown
• Pages: 377
• Language: English (en)

Reading & Word Statistics

• Estimated Reading Time: 394.66 minutes
• Total Words: 78,932
• Total Characters: 571,344
• Average Words per Page: 209.37
• Average Characters per Page: 1515.5

Most Frequent Words

platform (485), infrastructure (420), cloud (414), data (413), components (409), fractal (375), security (357), component (328), management (306), services (292), system (277), access (271), teams (263), service (251), systems (248), across (232), application (221), aws (216), architecture (202), model (198), applications (186), network (180), environments (176), specific (173), automation (170), within (166), azure (159), edge (157), business (156), approach (150), new (147), solutions (144), performance (140), software (136), also (136), resources (134), development (134), fractals (131), engineering (128), ensuring (128), tools (126), operational (125), between (122), control (121), without (120), capabilities (120), monitoring (119), provides (119), figure (113), different (112), chapter (111), ensure (104), design (102), observability (102), needs (102), storage (101), operations (100), policies (100), organizations (99), compliance (98), requirements (98), team (96), engine (95), configuration (95), integration (95), organization (94), atoms (91), live (90), identity (90), interface (90), ensures (90), governance (89), offers (89), used (88), process (88), challenges (87), secure (86), platforms (85), various (85), recovery (84), offer (83), resource (82), based (82), changes (82), managing (82), gcp (81), enables (80), use (79), public (79), like (77), support (77), allows (76), lifecycle (75), need (73), comprehensive (73), user (73), example (72), enterprise (72), complexity (72), multiple (72).

PDF Download