دانلود کتاب مهندسی پلتفرم مبتنی بر دامنه – چگونه پلتفرم‌های آگاه از متن، مقیاس‌پذیر و سلف سرویس برای سازمان بسازیم

Software scale breaks people before it breaks systems. A team of ten ships fast, communicates naturally, and holds the entire architecture in shared memory. Scale that to a thousand engineers across dozens of teams, and something fractures—not the code, but the coordination. Engineers wait on each other, copy-paste pipelines they don’t understand, reinvent infrastructure already built three floors up, and spend their sharpest hours navigating processes instead of solving problems. This is not a talent problem. It is an architectural one. Platform engineering exists to solve it. By treating the developer experience as a product—one with real users, real feedback loops, and real ownership—platform teams give engineers self-service access to the capabilities they need without the cognitive overhead of understanding everything underneath. The internal developer platform (IDP) becomes the connective tissue of the organization: invisible when it works, catastrophic when it doesn’t. And yet platform initiatives fail constantly. Teams pour years into platforms that engineers quietly route around. Leadership funds ambitious internal tooling that delivers marginal adoption and lukewarm reviews. The tools exist. The patterns are documented. The intent is genuine. What’s missing is the bridge between the technical foundation and the human system it is meant to serve—the judgment to know what to build, the discipline to know what to leave out, and the organizational understanding to make it matter. This book argues that the missing bridge is the domain. Most platforms are built as generic infrastructure layers that are useful but disconnected from the business problems engineers solve every day. A payments team, a healthcare team, and a semiconductor design team all get the same CI/CD pipeline, the same observability stack, and the same deployment templates. The platform works, technically. But it doesn’t understand the work. It doesn’t encode the compliance rules that a financial services team must follow, the patient privacy constraints that a healthcare team must navigate, or the tape-out deadlines that keep a chip design team awake at night. Engineers are left to bridge the gap between what the platform offers and what their domain demands, and that gap is where friction, frustration, and failed adoption live. Domain-Driven Platform Engineering changes this. By applying the principles of domain-driven design (DDD) to platform engineering, we build platforms that speak the language of the business domains they serve. Platforms that encode compliance as domain abstractions rather than scattering it across application code. Platforms that provide golden paths tailored to the specific workflows of each domain, not generic templates that teams must customize from scratch. Platforms that measure success not just in the DORA metrics of deployment frequency and lead time, but in the reduction of domain-specific friction and the acceleration of business outcomes that leadership cares about. This book is written for engineering leaders, platform architects, and senior practitioners who have experienced both the promise and the frustration of platform engineering. It draws on several decades of hands-on experience building platforms across semiconductors, financial services, healthcare, SaaS, and retail, those industries where the stakes are high, the domains are complex, and generic solutions simply do not survive. Each chapter combines foundational concepts with practical models, real-world case studies, and exercises designed to help you apply these ideas in your own organization. Whether you are building your first platform or evolving an existing one, this book will help you close the gap between what platforms offer and what your engineers and your business need. This is especially true in the world of agentic software development – agents need domain knowledge to operate effectively and safely. This book lays the foundations and concepts necessary to make this work at scale. The companion site for this book is hosted at https://ddpe.platformetrics.com. It is designed to extend what the printed pages can offer: as the tools, frameworks, and model capabilities covered in this book evolve, the companion site will reflect those changes with updated examples, revised recommendations, and new code. Platform engineering is a fast-moving field, and a static text can only capture a moment in time. The companion site is where that moment continues to move forward.