Addressing Systemic Complexity with SOA and Cloud?????SOA + Cloud?????Tony Shanmail@tonyshan.comJuly 15, 2011
Contents at a Glance• Introduction• What is SOA• What is Cloud• Why SOA• Why Cloud• Why Combination• State of SOA• State o...
IntroductionAddressing Systemic Complexity 3© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.
Concept of SOAThe Open Group• Service-Oriented Architecture(SOA) is an architectural stylethat supports serviceorientation...
Definition of Cloud ComputingCloud Computing is a model for enabling convenient, on-demand network access to a sharedpool ...
SOA BenefitsGreaterinteroperability• SOA, and theindustrystandardsunderpinning it,enable existingsiloedapplications tointe...
Value Proposition of Cloud•Enhance quality of service: improve the stability and reliability of services via Cloud-based s...
Why SOA+Cloud Combined?SOA• Service Orientation• Mostly software-intensive• Application integration• Loose coupling• Reuse...
SOA Landscape9© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity
State of Cloud10© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic ComplexitySource: ...
© 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 11Addressing Systemic Complexity
Barriers to Successful SOA12© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Comple...
Top 10 Cloud Adoption InhibitorsRisk-Testing•How is the cloudcomputing vendormanaging risk?Data Location•Where is the data...
How are cloud solutions crafted?Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Conf...
What these lead to…Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 15P...
How to Effectively Deal withComplexity?Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary a...
State of ArtAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 17Source: ...
WisdomAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 18The essential ...
In Search for a Pragmatic ApproachAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Co...
Key AreasNotationTechnologiesSpecificationModulesAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Pro...
21Increasing Disparate RepresentationsAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary an...
Semantic NotationsAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 22So...
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 23Increasing DynamicsS...
Service-Oriented Design AcceleratorAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and C...
25Application Framework Reference CardAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary an...
Increasing FragmentedActivities on SpecificationsAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Pro...
Stack of StandardsAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 27Fo...
28Increasing ModulesEnterprise Portal: Role based portal thatis available 24x7. Provides single point ofentry for all user...
Cloudonomic ParadigmAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 29...
Best PracticesAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 30Hybrid...
Case Study of Healthcare VerticalAddressing Systemic Complexity 31© 2011 Tony Shan. All rights reserved. Proprietary and C...
Make it Simple…Addressing Systemic Complexity 32© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.
Thank YouMerciGrazieGraciasObrigadoDanke JapaneseFrenchRussianGermanItalianSpanishBrazilian PortugueseArabicTraditional Ch...
Upcoming SlideShare
Loading in...5
×

Addressing Systemic Complexity with SOA and Cloud

397

Published on

Presentation at "SOA in Healthcare" Conference. The talk describes a practical approach to deal with the complexity of SOA+Cloud combined, focusing on the notation, modules, specifications, and technologies as well as best practices and lessons learned.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
397
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Addressing Systemic Complexity with SOA and Cloud

  1. 1. Addressing Systemic Complexity with SOA and Cloud?????SOA + Cloud?????Tony Shanmail@tonyshan.comJuly 15, 2011
  2. 2. Contents at a Glance• Introduction• What is SOA• What is Cloud• Why SOA• Why Cloud• Why Combination• State of SOA• State of Cloud• Barriers to Successful SOA• Barriers to Successful Cloud• State of Art of Complexity Management• Need Pragmatic Method• Increasing Disparate Representations• Increasing Dynamics• Increasing Fragmented Activities on Specifications• Increasing Components• Best Practices• Wrap-upAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 2
  3. 3. IntroductionAddressing Systemic Complexity 3© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.
  4. 4. Concept of SOAThe Open Group• Service-Oriented Architecture(SOA) is an architectural stylethat supports serviceorientation, which is a way ofthinking in terms of services andservice-based development andthe outcomes of services.OASIS• SOA is a paradigm for organizingand utilizing distributedcapabilities that may be underthe control of differentownership domains. It providesa uniform means to offer,discover, interact with and usecapabilities to produce desiredeffects consistent withmeasurable preconditions andexpectations.4© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity
  5. 5. Definition of Cloud ComputingCloud Computing is a model for enabling convenient, on-demand network access to a sharedpool of configurable computing resources (e.g., networks, servers, storage, applications,and services) that can be rapidly provisioned and released with minimal managementeffort or service provider interaction. This cloud model promotes availability and iscomposed of five essential characteristics, three service models, and four deploymentmodels.-- NIST Definition, V155© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity
  6. 6. SOA BenefitsGreaterinteroperability• SOA, and theindustrystandardsunderpinning it,enable existingsiloedapplications tointeroperateseamlessly andin an easier tomaintainmanner thanany traditionalEAI solution.Increased reuse• Once legacysystems andapplications areservice enabled,these servicescan be reused,which results inreduced ongoingdevelopmentcosts and resultsin reduced timeto market.Further,businessprocesses builtas anorchestration ofservices can alsobe exposed asservices, furtherincreasing reuse.More agilebusinessprocesses• SOA reduces thegap betweenthe businessprocess modelandimplementation.This enableschanges tobusinessprocessesalreadyimplemented asorchestrationsof services to beto be easilycaptured andimplemented.Improved visibility• SOA can giveimprovedbusinessvisibility byenablingbusinesscapabilitiesexposed asservices, and thestatus of in-flight businessprocessesautomated withBusiness processmanagement(BPM)technology, tobe rapidlyintegrated intoservice-enabledenterpriseportals aidingbusinessdecision-making.Reducedmaintenancecosts• SOAdevelopmentencouragesduplicatedoverlappingbusinesscapabilities(services) thatspan multipleapplications andsystems to beconsolidatedinto a smallnumber ofshared services.Compliance andgovernance• By realizingbetter and morestandardizedoperationalprocedures, SOAprovides thebasis for acomprehensivesecuritysolution, andenables bettervisibility intobusinessoperations andexceptionconditions.6© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity
  7. 7. Value Proposition of Cloud•Enhance quality of service: improve the stability and reliability of services via Cloud-based solutions•Improve flexibility: scale infrastructure resources on demand, or develop a hybrid approach,maintaining some fixed computing capacity in private cloud or your own data centers while using publiccloud for additional needs•Product-agnostic and vendor-independent: non-biased approach enables a reliable foundation of opentechnology and methodology for future growth and evolutionEnrichedcapabilities•Empower the alignment of IT and business: the increased adaptation and agility of IT enable betteralignment•Increase speed to value: reduce learning-curve time significantly•Strategize IT planning: balance the immediate needs with the long-term goalsIncreasedagility•Reduce expenses: achieve economies of scale through the right mix of use of cloud computinginfrastructure•Avoid capital expenditure: shift IT spending to operational investments•Implement greener IT: reduce your business’ carbon footprint, as the compute capacity of the cloud ishigher than traditional data centersLoweredcost7© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity
  8. 8. Why SOA+Cloud Combined?SOA• Service Orientation• Mostly software-intensive• Application integration• Loose coupling• Reuse via shared services• Asset-based use• Service components andcomposition• Predominantly usedwithin the enterpriseCloud• XaaS• Mainly hardware-focused• Resource provisioning• On-demand scalability• Multi-tenancy• Utility-based consumption• Infrastructure pooling andoutsourcing• New business model forservice delivery8© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity•Increased agility•Faster time to market•More cost savings•Reduced integration•Easier outsourcing
  9. 9. SOA Landscape9© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity
  10. 10. State of Cloud10© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic ComplexitySource: Gartner
  11. 11. © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 11Addressing Systemic Complexity
  12. 12. Barriers to Successful SOA12© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic ComplexityInitiatives solely ledand driven by techiesInsufficient semanticsin service compositionDisconnection betweentraditional educationand real-world SOAimplementation needsAbsence of holisticroadmaps withspecificityLack of well-definedservice models(business andtechnical)Gap between logicalarchitecture andinfrastructureAd-hoc governance(dictatorship oranarchy)Home-grown referencemodelsProduct lock-in with noor limitedinteroperabilityInability to quantifyROI/TCO andimproper-sizingProject-centricexecution withoutreuse/sharingdisciplinesImmaturespecifications andstandardization
  13. 13. Top 10 Cloud Adoption InhibitorsRisk-Testing•How is the cloudcomputing vendormanaging risk?Data Location•Where is the databeing stored? In-country or out of thecountry? Whatrestrictions and lawsare placed upon thedata dependent onlocation of storeddata?Data and CodePortability•Once the data hasbeen put onto thecloud computingsystem, how difficultwill it be to get thedata back out?Data Loss•Does the cloudcomputing systemback-up and restoredata?Data Privacy•Does the databecome morevulnerable when it islocated on anexternal cloudcomputing system?Source: Adapted and extended from Gartner and InformationWeek reports in 2009 and 2010.Vendor Viability•What will happen ifthe cloud computingvendor goes out ofbusiness?Performance•How can SLAguaranteeperformance?ROI•Does operationalexpense alwaystrump capitalexpense, at least intechnologyinvestment?Security•What are thevulnerabilities in theCloud architecture?Control•How can a cloudprovider be trustedthat they care aboutyour IT processing asmuch as you do?© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity 13
  14. 14. How are cloud solutions crafted?Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 14
  15. 15. What these lead to…Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 15Page 1 of 2
  16. 16. How to Effectively Deal withComplexity?Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 16
  17. 17. State of ArtAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 17Source: Wikipedia
  18. 18. WisdomAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 18The essential complexity isirreducible.Fred Brooks - Author of “The Mythical Man-Month”- Coined “Computer Architecture”- 1999 Turing Award
  19. 19. In Search for a Pragmatic ApproachAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 19Tomorrow’s computing systemscannot be built using methods oftoday. [Computing ResearchAssociation (CRA) report]We cant solve problems byusing the same kind ofthinking we used when wecreated them. [Albert Einstein]Conquering Complexity – one of five“deliberately monumental" researchchallenges, each requiring "at least adecade of concentrated research inorder to make substantive progress”.[“Grand IT Research Challenges” reportsupported by NSF]
  20. 20. Key AreasNotationTechnologiesSpecificationModulesAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 20
  21. 21. 21Increasing Disparate RepresentationsAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential.
  22. 22. Semantic NotationsAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 22Source: The “Physics” of Notations
  23. 23. Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 23Increasing DynamicsSIPMTOM REST SCA XOPXPATHDSLAJAXITIL CMMWOACOBIT POXPaaSSaaSIaaS
  24. 24. Service-Oriented Design AcceleratorAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 24Access & Interaction LayerIntegration/Communications LayerServices & Components LayerComposite Services LayerBusiness Process LayerEnterprise Resources LayerReference Model of Solutions Architecture for N-Tier ApplicationsDesigned by Tony ShanJetspeedLiferayJOSSOYaleCASAcegiModeling&DevelopmentToolsEclipse,NetbeansAnt,MavenCVS,Subversion,Bugzilla,FxCopJUnit,NUnit,CruiseControlArgoUML,StarUMLCrosscuttingAspects&PatternsMicrosoftEnterpriseLibraryMicrosoftApplicationBlocksGoFdesignpatternsJavaEEpatternsAspectJ,Spring,JBossAOPApplication&ServiceFrameworksJSF,Tapestry,WicketRIFE,SeamKeelSpringDWR,Echo2,JSON-RPC,DojoWebWork,Struts,BeehiveHostingEnvironmentJBossAppServerTomcatXenGridEngine,GlobusLAMPSecurityOpenSSHJacksumOpenSAMLEnhydraOysterOpenSSLOperationalManagementNagiosXMOJODMTFCIMJMX/SNMPWEBMServicesActiveBPELjBPMOpen-XchangeSharkJaWEWS-BPELjUDDIebXMLRegistrySCASDOAxisREST, AjaxDroolsSweetRulesNxBREServiceMixMuleActiveMQOpenJMSOpenESBDerbyOpenCMSSugraCRMMondrianWeka
  25. 25. 25Application Framework Reference CardAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential.
  26. 26. Increasing FragmentedActivities on SpecificationsAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 26WS-SecurityWS-AttachmentsWS-AddressingWS-Policy WS-PolicyAttachmentWS-AtomicTransactionWS-BusinessActivityWS-RXWS-CDL WS-TrustWS-FederationWS-CoordinationWS-TX WS-Discovery WS-SXWS-ResourceWS-EventingWS-Notification WS-TopicsWS-SecureConversation WS-ReliableMessaging WSRFWSEWS-TransferWS-EnumerationWS-MEX
  27. 27. Stack of StandardsAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 27FoundationPresentationManagementComposition/Orchestration/ConstructionProcessMessagingXML Processing· DOM· SAX· XPath· XSLT· XQuery· .Net XMLSerialization· JAXB· SDO· StAXDescription· XML· XML Schema· WSDL· XML Info Set· XOP/MTOM· SML· DMCBX· RELAX NG· SchematronAssertion LangCommunications and Events· Transport: SSL/TLS· Network: IPSec· BEEP· HTTP/IIOP/MQ· WS-Eventing· WS-Notification· WS-AddressingSecurity· WS-Security· WS-SecureConversation· WS-Federation· SAML· Liberty Alliance IDFF· WS-Trust· XKMS· XACML· XrML· EPALInteroperability· WS-I Basic Profile· WS-I Basic SecurityProfile· WS-I Reliable SecureProfile· GovernanceInteroperabilityFramework (GIF)· Reusable AssetSpecification (RAS)· DMTF CIMResources· WSRF· WSRF-ResourceProperties· WSRF-ResourceLifetime· WSRF-ServiceGroup· WSRF-BasicFaults· WS-Transfer· RRSHB· WS-EnumerationTransaction· WS-Coordination· WS-Business Activity· WS-Atomic Transaction· WS-Context· WS-CF· WS-TXM· WS-TXSemantics· RDF· WSDL-S· SA-WSDL, SA-REST· OWL-S, RDF/S· SWSO, WSMO· SWSL, WSML· SOA-S, FEARMO,ODMQoS· WS-ReliableMessenging· WS-Reliability· WS-RXDiscovery· OWL· WS-Discovery· WS-MetadataExchange· UDDI· ebXML· SwSA· WS-Policy· WS-PolicyAttachment· WS-SecurityPolicy· WS-Manageability· WS-Management· WSDM· WS-Provisioning· WSDM· WSRP· XUL· XAML· XBL· XForms· MXML· Ajax· WS-Choreography· BPMN· BPDM· BPML/BPQL· XPDL· WSCI· CDL4WS· BMM· UML· OAGIS· BPEL· WS-CAF· WSE· WCF· JAX-WS· SAAJ· SCA· Axis· SOAP· REST· JSON· SwA· WS-I Attachment Profile· XML Security: XML Encryption, XML Signature
  28. 28. 28Increasing ModulesEnterprise Portal: Role based portal thatis available 24x7. Provides single point ofentry for all users, multi-channel support,consistent look and feel, access to businesscapabilities based on role.Custom Applications: These are either built on anApp Server, Portal or proprietary thick client.Application Framework required to leverage reuse.Examples: Logging, Exception handling, data services,application configuration, monitoring, search framework,notification framework, service proxy, Single Sign-OnPackaged Applications: These are the best of the breedpackaged application that also act as the system of record fora particular business function.Enterprise Services: Basic services required across theenterprise. Examples: Directory Service, Content Management,Search, eMail, Calendar, IM, Discussion Forum, White Board, etc. Business ProcessManager: Configureand automate businessprocess. Providebusiness users thecapability to modify thebusiness process &policies.Enterprise Service Bus: Route services to the appropriatedestination; receive and transmit messages in any protocol, providemessage transformation, routing, validation, auditing, security,monitoring and reporting services.Service Registry:Service registrycontaining serviceproperties such asservice capabilities,parameters, servicelevels, etc.Shared DataServices: Extract,Transform & Load (ETL),Electronic DataInterchange (EDI),Enterprise InformationIntegration Data Quality(Matching Engine, MasterData Management)Service Manager:Manage servicelifecycle across theenterprise.Enterprise ApplicationIntegration: Traditionalenterprise integration approach.Provide Application Adapters,Business Process, Messaging,Security, etc. capabilities. Mostlyproprietary in nature andapplication integration generallyimplemented as a point-to-pointintegration on a Hub..Mainframe Application :Access data via gatewaysEnterprise Security: Provideuser authentication,authorization, identifymanagement, profilemanagement, delegated admin,etc.Business ServiceManagement: Monitoring,capacity planning, utilitycomputingMapping SOA Reference Architectureto the Enterprise SOA Maturity ModelTraditionalDevelopmentDevelop WebApplicationsCompositeApplicationsAutomateBP© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Legacy Application: Applications that do not have open APIs & are not web basedSource: SOA Practitioners’ Guide
  29. 29. Cloudonomic ParadigmAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 29Service Integration & Management Platform and Lifecycle EngineeringCloud Computing FoundationPrinciples Methodology Process Techniques Tools Patterns Policy Standards Practices MaturityDevSupport•Collaboration•AssetMgmt•Build Mgmt•Test Mgmt•ReleaseMgmtBizSupport•CustomerMgmt•PartnerMgmt•RevenueMgmt•BillingMgmtOperationSupport•IncidentMgmt•ChangeMgmt•ConfigMgmt•SLA MgmtProviderSupport•ProductMgmt•InventoryMgmt•CapacityMgmt•ResourceManagerInteractionEnablementVirtual HostingRuntimeCloud Service FactoryPlan Define Model Implement DeployChannel Device User exp ParticipateOnboard Catalog Provision ReportsUI Process Service DataSecurity Repository Metering MonitorFederated Composite Cloud FabricAggregateMashupBundle
  30. 30. Best PracticesAddressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 30HybridAttitude Program
  31. 31. Case Study of Healthcare VerticalAddressing Systemic Complexity 31© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Business Challenge• Healthcare cost containmentservices to U.S. payers andinsurance providers• An average annual increase ofover 40% for the last four years• Requires continuousmanagement of and investmentin processing capacity andutilities, including power andcooling• Using traditional servers andsuffering from occasional sub-par system performanceSolution• The cloud solution provides acomprehensive set of buildingblocks giving the company theflexibility to build systems in away that was most applicable totheir business• The public cloud has all thepieces needed at a price pointwell below the competition• Utilizing the computing, storage,and queuing capability in thepublic cloud to enable the claimprocessing system capacity toincrease and decrease asrequired to satisfy the servicelevel agreements (SLAs)• Meet the needs of requiringmassive amounts of computingresources that far exceed theexisting system, withoutpurchasing, housing andmaintaining the serversthemselvesResult• Providing retrospective claimprocessing services which isessentially processing multipleyears’ worth of data at a time• Encrypt and send the data thatneed processed to the cloudwhile the majority of the PHI isretained in-house and isreconnected with the processeddata upon its return• The firm was able to produce aHIPAA-compliant application thatscales as they do• The public cloud is a great fit forthe company because it allowsthem to economically expandand contract their computingresources to match the ebb andflow of the claim volume withoutmaking any long-term financialcommitments or capitalexpenditures
  32. 32. Make it Simple…Addressing Systemic Complexity 32© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.
  33. 33. Thank YouMerciGrazieGraciasObrigadoDanke JapaneseFrenchRussianGermanItalianSpanishBrazilian PortugueseArabicTraditional ChineseSimplified ChineseHindiRomanianThaiKoreanMultumescContact: Tony ShanEmail: mail@tonyshan.comWeb: http://tonyshan.com© 2006-2011 Tony Shan. All rights reserved.Duplication, reproduction or disclosure ofthe contents in this document is prohibitedwithout prior written permission of theauthor.33© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity

×