THE AGILE ARCHITECTURE REVOLUTION WILEY CIO SERIES Founded in 1807, John Wiley & Sons is the oldest independent publishing company in the United States With offices in North America, Europe, Asia, and Australia, Wiley is globally committed to developing and marketing print and electronic products and services for our customers’ professional and personal knowledge and understanding The Wiley CIO series provides information, tools, and insights to IT executives and managers The products in this series cover a wide range of topics that supply strategic and implementation guidance on the latest technology trends, leadership, and emerging best practices Titles in the Wiley CIO series include: The Agile Architecture Revolution: How Cloud Computing, REST-Based SOA, and Mobile Computing Are Changing Enterprise IT by Jason Bloomberg Big Data, Big Analytics: Emerging Business Intelligence and Analytic Trends for Today’s Businesses by Michele Chambers, Ambiga Dhiraj, and Michael Minelli The Chief Information Officer’s Body of Knowledge: People, Process, and Technology by Dean Lane CIO Best Practices: Enabling Strategic Value with Information Technology by Joe Stenzel, Randy Betancourt, Gary Cokins, Alyssa Farrell, Bill Flemming, Michael H Hugos, Jonathan Hujsak, and Karl D Schubert The CIO Playbook: Strategies and Best Practices for IT Leaders to Deliver Value by Nicholas R Colisto Enterprise IT Strategy, ỵ Website: An Executive Guide for Generating Optimal ROI from Critical IT Investments by Gregory J Fell Executive’s Guide to Virtual Worlds: How Avatars Are Transforming Your Business and Your Brand by Lonnie Benson Innovating for Growth and Value: How CIOs Lead Continuous Transformation in the Modern Enterprise by Hunter Muller IT Leadership Manual: Roadmap to Becoming a Trusted Business Partner by Alan R Guibord Managing Electronic Records: Methods, Best Practices, and Technologies by Robert F Smallwood On Top of the Cloud: How CIOs Leverage New Technologies to Drive Change and Build Value Across the Enterprise by Hunter Muller Straight to the Top: CIO Leadership in a Mobile, Social, and Cloud-based (Second Edition) by Gregory S Smith Strategic IT: Best Practices for IT Managers and Executives by Arthur M Langer Strategic IT Management: Transforming Business in Turbulent Times by Robert J Benson Transforming IT Culture: How to Use Social Intelligence, Human Factors and Collaboration to Create an IT Department That Outperforms by Frank Wander Unleashing the Power of IT: Bringing People, Business, and Technology Together by Dan Roberts The U.S Technology Skills Gap: What Every Technology Executive Must Know to Save America’s Future by Gary Beach http://avaxhome.ws/blogs/ChrisRedfield THE AGILE ARCHITECTURE REVOLUTION HOW CLOUD COMPUTING, REST-BASED SOA, AND MOBILE COMPUTING ARE CHANGING ENTERPRISE IT Jason Bloomberg with contributions from Ronald Schmelzer John Wiley & Sons, Inc Cover image: # 4X-image/iStockphoto Cover design: John Wiley & Sons, Inc Copyright # 2013 by Jason Bloomberg All rights reserved Published by John Wiley & Sons, Inc., Hoboken, New Jersey Published simultaneously in Canada No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600, or on the Web at www.copyright.com Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at http://www.wiley com/go/permissions Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose No warranty may be created or extended by sales representatives or written sales materials The advice and strategies contained herein may not be suitable for your situation You should consult with a professional where appropriate Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages For general information on our other products and services or for technical support, please contact our Customer Care Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002 Wiley publishes in a variety of print and electronic formats and by print-on-demand Some material included with standard print versions of this book may not be included in e-books or in print-ondemand If this book refers to media such as a CD or DVD that is not included in the version you purchased, you may download this material at http://booksupport.wiley.com For more information about Wiley products, visit www.wiley.com Library of Congress Cataloging-in-Publication Data: Bloomberg, Jason, 1961The agile architecture revolution : how cloud computing, REST-based SOA, and mobile computing are changing enterprise IT / Jason Bloomberg ; with contributions from Ronald Schmelzer pages cm Includes index ISBN 978-1-118-40977-0 (hbk.); ISBN 978-1-118-42199-4 (ebk); ISBN 978-1-118-55405-0 (ebk); ISBN 978-1-118-41787-4 (ebk); Business enterprises—Technological innovations Management information systems Service-oriented architecture (Computer science) I Title HD45.B5466 2013 658.4 0038—dc23 2012038783 Printed in the United States of America 10 To Ronald Schmelzer—business partner, mentor, colleague, parallel entrepreneur, curmudgeon, and friend CONTENTS FOREWORD PREFACE xi xv PART ONE—Enterprise as Complex System CHAPTER 1 Introducing Agile Architecture Deconstructing Agile Architecting Software/Human Systems Meta Thinking and Agile Architecture 10 Defining Architecture: Worse Than Herding Cats Why Nobody Is Doing Enterprise Architecture 12 13 Complex Systems: At the Heart of Agile Architecture CHAPTER 16 Shhh, Don’t Tell Anyone, but Let’s Talk about ServiceOriented Architecture 21 Rumors of SOA’s Demise Thinking Outside the SOA Box 23 26 Okay, So How Did SOA End Up Dead in the First Place? Services: The Core SOA Lesson 31 Implementing Policy-Driven Behavior What’s the Deal with Web Services? The Third Conversation 34 38 41 Freeing Architecture from the Underlying Infrastructure Implementing SOA without an ESB 44 47 The SOA Marketing Paradox and the Wizard of Oz CHAPTER 28 48 Governance: The Secret to Satisfying the Business Agility Meta-Requirement 51 Organizational Context for Governance 52 Architecture-Driven Governance: Beyond IT Governance Rethinking Quality 54 57 Introducing the Agility Model 60 vii viii CONTENTS Meta-Policy Governance 63 Interrelationships among Governance, Quality, and Management Four Stages of Agile Architecture Governance Architecture-Driven Governance and the Butterfly Effect CHAPTE R 70 The Enterprise as Complex System 73 Engineering the Enterprise with Complex Systems Engineering Best-Effort Quality and the Agile Architecture Quality Star Best-Effort Quality in Action The Flash Mob Enterprise 73 76 80 Resilience: The Flip Side of Agility CHAPTE R 64 67 83 86 Agile Architecture in Practice 89 The Composition Vision for IT 90 Vision to Reality: Rethinking Integration 93 Aligning Agile Architecture with BPM 96 Business Modeling and Agile Architecture 98 Processes That Satisfy the Meta-Requirement of Agility 100 PART TWO—The ZapThink 2020 Vision CHAPTE R 103 You Say You Want a Revolution Five Supertrends of Enterprise IT 105 108 Continuous Business Transformation: At the Center of ZapThink 2020 Where’s Our Deep Interoperability? 112 The Crisis Points of the ZapThink 2020 Vision 113 Big Data Explosion and the Christmas Day Bomber Stuxnet and Wikileaks: Harbingers of Cyberwar 116 119 Cybersecurity the Agile Architecture Way 125 The Generation Y Crisis Point CHAPTE R 128 The Democratization of Enterprise IT 133 Demise of the Enterprise IT Department 134 The Agile Architecture Approach to IT Project Management Crisis Point: The Enterprise Application Crash 138 Replacing Enterprise Software: Easier Said than Done 144 136 110 CONTENTS ix PART THREE—Implementing Agile Architecture CHAPTER Deep Interoperability: Getting REST Right (Finally!) 149 Programmable Interfaces: The Never-Ending Story REST to the Rescue REST vs Web Services 161 163 Can REST Fix Web Services? 166 Does REST Provide Deep Interoperability? Where Is the SOA in REST-Based SOA? 168 170 REST-Based SOA: An Iconoclastic Approach 150 155 Dogmatic vs Iconoclastic REST CHAPTER 147 173 Finally, Let’s Move to the Cloud 177 Deja Vu All Over Again 179 Countering Vendor Spin with Architecture Interlude: Neutralizing the Cloud Threat 181 183 Why Cloud Computing Scares the Platform Vendors 186 Architecting beyond Cloud Computing’s Horseless Carriage BASE Jumping in the Cloud: Rethinking Data Consistency Cloud Multitenancy: More than Meets the Eye 187 190 193 Keys to Enterprise Public Cloud 197 Why Public Clouds Are More Secure than Private Clouds Why You Really, Truly Don’t Want a Private Cloud 200 202 Avoiding Unexpected Cloud Economics Pitfalls 205 Rethinking Cloud Service Level Agreements 208 Are Your Software Licenses Cloud Friendly? 212 Garbage in the Cloud Beware Fake Clouds 214 217 Learning the Right Lessons from the 2011 and 2012 Amazon Crashes 219 Failure Is the Only Option 221 Cloud Configuration Management: Where the Rubber Hits the Clouds 223 Clouds, SOA, REST, and State 225 The Secret of a RESTful Cloud 229 BPM in the Cloud: Disruptive Technology 232 Cloud-Oriented Architecture and the Internet of Things Location Independence: The Buckaroo Banzai Effect Postscript: The Cloud Is the Computer 241 236 238 x CONTENTS CHAPTE R 10 Can We Do Agile Enterprise Architecture? 243 Frameworks and Methodologies and Styles, Oh My! 245 The Beginning of the End for Enterprise Architecture Frameworks How to Buy an Agile Architecture 250 The Dangers of Checklist Architecture CONCLUSION 257 LIST OF ABBREVIATIONS ABOUT THE AUTHOR 265 INDEX 267 261 253 248 FOREWORD: THE AGILE ARCHITECTURE REVOLUTION The core thrust of architecture has been to define core business requirements, and then construct the IT solution to meet those requirements, typically as instances of software While this seems like a simple concept, many in enterprise IT went way off course in the last 10 to 15 years IT does not provide the value it once did, meaning IT does not meet the objectives and expectations of the business Indeed, IT has become a cost center where the resource burn increased significantly over the last 20 years, while the value to the business decreased relative to costs This can’t continue We’ve tried all of the tricks With “waterfall” types of approaches to application architecture, the time it takes to move from understanding the requirements to the final deployed system could be years Thus, by the time the system is completed and deployed, the business requirements likely have changed, you’re back to the drawing board, and the delivered system has significantly diminished in value To address the latency issues around the waterfall, those who design and build systems turned to the concept of interaction This means moving through cycles of understand-design-develop-deploy, over and over again, until there is something that resembles the desired business solution Iteration approaches to software development often lead to poorly designed and lower-quality systems because you get it wrong over and over again, seemingly to get it right once Moreover, as requirements change, it’s back to the iterations again, sometimes in a never-ending loop The core benefit IT should provide is that of achieving business agility, or the ability to allow the business to change rapidly around changing business requirements and business opportunities Thus, businesses can move quickly into newer and more profitable product lines, acquire companies to expand their position in the market, or quickly align with regulatory changes that could stop their business in its tracks So, if business agility is good, how can IT achieve it? The current thinking is that we need to change our approach to design and development, again, and move to newer methods and approaches around software architecture The right answer is that we need to change what we build, not how we build it xi The Agile Architecture Revolution: How Cloud Computing, Rest-Based SOA, and Mobile Computing are Changing Enterprise IT by Jason Bloomberg Copyright © 2013 Jason Bloomberg Published 2013 by John Wiley & Sons, Inc ABOUT THE AUTHOR Jason Bloomberg is President of ZapThink, a Dovel Technologies Company He is a global thought leader in the areas of Cloud Computing, Enterprise Architecture, and Service-Oriented Architecture He created the Licensed ZapThink Architect (LZA) SOA course and associated credential, and runs the LZA course as well as his Cloud Computing for Architects course around the world He is a frequent conference speaker and prolific writer Mr Bloomberg is one of the original managing partners of ZapThink LLC, the leading SOA advisory and analysis firm, which was acquired by Dovel Technologies in August 2011 His book, Service Orient or Be Doomed! How Service Orientation Will Change Your Business (John Wiley & Sons, 2006, coauthored with Ron Schmelzer), is recognized as the leading business book on Service Orientation Mr Bloomberg has a diverse background in eBusiness technology management and industry analysis, including serving as a senior analyst in IDC’s eBusiness Advisory group, as well as holding eBusiness management positions at USWeb/CKS (later marchFIRST) and WaveBend Solutions (now Hitachi Consulting) He also coauthored the books XML and Web Services Unleashed (SAMS Publishing, 2002) and Web Page Scripting Techniques (Hayden Books, 1996) 265 The Agile Architecture Revolution: How Cloud Computing, Rest-Based SOA, and Mobile Computing are Changing Enterprise IT by Jason Bloomberg Copyright © 2013 Jason Bloomberg Published 2013 by John Wiley & Sons, Inc INDEX Abstracted Service: Amazon Cloud crashes and, 220–221 managing of, 58–59 SOA and, 31–33 ACID (atomic, consistent, isolated, and durable) transactionality, 191, 192 ADM (Architecture Development Method), 14, 243–244, 249 “Agile,” deconstructed, 4–8 Agile Architecture, 3–19 “agile” deconstructed, 4–8 “architecture” defined, 12–13 Complex Systems and, 16–19 dangers of checklist architecture, 253–254 difficulties of, 31 Enterprise Architecture not being done, 13–15 future of, 257–260 how to buy, 250–251 key to successful, 17 meta thinking and, 10–12 paradigm shifts in thinking about, 257–258 RFP mistakes, 251 RFP pointers, 252–253 software/human systems and, 8–10 as true revolution, xv–xvi, Agile Architecture, in practice, 89–102 agility meta-requirement and, 90–91, 100–102 aligning with BPM, 96–98 business process definitions, 89 composition-centric approach to automation, 89–93 legacy applications and, 92, 95, 101 modeling and, 98–100 SOA and integration challenges, 93–96 Agile Architecture Quality Star, 78–79 Agile Manifesto: changing software requirements and, 7–8 checklist architecture contrasted, 255 four core principles of, 4–5 paradox of, 10 Agility Model: key capabilities of, 84 Richardson Maturity Model (RMM) and, 158–160 Agility Model, governance and, 60–63 diagram of, 62 measuring of, 61–62 Amazon: Cloud Computing and, 204, 207 lessons of Cloud crashes, 219–221 shopping cart and Cloud Computing, 232 Ambiguity, allowing for, 81 APIs (Application Programming Interfaces (APIs), 27, 150–152, 219 Application, meaning of, 149 Application architecture, 246 Application portability, 189 Application Programming Interfaces, 27, 150–152, 219 Application state, Cloud Computing and, 226, 229–235 267 268 INDEX Application tier, Cloud Computing and, 231, 233–235 “Architecting the enterprise,” Architecture, defined, 12–13 Architecture Development Method (ADM), 14, 243–244, 249 Architecture-driven governance, 53, 54–57 Complex Systems Engineering and, 76 “Argument,” as collective term for architecture, 12 Attractors, in Complex Systems theory, 18–19 Automated configurations, Cloud Computing and, 219, 224–225 Automation, in architecture-driven governance, 55 Babbage, Charles, 217 BASE (basic availability soft state, eventual consistency), 192–193 Best-effort quality, 76–80 in action, 80–82 Agile Architecture Quality Star, 78–79 Best-Effort Triangle, 78–79 Big brother effect, 76 Big Data Explosion Crisis point, 115, 116–119 BPM (Business Process Management), 29 Cloud Computing and states, 228–229, 232–236 SOA, dynamic changes in Services, and Agile Architecture in practice, 90–93, 96–98, 100 Business agility: Complex Systems Engineering and, 110–111 defined, proactive, strategic part, 6–7 reactive, tactical part, Business(es): business architecture, 246 business context, of Service, 42–43 business/IT alignment, 41–42 defining of, definitions of business processes, 89 gap between needs and software functions, Business Process Execution Language (BPEL), 172 Business Process Management (BPM), 29, 228, 232 Cloud Computing and states, 228–229, 232–236 SOA, dynamic changes in Services, and Agile Architecture in practice, 90–93, 96–98, 100 Business Process Modeling and Notation (BPMN), 172 Business Service abstraction, 21–23, 41, 46, 47–48 Business value, Cloud Computing and Service Level Agreements and, 211 Butterfly Effect, 70–72 Capital expense, Private Clouds and, 203 CAP (consistency, availability, partition tolerance) Theorem, 191 CSE (Complex Systems Engineering), 73–87, 121, 255 best-effort quality, 76–80 best-effort quality, in action, 80–82 characteristics of, 75 demise of Enterprise IT and, 136 as Enterprise IT supertrend, 110 flash mobs and self-organization, 86–87 INDEX 269 node-centric perspective and, 75–76 resilience and, 83–86 simplicity of, 74 traditional systems engineering contrasted, 73–74 Change: governance and meta-policies, 58–60 quality and change-time requirements, 56, 59–60, 63, 255 responding to, in Agile Manifesto, Chaos theory See Butterfly Effect Chargebacks, Cloud Computing and, 207 Checklist architecture, dangers of, 253–254 Chief Information Officers (CIOs), SOA’s lack of success and, 29 Churn, in Cloud, 207 “Client,” as used in REST, 161 Clinger-Cohen Act, 254 Cloud Computing, 177–241 Amazon crash lessons, 219–221 architecture and challenges of, 179–182 BPM and, 228–229, 232–236 challenges of, 30–31 characteristics of, 179 Cloud as the computer, 241 Cloud-Oriented Architecture and, 236–238 configuration management, 223–225 data consistency and, 190–193 data garbage in, garbage out and, 214–215 demise of Enterprise IT and, 135–136, 141, 145 deployment models, 177–178 deployment scenarios, 187–188, 189 disadvantages of Private Clouds, 202–205 economic pitfalls and, 205–208 Enterprise Public Cloud and, 197–200 failure expectations and plans for, 221–222 fake clouds, 217–219 HATEOAS and, 231–232, 233–234 location independence and Next Big Thing, 238–241 multitenancy and, 193–197 NIST definition of, 177 REST, SOA and states, 225–232 security of Public and Private Clouds, 200–202 Service Level Agreements and, 208–211 service models, 178 SOA and, 24, 27 software licenses and, 212–214 vendor-centric model, 179–184 Cloud-Oriented Architecture (COA), 236–238 location independence and Next Big Thing, 238–239 Cloudwashing, 212 Clustered Shared Schema Approach (second degree multitenancy), advantages and disadvantages of, 195–196 COA (Cloud-Oriented Architecture), 236–238 location independence and Next Big Thing, 238–239 Collaboration, composition-driven business processes and, 91 Commercial off the shelf (COTS) software, lack of agility in, 7, 145–146 Communication, in architecturedriven governance, 54 Community Cloud, 178 270 INDEX Complex Systems: emergence, as defining characteristic of, 15 fixed requirements discouraging emergence, 16–17 inherently collaborative nature of, 19 self-adapting nature of, 18 simplicity of, 16 successful innovation examples of, 17–18 as systems of systems, 16 Complex Systems Engineering (CSE), 73–87, 121, 255 best-effort quality, 76–80 best-effort quality, in action, 80–82 characteristics of, 75 demise of Enterprise IT and, 136 as Enterprise IT supertrend, 110 flash mobs and self-organization, 86–87 node-centric perspective and, 75–76 resilience and, 83–86 simplicity of, 74 traditional systems engineering contrasted, 73–74 Composition-centric approach to automation, 89–93 Configuration management, in Cloud Computing, 223–225 Consulting firms, SOA’s lack of success and, 29–30 Continuous Business Transformation, 110–112 Contracts See also Service Level Agreements (SLAs) contract variability, Agility Model and governance, 61 SOA and contracts, 34–38 Cookies, 227 CORBA (common object request broker architecture), 22, 38 Corporate governance, defined, 52 COTS (commercial off the shelf) software, lack of agility in, 7, 145–146 Cost efficiencies, Private Clouds and, 204 Create Employee Service, example of document-style interactions, 153–155 Crisis Points, of ZapThink 2020 Vision, 107, 113–116 Big Data explosion, 115, 116–119 collapse of Enterprise IT, 114 cyberwar, 115, 119–125 enterprise application crash, 115 fall of frameworks, 114–115 Generation Y, 109, 115, 128–131 IPv4 exhaustion, 114 CRM (customer relationship management), Cloud Computing and, 141, 212 Crowdsourcing: Complex Systems and, 18 Cyberwar Crisis Point, 124 Customer collaboration, in Agile Manifesto, Customer relationship management (CRM), Cloud Computing and, 141, 212 Cybersecurity, 125–128 scenarios, 125–127 software immune system and, 127–128 Cyberwar Crisis Point, 115, 119–125 protecting against, 122–125 DoDAF (Department of Defense Architecture Framework), 114, 245, 248, 254 Data: Big Data Explosion Crisis point, 115, 116–119 INDEX 271 data architecture, 246 Private Clouds and data centers, 203 Data, Cloud Computing and: consistency of, 190–193 data centers and, 236–238 garbage in, 214–215 garbage out, 216–217 portability of, 189 Data structure variability, Agility Model and governance, 62 DCOM (Distributed Component Object Model), 38 Deadlocks, states and Cloud Computing, 230 Declarative programming, 151–152 Deep Interoperability: as Enterprise IT supertrend, 110, 112–113 REST and, 168–170 “DELETE,” as used in REST, 162, 163, 164 Democratization of technology, 145 demise of Enterprise IT and, 136 as Enterprise IT supertrend, 109–110 Democratization of technology, as Enterprise IT supertrend, 109–110 Department of Defense Architecture Framework (DoDAF), 114, 245, 248, 254 Deployment models, of Cloud Computing, 177–178 Design-time governance, 55, 56 DevOps, 225 Distributed Component Object Model (DCOM), 38 Distributed computing, 150 Document-style Web Services example of, 153–155 RPC contrasted, 152–155 EA See Enterprise Architecture (EA) EAI (Enterprise Application Integration), 28 eBusiness, 44 Edison, Thomas, 80 Elasticity: Cloud Computing and, 179, 188–190 Cloud Computing and Service Level Agreements and, 210–211 Cloud Computing and utility, 205–206 failure expectations and plans for, 222 fake clouds and, 217–218 Private Clouds and, 203 Emergence, as defining characteristic of Complex Systems, 15 Emergent property, business agility as, Empowerment, of users, 101–102 End-to-end, continuous Hybrid Cloud testing, required of Public Cloud, 199 End-user license agreements (EULAs), 209, 210 Enterprise application crash Crisis Points, of ZapThink 2020 Vision, 115 Enterprise Application Integration (EAI), 28 Enterprise Architecture (EA), 9–10 Complex Systems and, 18 Continuous Business Transformation, 111 framework and methodologies of, 245–250 not being done, 13–14 professional credentialing and, 243–244 role today, 15 SOA’s lack of success and, 29 272 INDEX Enterprise Architecture Center of Excellence (EACOE), 111 Enterprise IT, Supertrends of, 108–110 Complex Systems Engineering, 110 deep interoperability, 110 democratization of technology, 109–110 global cubicle, 109 location independence, 108–109 Enterprise IT Crisis Point: Agile Architecture approach to project management, 136–138 application crash, 138–144 Cloud Computing and demise of, 114, 135–136, 141, 145 costs and steps in using Enterprise IT, 133–134 difficulty of replacing, 144–146 Enterprise operations context, of SLAs, 209 Enterprise Public Cloud Provider marketplace, 204–205 Enterprise Public Clouds, 197–200 Enterprise resource planning (ERP), Cloud Computing and, 141, 212 Enterprises: grown, not architected, 15 as systems of systems, Enterprise Service Bus (ESB), 187 pitfalls of, 44–47 as service intermediary, 47–49 SOA with, 40 SOA without, 47–50 Environment, in definition of architecture, 13 ERP (enterprise resource planning), Cloud Computing and, 141, 212 ESB (Enterprise Service Bus), 187 pitfalls of, 44–47 as service intermediary, 47–49 SOA with, 40 SOA without, 47–50 EULAs (end-user license agreements), 209, 210 Eventual consistency, Cloud Computing and, 191–193 Evolution, in definition of architecture, 13 Executives, SOA’s lack of success and, 30 eXtensible Markup Language (XML)-based interfaces, 152 Facebook, 219 Failure, expecting and planning for, in Cloud Computing, 221–222 See also Best-effort quality Fake clouds, 217–218 questions to ask regarding, 218–219 Fielding, Roy, 147, 156–157 definition of REST, 157 Financials, of Cloud providers, 208 Fine-grained governance, required of Public Cloud, 199 Flash Crowd (Niven), 86 Flash mobs, self-organization and, 86–87 Flexibility: designing for, 81–82 as key to profitability, longevity, success, Frameworks: Crisis Point of fall of, 114–115 EA and, 245–250 Functional programming, declarative nature of, 150–152 Garbage in, garbage out, Cloud Computing and, 214–217 Generation Y Crisis Point, 109, 115, 128–131 INDEX 273 “GET,” as used in REST, 162, 163, 164 Global Cubicle: demise of Enterprise IT and, 136 as Enterprise IT supertrend, 109 Governance, 51–72 Agility Model of, 60–63 architecture-driven, 54–57, 76 Butterfly Effect and, 70–72 Cloud Computing and, 207–208, 217 Complex Systems Engineering and, 110 composition-driven business processes and, 90, 91, 93, 101 corporate, defined, 52 demise of Enterprise IT and, 135 distinct parts of, 55–56 as driver of Services, fine-grained governance, required of Public Cloud, 199 interrelationships of quality, management and, 64–66 IT’s role in, 51–52 meta-policy and, 63–64 organization context, 52–54 quality and, 57–60 questions to ask regarding framework for, 54 stages of Agile Architecture governance, 67–69 user empowerment and, 101–102 Hall of mirrors problem, 11 HATEOAS (hypermedia as the engine of application state): Cloud Computing and, 231–232, 233–234 REST issues and, 158–159, 162–163, 166–167, 169 SPEAR and, 174 Heraclitus, 110 Heterogeneity, leveraging of, 50 HoneyMonkey project, of Microsoft, 127 Hosted Private Cloud, 177 Human-centric architecture-driven governance, 54, 67, 69 Human-centric SOA governance, 67–68 Human/technology systems, 17 Hybrid Clouds: defined, 178 end-to-end continuous testing, required of Public Cloud, 199 integration, required of Public Cloud, 199 Hypermedia: application state and, 231 as term used in REST, 161 Hypermedia as the engine of application state (HATEOAS): Cloud Computing and, 231–232, 233–234 REST issues and, 158–159, 162–163, 166–167, 169 SPEAR and, 174 Hypermedia-Oriented Architecture (HOA), 233–234 location independence and Next Big Thing, 238–239 Hypertext Transfer Protocol (HTTP), 156 IA (Information Assurance), 126 IANA (Internet Assigned Numbers Authority), 114 IaaS (Infrastructure-as-a-Service), Cloud Computing and, 178, 212–213 IBM, Rational Unified Process of, Immediate consistency, Cloud Computing and, 191–193 Imperative programming, 149–150 274 INDEX Implementation variability, Agility Model and governance, 61 Individual and interactions, in Agile Manifesto, Infinite capacity, Clouds and illusion of, 179 Information Assurance (IA), 126 Infrastructure-as-a-Service (IaaS), Cloud Computing and, 178, 212–213 Infrastructure costs, 212 Private Clouds and, 203 Infrastructure variability, Agility Model and governance, 61 Institute of Electrical and Electronics Engineers (IEEE), definition for architecture, 12 Integration-centric approach to automation, 89, 94 Interation, organizational behavior and, 82 Interative methodologies, Internet Assigned Numbers Authority (IANA), 114 IPv4 exhaustion, as Crisis Point in ZapThink 2020 Vision, 114 Isolated Tenancy Approach (third degree multitenancy), advantages and disadvantages of, 196–197 IT context, of Service, 42–43 Iterative/agile software project, 5–6 IT governance See Governance IT infrastructure vendors, SOA’s lack of success and, 28–29 Java Message Service (JMS) interface, 175 Java Remote Method Invocation (RMI), 151 Knowledge management, in architecture-driven governance, 55 Kuhn, Thomas, 103, 106, 113 Legacy applications: options for Cloud Computing, 182–183, 187–189 SOA and composition-driven business processes and, 92, 95, 101 Location independence: as characteristic of Cloud Computing, 179 as Enterprise IT supertrend, 108–109 Next Big Thing in Cloud Computing and, 238–241 LOIC (Low Orbit Ion Cannon), 124 Loose coupling: complex systems and, 75 document-style and, 152–155 SOA and, 32–33, 37–38, 61 Lottery fallacy, 126–127 Low Orbit Ion Cannon (LOIC), 124 Managed hosting provider context, of SLAs, 209 Management, interrelationships of quality and governance and, 64–66 Management-quality feedback loop, 66 Manes, Anne Thomas, 23 “Many-to-many-to-many,” 32, 33 Maps PlaceFinder Geocoding API, of Yahoo!, 167–168 MasterCard, 122 MDA (Model Driven Architecture), 11 Measured service, as characteristic of Cloud Computing, 179 Measurement, frequency of, 82 INDEX 275 Meta-architecture, 12 Meta-best practices, 24 Metadata: metadata artifacts, 53 role in SOA, 37 Meta-meta-models, 11 Meta-methodology, 249–250 Meta-policies, 57 feedback loop, 118–119 governance and, 63–64 Meta-requirements: agility and, 8, 90–91, 100–102 agility and quality, 77 business agility and SOA, 12 Methodologies, EA and, 245–250 Microsoft Azure, 204 Microsoft.NET, 151 Microsoft Research, HoneyMonkey project of, 127 Middleware, SOA’s lack of success and, 28–29 Millennials See Generation Y Crisis Point Model Driven Architecture (MDA), 11 Modeling, Agile Architecture and, 98–100 Moore’s Law, 116–117 Multitenancy, Cloud Computing and, 179, 193–197 Clustered Shared Schema Approach (second degree), 195–196 Isolated Tenancy Approach (third degree), 196–197 Shared Schema Approach (first-degree), 193–195 National Institute for Standards and Technology (NIST): Cloud deployment scenarios, 187–189 definition of Cloud Computing, 177, 236 interoperability and portability standards, 188–190 Negroponte, Nicholas, 257 NET Remoting, 151 Network access, broad, as Cloud Computing characteristic, 179 Network effect, Complex Systems and, 18 Next-generation modularization, 145 NIST (National Institute for Standards and Technology): Cloud deployment scenarios, 187–189 definition of Cloud Computing, 177, 236 interoperability and portability standards, 188–190 Niven, Larry, 86 Node-centric perspective, complex systems engineering and, 75–76 Object-Oriented Analysis and Design (OOAD), 37 Offshoring, Enterprise IT and, 134–135 OOAD (Object-Oriented Analysis and Design), 37 Open source software, Cloud Computing and, 213–214 Open standards, deep interoperability, 112–113 Oracle Database Cloud, 218 Organization of systems, in definition of architecture, 13 Outsourcing, Enterprise IT and, 134–135 PaaS (Platform-as-a-Service), Cloud Computing and, 178, 183–184 276 INDEX Partition tolerance, Cloud Computing and, 191 PayPal, 122 Performance objectives (POs), 254 Persistence tier, Cloud Computing and, 230–232, 234–235 Platform-as-a-Service (PaaS), Cloud Computing and, 178, 183–184 Platform-level security measures, required of Public Cloud, 199 Policies See also Meta-policies as driver of Services, variability, Agility Model and governance, 62 Portfolio management, in IT, 137–138 “POST,” as used in REST, 162, 163, 164 Post Finance, 122 Pricing models, Cloud Computing and, 206–207 Private Clouds, 177 disadvantages of, 202–205 governance and, 217 less secure than Public Clouds, 200–202 Public Clouds contrasted, 197–198 Service Level Agreements and, 210 vendors and, 183–184 Proactive strategic part, of business agility, 6–7 Process variability, Agility Model and governance, 61 Project management, Agile Architecture approach to, 136–138 Public Clouds: Amazon Cloud crashes, 219–221 capabilities required of, 198–199 Enterprise Public Cloud and, 197–200 governance and, 217 more secure than Private Clouds, 200–202 multitenancy and, 193 Private Clouds contrasted, 197–198 Public Cloud Providers, 177 “PUT,” as used in REST, 162, 163, 164 QoS (quality of service) metrics, 56 Quality: best-effort quality, 76–80 best-effort quality, in action, 80–82 change and, 58–60 governance and, 57–60 interrelationships of management, governance, and, 64–66 traditional approach to, 58 Quality of service (QoS) metrics, 56 Race conditions, states and Cloud Computing, 230 Rackspace, 204 Rational Unified Process, of IBM, Reactive part, of business agility, Reliability, Cloud Computing and Service Level Agreements and, 210–211 Remote Method Invocation (RMI), of Java, 151 Remote Procedure Call (RPC) programming challenges of, 150–151 in Create Employee Service example, 154 Web Services and, 152–155 “Representation,” as used in REST, 161 Representational State Transfer (REST), 149–176 See also Representational State Transfer (REST)-based SOA INDEX 277 as abstraction, 157 Agility Model and, 159–160 architectural constraints on, 162–163 as architectural style, 156, 157 best uses, 160 deep interoperability and, 168–170 definitions, 155–157 as distributed hypermedia application, 157–158 HATEOAS and, 158–159, 162–163, 166–167, 169 hypermedia-oriented architecture and, 233–234 precursors of, 149–155 Richardson Maturity Model and, 158–159 vocabulary of, 161–162 Web Services and, 163–168 Representational State Transfer (REST)-based SOA, 27, 40 Cloud Computing and states, 225–232 SOA in, 170–173 SPEAR initiative and, 173–176 “Representations of business capabilities,” 32 Reprovisioning, in Cloud Computing, 224 Request for Proposal (RFP), for Agile architecture: mistakes in, 250–251 pointers for, 252–253 Requirements, of software: business agility and, 6–7 changing, 7–8 fixed, and lack of emergence, 16–17 flexibility and, myth of complete, well-defined, Resilience, 83–86 at infrastructure level, 85 Service policies and, 85 ways to provide, 84 “Resource,” as used in REST, 161 Resource-Oriented Architecture (ROA), 237 Resource pooling, as characteristic of Cloud Computing, 179 Resources, REST architectural constraints and, 162 Resource state, Cloud Computing and, 226, 230–232, 235 Retrospectives, Scrum use and, 10 Revolutions, difficulty recognizing while in progress, 105–108 Richardson, Leonard, 158 Richardson Maturity Model (RMM), 158–159, 169 Agility Model and, 159–160 ROA (Resource-Oriented Architecture), 237 RPC (Remote Procedure Call) programming challenges of, 150–151 in Create Employee Service example, 154 Web Services and, 152–155 Run-time governance, 56 Run-time work flow, 235–236 Salesforce.com, 209–210, 215 SCM (supply chain management), Cloud Computing and, 141, 212 Scrum: best practices, 10 meta-methodology, 11 Scrum Buts, 10 Complex Systems and, 18–19 schools of thought on, 10–11 Security measures: platform-level, required of Public Cloud, 199 Public versus Private Clouds, 200–202 278 INDEX Self-descriptive messages, REST architectural constraints and, 162 Self-healing, composition-driven business processes and, 91 Self-organization, 86–87 Self-reference paradoxes, 11 Self service, as Cloud Computing characteristic, 179 Semantics tooling, Complex Systems and, 18 Semantic variability, Agility Model and governance, 62 “Server,” as used in REST, 161 Server utilization, Private Clouds and, 203 Service, defining of, Service Level Agreements (SLAs), Cloud Computing and, 208–211 contexts of, 209–211 Service models, of Cloud Computing, 178 Service Orientation (SO) conversation, 42–44 Service Oriented Architecture (SOA), 9, 21–50 best practices and, 24–28 Centers of Excellence, 27 Complex Systems and, 16–17 composition-driven business processes and, 93–96 demise of Enterprise IT and, 145 document-style Service interactions and, 153 as evolutionary, not revolutionary, 105 framework and methodologies of, 245–250 freeing architecture from underlying infrastructure, 44–50 governance and Complex Systems, 17 hindrances to success of, 28–31 location independence and Next Big Thing, 238–241 loose coupling and, 32–33, 37–38 move to composition-centric approach to automation and, 89–93 multi-contracts and policy-driven behavior, 34–38 outside the box thinking about, 26–28 quality and, 77 REST and Cloud Computing, 227 in REST-based SOA, 170–176 REST contrasted, 163–165 Service as business abstraction, 21–23 Service as core of, 31–33 Service Orientation conversation and, 42–44 “SOA is dead” meme, 23–25 as style of Enterprise Architecture, 156 Web Services and, 27, 38–40 what’s not part of, 22 Service policies, resilience and, 85 Services: composition-centric approach to automation and, 90 as core of SOA, 31–33 Shared Schema Approach (firstdegree multitenancy), advantages and disadvantages of, 193–195 Shopping carts, REST state example of Cloud Computing and, 229–232 Simple Object Access Protocol See SOAP) SOA See Service Oriented Architecture INDEX 279 SOAP (Simple Object Access Protocol), 39, 152 Web Services and REST, 163–165 Social media, Cyberwar Crisis Point and, 123–124 Soft state, Cloud Computing and, 192 Software See also Applications; Legacy applications gap between functions and business needs, not-so-agile updates to, Software-as-a-Service (SaaS), Cloud Computing and, 178, 218–219 Software Development (SD) Triangle, 78 Software/human systems, 8–10 Software licenses, Cloud Computing and, 212–214 Software Security Assurance (SSA), 126 Software vendor context, of SLAs, 209 SPEAR architecture, of U.S Coast Guard, 173–176, 229 Spiral methodology, Sprints, Scrum use and, 10 States, Cloud Computing and concept of: data and, 229–230 REST and, 225–232 ways to maintain, 227–229 Structure of Scientific Revolutions, The (Kuhn), 106 Stuxnet, 107, 119–121, 123 Sun Microsystems, 171 Supply chain management (SCM), Cloud Computing and, 141, 212 Systems of systems, Complex Systems and, 16–17 Taylor, Frederick Winslow, Technology, democratization of, 145 demise of Enterprise IT and, 136 as Enterprise IT supertrend, 110 Technology architecture, 246 Technology-centric architecturedriven governance, 67–69 Technology-centric SOA governance, 67–68 TSE (traditional systems engineering), contrasted to Complex Systems engineering, 73–74 The Open Group Architecture Framework (TOGAF), 14, 114, 243–244, 246, 248, 249 Tiered pricing, Cloud Computing and, 206–207 Tight coupling, RMI and, 151–152 Tim Woodman pattern, 49–50 TOGAF (The Open Group Architecture Framework), 14, 114, 243–244, 246, 248, 249 Traditional systems engineering (TSE), contrasted to Complex Systems Engineering, 73–74 Training, in architecture-driven governance, 54 trust.salesforce.com, 210 Twitter, 17 Ubiquitous Computing, 124 UDDI (Universal Description, Discovery, and Integration), 39, 164 “Uniform Resource Identifier (URI),” as used in REST, 161 Uniform Resource Names (URNs), 161 Universal Description, Discovery, and Integration (UDDI), 39, 164 280 INDEX URNs (Uniform Resource Names), 161 “URI (Uniform Resource Identifier),” as used in REST, 161 U.S Coast Guard SPEAR architecture, 173–176, 229 Users: empowerment of, 101–102 as part of agile system, Variability, planning for, 84 Vendor-centric nature of Cloud Computing, 179–184 Versioning, of Service, 63–64 Viral marketing, Complex Systems and, 17 Virtual machine (VM) architecture, of Java, 151 Virtual Private Clouds (VPCs), 201–202 Virtual Private Networks (VPNs), 179 WADL (Web Application Description Language), 171 Waterfall software project, Web Application Description Language (WADL), 171 Web-Oriented Architecture (WOA), location independence and Next Big Thing, 239–240 Web Services, 152–153 REST contrasted, 163–168 RPC programming and, 152–155 RPC versus document-style, 153–155 SOA and, 27, 38–40, 49 Web Services Description Language (WSDL), 31, 37–40, 152–153, 155 REST and, 163–165, 166, 171 Wikileaks, 122, 123, 124 Wikipedia, definition of REST, 156, 157 WOA (Web-Oriented Architecture), location independence and Next Big Thing, 239–240 Working software, in Agile Manifesto, WS-Ã, 39–40 WSDL (Web Services Description Language), 31, 37–40, 152–153, 155 REST and, 163–165, 166, 171 Yahoo! Maps PlaceFinder Geocoding API, 167–168 Zachman Framework, 14, 42, 114, 243, 248–249 ZapThink, xvi, 4, 12, 23, 77, 94, 236 definition of business processes, 89 ESB and, 47, 49–50 Web Services and, 39 ZapThink 2020 Vision, 105–131, 248, 249 Big Data Crisis Point, 116–119 coming paradigm shift and revolution in progress, 105–108 Continuous Business Transformation and, 110–112 Crisis Points of, 107, 113–116 cybersecurity and, 125–128 Cyberwar Crisis Point, 119–125 Deep Interoperability, 110, 112–113, 168–170 Enterprise IT Crisis Point, 114, 134–136 Generation Y Crisis Point, 109, 115, 128–131 poster, xvi, xvii ... what the Agile Architecture Revolution is all about Hold on to your hats! You’re in for a wild ride Jason Bloomberg September 2012 THE AGILE ARCHITECTURE REVOLUTION The Agile Architecture Revolution: ... Can We Do Agile Enterprise Architecture? 243 Frameworks and Methodologies and Styles, Oh My! 245 The Beginning of the End for Enterprise Architecture Frameworks How to Buy an Agile Architecture. .. PART ONE Enterprise as Complex System CHAPTER 1 Introducing Agile Architecture Deconstructing Agile Architecting Software/Human Systems Meta Thinking and Agile Architecture 10 Defining Architecture: