Book Image

Technology Operating Models for Cloud and Edge

By : Ahilan Ponnusamy, Andreas Spanner
Book Image

Technology Operating Models for Cloud and Edge

By: Ahilan Ponnusamy, Andreas Spanner

Overview of this book

Cloud goals, such as faster time to market, lower total cost of ownership (TCO), capex reduction, self-service enablement, and complexity reduction are important, but organizations often struggle to achieve the desired outcomes. With edge computing gaining momentum across industries and making it possible to move workloads seamlessly between cloud and edge locations, organizations need working recipes to find ways of extracting the most value out of their cloud and edge estate. This book provides a practical way to build a strategy-aligned operating model while considering various related factors such as culture, leadership, team structures, metrics, intrinsic motivators, team incentives, tenant experience, platform engineering, operations, open source, and technology choices. Throughout the chapters, you’ll discover how single, hybrid, or multicloud architectures, security models, automation, application development, workload deployments, and application modernization can be reutilized for edge workloads to help you build a secure yet flexible technology operating model. The book also includes a case study which will walk you through the operating model build process in a step-by-step way. By the end of this book, you’ll be able to build your own fit-for-purpose distributed technology operating model for your organization in an open culture way.
Table of Contents (13 chapters)
1
Part 1:Enterprise Technology Landscape and Operating Model Challenges
6
Part 2: Building a Successful Technology Operating Model for Your Organization
8
Chapter 6: Your Distributed Technology Operating Model in Action

Becoming antifragile

The author Nassim Nicholas Taleb describes antifragile in his book with the same name as “things that gain from disorder.” While we all understand what fragile means, we don’t really have a word that describes the opposite, so the author claims. The word robust might come to mind, but robust better describes things that don’t change when exposed to disorder, such as uncertainty, variability, imperfect/incomplete knowledge, and error. Antifragility does take a different approach instead of just going further. Antifragile describes things that thrive, evolve, or get better when exposed to stressors or change, and open source software does exactly that.

We need to be more explicit, though, with what we mean when we say open source software. We are not talking about a public GitHub repo that is maintained by a handful of people. While impactful software might start that way, we really refer to enterprise-grade or enterprise-ready software...