Beruflich Dokumente
Kultur Dokumente
"Requirements
for Extending
Enterprise SOA to Public Clouds
Agenda
• Understanding Clouds
• Questions/Comments
• Definition (NIST):
– On demand Self Service
– Resource Pooling
– Rapid Elasticity
– Measured Service
– Broad Network Access
• Install/Activate Components
– Build full reference system with test data in the cloud
– Database, ESB, Application Server, CMS, Identity store
• Costs
– IaaS provider costs are minimal but vary: $0.08/hr to $2.40/hr
– Installation/bundling/imaging costs
– Establishing Enterprise-to-Cloud communication (Cloud Gateway, ESB,
Application Server, Load balancer, Firewall)
– Hand coding “what-if” scenarios for:
Timeouts
message delivery errors
security profiles
– Evaluate Multiple IaaS providers
Different Token Types
Different Management APIs
Different Sever Classes and cost structure
Cost-Risk Trade-offs
• Enterprise-to-Cloud migration simulation may reveal key trade-offs between
cost and risk factors
• Costs
– Server Class:
– server class required within a cloud provider to maintain the required
application performance thresholds may be cost prohibitive.
– Top-end : entry-level = 30:1
Cost-Risk Trade-offs
• Risks
– Change in Topology by adding “Cloud Node.”
LDAP
• Interoperability Categories
– Message
– Structural: JSON SOAP
– Semantic: PONum PurchaseOrderNumber
– Protocol
– Across SOA Domains: HTTP (AS/2)
– Closer to Mainframes: JMS, MQSeries, FTP
• Security
– Protocol Level: SSL
– Content Level: XML Security Encryption and Signatures
• Reliability
– HTTP inherently unreliable – JMS not used for cross Domain communication
– Use Re-tries, WS-RM not available for IaaS
• Business Drivers/Owners
– Business Service Owner
– Technology Owner
• Requirements:
– Establishing Trust: Federated Identity Management
– Interoperability: Varying Message Types
– Flexibility: Virtualization & Leveraging Legacy Systems
– Message Hygiene: Check/Validate In-bound and Out-bound Messages
– Governance: Enforce, Measure and Audit SOA policies
• Lessons
– Federated SOA is NOT a product or technology, it is an architecture and philosophy
– Architecture: May not get everything right on 1st implementation, but be sure the get
the architecture right.
– Federated SOA is hard, but with the right approach, it can unlock tremendous value
• Deployed a Federated SOA strategy for call centers, branch platforms, deposit platforms, loan platforms,
Internet and Mobile Banking
“It's hard as
a customer • Cut $1M/year in 3rd Party processing in just the first year.
service rep
to look • Unified Customer activity view
credible in
front of the • Integrated Systems and Portals with over 35 trading partners
client when
you don't • Over 2 Billion Transactions Per Year; 150,000 Concurrent Users
have the
transaction • 20 Appliances across 2 Data Centers
related facts
easily at • Winner of Grand Prize – CIO Magazine
your
disposal.” –
John
Woolbright,
CTO
Point-and-Click Test Generator, Custom WSDL Parser, Custom SOAP Generator, Governance Scanning Engine
Questions/Comments?
Mamoon Yunus: myunus@crosschecknet.com