Intelligent agent that can understand natural language queries and provide responses by accessing various systems and aggregating information. Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. Integration Platform: Integrate disparate systems and applications. Provide connectivity, data transformation, routing, orchestration, monitoring and management capabilities. Data Services: Services to access, integrate and analyze enterprise data. Examples: Master Data Management, Data Warehousing, Business Intelligence, Analytics. Collaboration Platform: Enable collaboration between users, teams and communities. Provide capabilities like document management, project management, team rooms, wikis, blogs, etc

1. Addressing Systemic Complexity with SOA and Cloud
?????
SOA + Cloud
?????
Tony Shan
mail@tonyshan.com
July 15, 2011

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-up
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 2

3. Introduction
Addressing Systemic Complexity 3© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.

4. Concept of SOA
The Open Group
• Service-Oriented Architecture
(SOA) is an architectural style
that supports service
orientation, which is a way of
thinking in terms of services and
service-based development and
the outcomes of services.
OASIS
• SOA is a paradigm for organizing
and utilizing distributed
capabilities that may be under
the control of different
ownership domains. It provides
a uniform means to offer,
discover, interact with and use
capabilities to produce desired
effects consistent with
measurable preconditions and
expectations.
4© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity

5. Definition of Cloud Computing
Cloud Computing is a model for enabling convenient, on-demand network access to a shared
pool of configurable computing resources (e.g., networks, servers, storage, applications,
and services) that can be rapidly provisioned and released with minimal management
effort or service provider interaction. This cloud model promotes availability and is
composed of five essential characteristics, three service models, and four deployment
models.
-- NIST Definition, V15
5© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity

6. SOA Benefits
Greater
interoperability
• SOA, and the
industry
standards
underpinning it,
enable existing
siloed
applications to
interoperate
seamlessly and
in an easier to
maintain
manner than
any traditional
EAI solution.
Increased reuse
• Once legacy
systems and
applications are
service enabled,
these services
can be reused,
which results in
reduced ongoing
development
costs and results
in reduced time
to market.
Further,
business
processes built
as an
orchestration of
services can also
be exposed as
services, further
increasing reuse.
More agile
business
processes
• SOA reduces the
gap between
the business
process model
and
implementation.
This enables
changes to
business
processes
already
implemented as
orchestrations
of services to be
to be easily
captured and
implemented.
Improved visibility
• SOA can give
improved
business
visibility by
enabling
business
capabilities
exposed as
services, and the
status of in-
flight business
processes
automated with
Business process
management
(BPM)
technology, to
be rapidly
integrated into
service-enabled
enterprise
portals aiding
business
decision-
making.
Reduced
maintenance
costs
• SOA
development
encourages
duplicated
overlapping
business
capabilities
(services) that
span multiple
applications and
systems to be
consolidated
into a small
number of
shared services.
Compliance and
governance
• By realizing
better and more
standardized
operational
procedures, SOA
provides the
basis for a
comprehensive
security
solution, and
enables better
visibility into
business
operations and
exception
conditions.
6© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity

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 public
cloud for additional needs
•Product-agnostic and vendor-independent: non-biased approach enables a reliable foundation of open
technology and methodology for future growth and evolution
Enriched
capabilities
•Empower the alignment of IT and business: the increased adaptation and agility of IT enable better
alignment
•Increase speed to value: reduce learning-curve time significantly
•Strategize IT planning: balance the immediate needs with the long-term goals
Increased
agility
•Reduce expenses: achieve economies of scale through the right mix of use of cloud computing
infrastructure
•Avoid capital expenditure: shift IT spending to operational investments
•Implement greener IT: reduce your business’ carbon footprint, as the compute capacity of the cloud is
higher than traditional data centers
Lowered
cost
7© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity

8. Why SOA+Cloud Combined?
SOA
• Service Orientation
• Mostly software-intensive
• Application integration
• Loose coupling
• Reuse via shared services
• Asset-based use
• Service components and
composition
• Predominantly used
within the enterprise
Cloud
• XaaS
• Mainly hardware-focused
• Resource provisioning
• On-demand scalability
• Multi-tenancy
• Utility-based consumption
• Infrastructure pooling and
outsourcing
• New business model for
service delivery
8© 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. SOA Landscape
9© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity

