Ponnusamy / Spanner Technology Operating Models for Cloud and Edge

Create your purpose-built distributed operating model for public, hybrid, multicloud, and edge
1. Auflage 2023
ISBN: 978-1-83763-638-9
Verlag: De Gruyter
Format: EPUB
Kopierschutz: 0 - No protection

E-Book, Englisch, 228 Seiten

No detailed description available for "Technology Operating Models for Cloud and Edge".

Autoren/Hrsg.

Ponnusamy, Ahilan

Spanner, Andreas

Weitere Mitwirkende

Hering, Mirco

Caldeira, Vincent

Chopra, Neetan

Fachgebiete

• Mathematik | Informatik EDV | Informatik Technische Informatik Systemverwaltung & Management
• Mathematik | Informatik EDV | Informatik Computerkommunikation & -vernetzung Cloud-Computing, Grid-Computing
• Mathematik | Informatik EDV | Informatik Computerkommunikation & -vernetzung Client-Server Netzwerke

Inhaltsverzeichnis

Table of Contents - Fundamentals for an Operating Model
- Enterprise Technology Landscape Overview
- Learnings From Bimodal IT's Failure
- Approaching Your Distributed Future
- Building Your Distributed Technology Operating Model
- Your Distributed Technology Operating Model in Action
- Implementing Distributed Cloud and Edge Platforms with Enterprise Open Source Technologies
- Into the Beyond

Leseproben

Preface
Speeding up time to market, lowering the total cost of ownership (TCO), reducing CapEx, enabling self-service, and reducing complexity are important cloud goals; however, the desired outcomes don’t always materialize. With edge computing making its way through all industries on top of ongoing journeys to the public cloud (and back), it’s vital to share working recipes for organizations to find their preferred way of extracting the most value out of their technology investments. This book demonstrates a practical way of building a strategy-aligned operating model while considering a variety of related aspects such as culture, leadership, team structures, metrics, intrinsic motivators, team incentives, tenant experience for development and product teams, platform engineering, operations, open source, and technology choices – just to name a few. You’ll understand how single, multi, or hybrid cloud architectures, security models, automation, application development, workload deployments, and app modernization can be re-utilized for edge workloads to help you build a secure, yet flexible technology operating model. You will learn how to build a distributed technology operating model using a case study. By the end of this book, you’ll be able to build your own fit-for-purpose operating model for your organization in an open culture way. Who this book is for
As a cloud architect, solutions architect, DevSecOps or platform engineering lead, program manager, CIO, CTO, or chief digital officer, if you’re tasked to lead cloud or edge computing initiatives, create architectures and enterprise capability models, align budgets, or show your board the value of your technology investments, then this book is for you. This book will help you define and build your cloud and edge computing capabilities around a fit-for-purpose technology operating model. What this book covers
Chapter 1, Fundamentals for an Operating Model, looks at the challenges that the journey to the cloud has thrown at organizations and why. It goes through a rich set of examples to look at different ways to define key components of an operating model: the operating model dimensions. It also introduces key terms from engineering and operations and distinguishes between platform and product engineering and SRE. This chapter closes with thoughts on how to construct metrics, teaming, and how Conway’s law affects your architecture. Chapter 2, Enterprise Technology Landscape Overview, gives an overview of common enterprise technology landscape components. It distinguishes between systems of innovation, differentiation, and systems of record, and examines the associated change cadence and challenges related to these cadences by expanding the classification from applications to infrastructure. It completes the discussion by looking into the difficulties around the adoption of a standard operating model because of the distinguished traits across that classification. Chapter 3, Learnings From Bimodal IT’s Failure, examines closely why the Gartner Bimodal IT approach never yielded the results expected and extracts the learnings out of it in order to apply them to the distributed technology operating model. It looks at the change cadence differences between mode 1 and mode 2. It closes by highlighting that there is no endorsed bimodal architecture that combines a working approach between mode 1 and mode 2 estates. Chapter 4, Approaching Your Distributed Future, focuses on the imminent distributed future. It looks at the reasons why the future is distributed and revisits hybrid and multi-cloud definitions while shedding light on specific business and technology reasons why the public or single cloud cannot be a target state for organizations. It spends time on different edge classifications to get a better handle on different viewpoints in light of worthwhile use cases. It closes by looking at emerging trends and external factors such as compliance, mergers, and acquisitions. Chapter 5, Building Your Distributed Technology Operating Model, explains in detail the building blocks for a distributed operating model across the cloud and edge. It starts off by showing the steps toward the desired outcome in the Starting at the end section and introduces an operating model dashboard to track outcomes, work in process (WIP), and dependencies. It presents workshop-leading practices to help lead teams along the forming, storming, norming, and performing life cycle. The chapter also walks through more than 30 dimensions to consider and choose from for the operating model. It also provided numerous suggestions for further reading if you want to dive deeper into any of the research underpinning our recommendations. Chapter 6, Your Distributed Technology Operating Model in Action, introduces an anonymized real-life use case and walks through how this organization built its distributed technology operating model in a hybrid multi-cloud and edge context. It walks through the step-by-step process of utilizing already introduced templates and new assets that can be reused for the operating model development process. Chapter 7, Implementing Distributed Cloud and Edge Platforms with Enterprise Open Source Technologies, walks through an operating model-based platform implementation example. It connects real work architecture, design, and implementation with the previously developed operating model. It shows how requirements and principles from the operating model flow into technology selection and how they map to capabilities. Chapter 8, Into the Beyond, wraps the book up. It introduces additional aspects such as antifragility, geographically disparate (non-)autonomous operating models; different ways to measure progress; how tech debt, undifferentiated heavy lifting, and open source are connected; gap analysis; and roadmap development. It revisits prioritization and decision-making and introduces a quick way to make the best possible decision with the often limited information available. To get the most out of this book
With prior knowledge of cloud computing, application development, and edge computing concepts, you will get the most out of this book. You may appreciate it more if you are in a role such as CxO, senior business/IT leadership, enterprise architecture, or the development and operations teams. Conventions used
There are a number of text conventions used throughout this book. Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “Prakash captured it and followed a similar approach to help the steam team define the transition states for the PTE.Platform.UnifiedPlatform item.” Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “For example, the two dependencies that were identified under LA.Customer were LA.Architecture.Resilience and LA.Architecture.Security.” Tips or important notes Appear like this. Get in touch
Feedback from our readers is always welcome. General feedback: If you have questions about any aspect of this book, email us at [e-mail] and mention the book title in the subject of your message. Errata: Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you have found a mistake in this book, we would be grateful if you would report this to us. Please visit www.packtpub.com/support/errata and fill in the form. Piracy: If you come across any illegal copies of our works in any form on the internet, we would be grateful if you would provide us with the location address or website name. Please contact us at [e-mail] with a link to the material. If you are interested in becoming an author: If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, please visit authors.packtpub.com. Share Your Thoughts
Once you’ve read Technology Operating Models for Cloud and Edge, we’d love to hear your thoughts! Please click here to go straight to the Amazon review page for this book and share your feedback. Your review is important to us and the tech community and will help us make sure we’re delivering excellent quality content. Download a free PDF copy of this book
Thanks for purchasing this book! Do you like to read on the go but are unable to carry your print books everywhere? Is your eBook...

Über Autor(innen)

Ponnusamy Ahilan:
Ahilan Ponnusamy is a GTM specialist for Application Platform at Red Hat based in Singapore. He enjoys working with customers to deliver real value on hybrid cloud architectures and cloud-native application development and delivery practices. Ahilan completed his Master of Computer Applications from MKU, India in 1999. His work history includes the likes of Philips CE in Eindhoven Netherlands, BEA technologies as a member of Customer Centric Engineering and support in India and USA, Pre-sales Tech-lead for cloud platform team at Oracle USA, Principal platform engineer at VMware, Global Architect at Dell Technologies Singapore. Originally from Madurai, Tamil Nadu, India, Ahilan currently resides in Singapore with his wife and two boys.Spanner Andreas:
Andreas Spanner is currently working as Chief Architect within the CTO Organization at Red Hat. Prior to his role as the Chief Architect for Australia & New Zealand, Andreas worked across the globe in many different industries ranging from automotive, manufacturing, and supply chain logistics to telco, FSI and public sector on areas such as ERP, CRM, HR, and payroll data and processes migrations, Internet security appliances, and B2B marketplaces. He has delivered Just-In-Time-logistics and series production systems for customers such as BMW, Volkswagen, and Mercedes. Andreas completed his engineering degree in Germany and got his first Commodore 64 when he was 12 years old. Originally from Bavaria, Andreas now lives in Sydney, Australia.