10. State of Cloud
10© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity
Source: Gartner

11. © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 11Addressing Systemic Complexity

12. Barriers to Successful SOA
12© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity
Initiatives solely led
and driven by techies
Insufficient semantics
in service composition
Disconnection between
traditional education
and real-world SOA
implementation needs
Absence of holistic
roadmaps with
specificity
Lack of well-defined
service models
(business and
technical)
Gap between logical
architecture and
infrastructure
Ad-hoc governance
(dictatorship or
anarchy)
Home-grown reference
models
Product lock-in with no
or limited
interoperability
Inability to quantify
ROI/TCO and
improper-sizing
Project-centric
execution without
reuse/sharing
disciplines
Immature
specifications and
standardization

13. Top 10 Cloud Adoption Inhibitors
Risk-Testing
•How is the cloud
computing vendor
managing risk?
Data Location
•Where is the data
being stored? In-
country or out of the
country? What
restrictions and laws
are placed upon the
data dependent on
location of stored
data?
Data and Code
Portability
•Once the data has
been put onto the
cloud computing
system, how difficult
will it be to get the
data back out?
Data Loss
•Does the cloud
computing system
back-up and restore
data?
Data Privacy
•Does the data
become more
vulnerable when it is
located on an
external cloud
computing system?
Source: Adapted and extended from Gartner and InformationWeek reports in 2009 and 2010.
Vendor Viability
•What will happen if
the cloud computing
vendor goes out of
business?
Performance
•How can SLA
guarantee
performance?
ROI
•Does operational
expense always
trump capital
expense, at least in
technology
investment?
Security
•What are the
vulnerabilities in the
Cloud architecture?
Control
•How can a cloud
provider be trusted
that they care about
your IT processing as
much as you do?
© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity 13

14. How are cloud solutions crafted?
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 14

15. What these lead to…
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 15
Page 1 of 2

16. How to Effectively Deal with
Complexity?
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 16

17. State of Art
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 17
Source: Wikipedia

18. Wisdom
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 18
The essential complexity is
irreducible.
Fred Brooks - Author of “The Mythical Man-Month”
- Coined “Computer Architecture”
- 1999 Turing Award

19. In Search for a Pragmatic Approach
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 19
Tomorrow’s computing systems
cannot be built using methods of
today. [Computing Research
Association (CRA) report]
We can't solve problems by
using the same kind of
thinking we used when we
created them. [Albert Einstein]
Conquering Complexity – one of five
“deliberately monumental" research
challenges, each requiring "at least a
decade of concentrated research in
order to make substantive progress”.
[“Grand IT Research Challenges” report
supported by NSF]

20. Key Areas
Notation
Technologies
Specification
Modules
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 20

21. 21
Increasing Disparate Representations
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential.

22. Semantic Notations
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 22
Source: The “Physics” of Notations

23. Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 23
Increasing Dynamics
SIP
MTOM REST SCA XOP
XPATH
DSL
AJAX
ITIL CMM
WOACOBIT POX
PaaSSaaS
IaaS

24. Service-Oriented Design Accelerator
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 24
Access & Interaction Layer
Integration/Communications Layer
Services & Components Layer
Composite Services Layer
Business Process Layer
Enterprise Resources Layer
Reference Model of Solutions Architecture for N-Tier Applications
Designed by Tony Shan
Jetspeed
Liferay
JO
SSO
Yale
CAS
Acegi
Modeling&DevelopmentTools
Eclipse,NetbeansAnt,Maven
CVS,Subversion,
Bugzilla,FxCop
JUnit,NUnit,Cruise
Control
ArgoUML,StarUML
CrosscuttingAspects&Patterns
MicrosoftEnterprise
Library
Microsoft
ApplicationBlocks
GoFdesignpatternsJavaEEpatterns
AspectJ,Spring,
JBossAOP
Application&ServiceFrameworks
JSF,Tapestry,
Wicket
RIFE,SeamKeelSpring
DWR,Echo2,
JSON-RPC,Dojo
WebWork,Struts,
Beehive
HostingEnvironment
JBossAppServerTomcatXenGridEngine,GlobusLAMP
Security
OpenSSHJacksumOpenSAMLEnhydraOysterOpenSSL
OperationalManagement
NagiosXMOJODMTFCIMJMX/SNMPWEBMServices
ActiveBPEL
jBPM
O
pen-Xchange
Shark
JaW
E
W
S-BPEL
jUDDI
ebXM
L
Registry
SCA
SDO
Axis
REST, Ajax
Drools
SweetRules
NxBRE
ServiceM
ix
M
ule
ActiveM
Q
O
penJM
S
O
pen
ESB
Derby
O
penCM
S
SugraCRM
M
ondrian
W
eka

25. 25
Application Framework Reference Card
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential.

26. Increasing Fragmented
Activities on Specifications
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 26
WS-Security
WS-Attachments
WS-Addressing
WS-Policy WS-PolicyAttachment
WS-AtomicTransaction
WS-BusinessActivity
WS-RX
WS-CDL WS-Trust
WS-Federation
WS-Coordination
WS-TX WS-Discovery WS-SX
WS-Resource
WS-Eventing
WS-Notification WS-Topics
WS-SecureConversation WS-ReliableMessaging WSRF
WSE
WS-Transfer
WS-Enumeration
WS-MEX

27. Stack of Standards
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 27
Foundation
Presentation
Management
Composition/Orchestration/Construction
Process
Messaging
XML Processing
· DOM
· SAX
· XPath
· XSLT
· XQuery
· .Net XML
Serialization
· JAXB
· SDO
· StAX
Description
· XML
· XML Schema
· WSDL
· XML Info Set
· XOP/MTOM
· SML
· DMCBX
· RELAX NG
· Schematron
Assertion Lang
Communications and Events
· Transport: SSL/
TLS
· Network: IPSec
· BEEP
· HTTP/IIOP/MQ
· WS-Eventing
· WS-Notification
· WS-Addressing
Security
· WS-Security
· WS-
SecureConversation
· WS-Federation
· SAML
· Liberty Alliance IDFF
· WS-Trust
· XKMS
· XACML
· XrML
· EPAL
Interoperability
· WS-I Basic Profile
· WS-I Basic Security
Profile
· WS-I Reliable Secure
Profile
· Governance
Interoperability
Framework (GIF)
· Reusable Asset
Specification (RAS)
· DMTF CIM
Resources
· WSRF
· WSRF-
ResourceProperties
· WSRF-
ResourceLifetime
· WSRF-ServiceGroup
· WSRF-BasicFaults
· WS-Transfer
· RRSHB
· WS-Enumeration
Transaction
· WS-Coordination
· WS-Business Activity
· WS-Atomic Transaction
· WS-Context
· WS-CF
· WS-TXM
· WS-TX
Semantics
· RDF
· WSDL-S
· SA-WSDL, SA-REST
· OWL-S, RDF/S
· SWSO, WSMO
· SWSL, WSML
· SOA-S, FEARMO,
ODM
QoS
· WS-
ReliableMessenging
· WS-Reliability
· WS-RX
Discovery
· 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
Increasing Modules
Enterprise Portal: Role based portal that
is available 24x7. Provides single point of
entry for all users, multi-channel support,
consistent look and feel, access to business
capabilities based on role.
Custom Applications: These are either built on an
App 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-On
Packaged Applications: These are the best of the breed
packaged application that also act as the system of record for
a particular business function.
Enterprise Services: Basic services required across the
enterprise. Examples: Directory Service, Content Management,
Search, eMail, Calendar, IM, Discussion Forum, White Board, etc. Business Process
Manager: Configure
and automate business
process. Provide
business users the
capability to modify the
business process &
policies.
Enterprise Service Bus: Route services to the appropriate
destination; receive and transmit messages in any protocol, provide
message transformation, routing, validation, auditing, security,
monitoring and reporting services.
Service Registry:
Service registry
containing service
properties such as
service capabilities,
parameters, service
levels, etc.
Shared Data
Services: Extract,
Transform & Load (ETL),
Electronic Data
Interchange (EDI),
Enterprise Information
Integration Data Quality
(Matching Engine, Master
Data Management)
Service Manager:
Manage service
lifecycle across the
enterprise.
Enterprise Application
Integration: Traditional
enterprise integration approach.
Provide Application Adapters,
Business Process, Messaging,
Security, etc. capabilities. Mostly
proprietary in nature and
application integration generally
implemented as a point-to-point
integration on a Hub..
Mainframe Application :
Access data via gateways
Enterprise Security: Provide
user authentication,
authorization, identify
management, profile
management, delegated admin,
etc.
Business Service
Management: Monitoring,
capacity planning, utility
computing
Mapping SOA Reference Architecture
to the Enterprise SOA Maturity Model
Traditional
Development
Develop Web
Applications
Composite
Applications
Automate
BP
© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Legacy Application: Applications that do not have open APIs & are not web based
Source: SOA Practitioners’ Guide

29. Cloudonomic Paradigm
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 29
Service Integration & Management Platform and Lifecycle Engineering
Cloud Computing Foundation
Principles Methodology Process Techniques Tools Patterns Policy Standards Practices Maturity
Dev
Support
•Collaborati
on
•Asset
Mgmt
•Build Mgmt
•Test Mgmt
•Release
Mgmt
Biz
Support
•Customer
Mgmt
•Partner
Mgmt
•Revenue
Mgmt
•Billing
Mgmt
Operation
Support
•Incident
Mgmt
•Change
Mgmt
•Config
Mgmt
•SLA Mgmt
Provider
Support
•Product
Mgmt
•Inventory
Mgmt
•Capacity
Mgmt
•Resource
Manager
Interaction
Enablement
Virtual Hosting
Runtime
Cloud Service Factory
Plan Define Model Implement Deploy
Channel Device User exp Participate
Onboard Catalog Provision Reports
UI Process Service Data
Security Repository Metering Monitor
Federated Composite Cloud Fabric
Aggregate
Mashup
Bundle

30. Best Practices
Addressing Systemic Complexity © 2011 Tony Shan. All rights reserved. Proprietary and Confidential. 30
Hybrid
Attitude Program

31. Case Study of Healthcare Vertical
Addressing Systemic Complexity 31© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.
Business Challenge
• Healthcare cost containment
services to U.S. payers and
insurance providers
• An average annual increase of
over 40% for the last four years
• Requires continuous
management of and investment
in processing capacity and
utilities, including power and
cooling
• Using traditional servers and
suffering from occasional sub-
par system performance
Solution
• The cloud solution provides a
comprehensive set of building
blocks giving the company the
flexibility to build systems in a
way that was most applicable to
their business
• The public cloud has all the
pieces needed at a price point
well below the competition
• Utilizing the computing, storage,
and queuing capability in the
public cloud to enable the claim
processing system capacity to
increase and decrease as
required to satisfy the service
level agreements (SLAs)
• Meet the needs of requiring
massive amounts of computing
resources that far exceed the
existing system, without
purchasing, housing and
maintaining the servers
themselves
Result
• Providing retrospective claim
processing services which is
essentially processing multiple
years’ worth of data at a time
• Encrypt and send the data that
need processed to the cloud
while the majority of the PHI is
retained in-house and is
reconnected with the processed
data upon its return
• The firm was able to produce a
HIPAA-compliant application that
scales as they do
• The public cloud is a great fit for
the company because it allows
them to economically expand
and contract their computing
resources to match the ebb and
flow of the claim volume without
making any long-term financial
commitments or capital
expenditures

32. Make it Simple…
Addressing Systemic Complexity 32© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.

33. Thank You
Merci
Grazie
Gracias
Obrigado
Danke Japanese
French
Russian
GermanItalian
Spanish
Brazilian Portuguese
Arabic
Traditional Chinese
Simplified Chinese
Hindi
Romanian
Thai
Korean
Multumesc
Contact: Tony Shan
Email: mail@tonyshan.com
Web: http://tonyshan.com
© 2006-2011 Tony Shan. All rights reserved.
Duplication, reproduction or disclosure of
the contents in this document is prohibited
without prior written permission of the
author.
33© 2011 Tony Shan. All rights reserved. Proprietary and Confidential.Addressing Systemic Complexity