DataPower SOA Appliance Administration, Deployment, and Best
Applied SOA: Best Practices of the Best PractitionersB2B "Lite" Multichannel Composite Applications...
24
IT Service Convergence 2005 Notes accompany this presentation. Please select Notes Page view. These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e-mail — [email protected]. Applied SOA: Best Practices of the Best Practitioners Steve Bittinger
Transcript of Applied SOA: Best Practices of the Best PractitionersB2B "Lite" Multichannel Composite Applications...
IT Service Convergence 2005
Notes accompany this presentation. Please select Notes Page view.These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e-mail — [email protected].
Applied SOA:Best Practices of the Best Practitioners
Steve Bittinger
Drivers:B2B "Lite"
Multichannel Composite Applications"Doing more with less"
1995 2002 2008
SOA Adoption
Time
Enablers:Peer-to-Peer NetworksRPC, Distributed TPMs
Stored Procedures
Drivers:Mergers & Acquisitions
E-business
Irresistible Forces Push Service-Oriented Architecture Into Mainstream Adoption
Enablers:MOM
CORBA, DCOM, Screen-Scrapers
Enablers:Integration Middleware
Web Services J2EE, .NET
BPM
Enablers:ESB
Complex Event Processing SOA-Based Packaged Applications
Drivers:Business FlexibilityInterenterprise BPM
"Everybody is doing it"
Client Issues
1. What are the key drivers to SOA adoptionand when should SOA be avoided?
2. What are the technology challenges userswill face when implementing large-scaleSOA projects?
3. Which are the critical success factorsfor successful SOA initiatives?
Client Issues
1. What are the key drivers to SOA adoptionand when should SOA be avoided?
2. What are the technology challenges userswill face when implementing large-scaleSOA projects?
3. Which are the critical success factorsfor successful SOA initiatives?
Business Initiatives Drive Strategic Adoption of SOA
IT Architectural RequirementsFiner granularity of application back-endsRapid composite applications developmentReal-time "request/reply" interoperability
Service-Oriented Architecture
Business Unit-WideCall center integrationSingle face to clients/suppliers"Light" B2B integrationIntegration of cross-functional processes
EnterprisewideEnable mergers/divestitureMultichannel sales/support strategiesGreater business processes flexibilityFaster time to market for new products
Pressures on IT Favor CIOs' Endorsement of Service-Oriented Architecture
Perennial IT Challenges"Doing more with less"Business/IT AlignmentImprove data consistency/qualityTime-to-deployment of new applications
Application Integration IssuesImprove reuse of integration artifactsEnable composite applications Support business process integration
Application Development IssuesImprove reuse of application componentsAssembly vs. DevelopmentOptimization of skills allocation
Service-Oriented Architecture
Beyond the Hype: The Fundamental Benefits of SOA Are Few, but Compelling
2 – Incremental Deployment & MaintenanceGradual migration to SOA Cost "spreading" across multiple projectsReduced maintenance cost
3 – Reuse of Services:Faster time to deploymentLower development cost Greater adaptability of applications
1 – Architectural PartitioningDiverse life cycle "speeds"Synergy of different technologiesOptimal tech skills allocationImproved documentationGreater maintainabilityEasier outsourcing/offshoring
…But Service-Oriented Architecture Doesn't Come for Free
SOA Organizational InvestmentsServices definition/validation processEnforce and incentive service reuseTraining-Skills redeploymentCost allocation
SOA Infrastructure InvestmentsIntegration MiddlewareWeb servicesServices RegistrySystem Management/Security
SOA Architectural InvestmentsServices definition methodologyDesign the SOA BackplaneTechnology selectionOthers
Client Issues
1. What are the key drivers to SOA adoptionand when should SOA be avoided?
2. What are the technology challenges userswill face when implementing large-scaleSOA projects?
3. Which are the critical success factorsfor successful SOA initiatives?
SOAP and WSDL Are Not Enough: Orient Yourself Through the Middleware Bazaar
Non-SOA Wrapped Application
Multichannel Portal
Composite Application
WrapperWrapper
Services Application Logic
Native SOA Application
Interface Interface Interface
SOA Backplane(Web Services or Other Protocols)
BPM Application
Wrapper
BPM Suite, IBS
Portal Product, EAS, Presentation Integration Server
Portal Product, SES
Adapters, Programmatic Integration Servers
TPM, EAS, CAS
APS
ESB, MOM, ORB, TPM, IBS
The SOA Backplane Unveiled:Web Services and More
Security ManagementAdapters
DevelopmentTools
= Common Features
Life Cycle ManagementTools
Orchestration Registry
ExtensibilityFramework
= Advanced Features
Communication(SOAP, IIOP, JMS, MOM, RPC, ORB, TPM)
Mediation/Transformation
Routing/Addressing Naming QOS
= Minimal Features
ESBsBlue Titan's Network DirectorCapeClear's Integration ServerFiorano's Bus. Integration SuiteIona's ArtixPolarLake's Integration SuiteSystinet's WASPSoftware AG'sEnterprise ServiceIntegratorSonic Software's Sonic ESBwebMethods' ServiceNetOthers
Progr. Integration ServersCommerceQuest’s BPI/CPIJacada's Jacada IntegratorMicrosoft's HISNeon Systems' ShadowDirect & zServicesNetManage's OnWebObjectStar's ObjectStar SuiteSeagull's LegasuiteWRQ's VerastreamOthers
Plain MOMFiorano's FioranoMQ IBM's WebSphere MQSonic's SonicMQTIBCO's EMSOthers
Integration SuitesAxway's XIPBEA Systems' WebLogic IntegrationIBM's WebSphere Business IntegrationMicrosoft's BizTalk ServerSeeBeyond's ICANTibco's BusinessWorkswebMethods‘Integration ServerOthers
Picking the Right Platform for the SOA Backplane: 'Know Thy Needs'
IndustryFollowing
Architectural Fit
QOSLegacy Support
Completeness of Integration Capabilities
(BPM, BAM, Transformation, Adapters)
Low Cost
Implementing Services Out of Existing Applications: Wrapping, Re-engineering or Redeveloping?
Data Model
Wrapper
InterfaceInterfaceWrapper
InterfaceInterface
Mixed Business Logic
andPresentation Logic
Mixed Mixed Business LogicBusiness Logic
andandPresentation LogicPresentation Logic
Wrapping
Pros:NoninvasivenessLow cost/Fast
Cons:Suboptimal granularityHard to maintain
Use of screen-scraping to package "pseudo-services"
PresentationPresentationLogicLogic
Data Model
Orchestration
InterfaceInterface
Orchestration
InterfaceInterface
Business LogicBusiness LogicBusiness Logic
Re-engineering
Pros:Easier to maintainBetter performance/scalability
Cons:Invasive/high costGranularity might be suboptimal
Business logic is modularized and separated from presentation
Data Model
OrchestrationInterfaceInterface
Orchestration
InterfaceInterface
Business LogicBusiness LogicBusiness Logic
Redeveloping
Pros:Optimal granularity/reuseEnables technology change
Cons:Risk is higher High cost
Business logic of servicesis redesigned from scratch
To Fully Support Business Requirements, Credit Suisse Complements SOA With Events
ConsumerComposite Applications
ProducerEnvironment
ServiceCalls C
SIB
MainframeApplications
Databases
Packaged Applications(PeopleSoft, other)
Data Warehouses
New Non-mainframe
Applications
External Data Feeds
(Swift, SIC, . . . )
Events
Services(IMS PL/1/Orbix)
IONA's Orbix(CORBA)
BEA's WebLogic(J2EE)
JavaVB, C++, MS Office
WebSphere MQWBI Message
BrokerEvent Bus
Infrastructure
Source: Gartner Research and Credit Suisse Technology and Operations
Client Issues
1. What are the key drivers to SOA adoptionand when should SOA be avoided?
2. What are the technology challenges userswill face when implementing large-scaleSOA projects?
3. Which are the critical success factorsfor successful SOA initiatives?
How Big Is Big in Service-Oriented Architecture?
ORB, TPM,ESB, MOM,
IBSORB, TPM,ESB, MOM
Progr. IS,ESB
Progr. IS,WS ESBSOA Backplane
EnterpriseBusiness UnitInter-AppSingle AppScope
>100<100<20<10# of Service Developers
>1,000,000<1,000,000<100,000<10,000# of Service Calls/Day
>100<50<25<5# of Service Consumers
>1,000<500<100<25# of Published Services
Extra LargeLargeMediumSmall
Experimental Mainstream Leading Edge
How Do You Know Which Services You Actually Need (and How Large They Are)?
Inter-Domain Services
Top-Down Approach (Process Centric)1. Define Application Domains2. Model Business Processes3. Services = Process Activities
Intra-Application Services
Bottom-Up Approach (Data Centric)1. Define data model2. Design CRUD components 3. Services = Assembly of CRUD
components
Inter-Application Services
Pragmatic Approach (Application Centric)1. Design consumer application2. "Extract" services out of established
applications3. Make sure service are "generic enough"
"Incremental" SOA
"Big-Bang" SOA
How Do You Get There:'Big Bang' or 'Incremental'?
Application Domain 1
Application Domain 2
Application Domain 3
Application Domain 1
Application Domain 2
Application Domain 3
How Do You Enforce Reuse of Services?
Services
"Good" SOA
Service Definition Process
Services Description Services MetadataCross-ReferencingVersioning/Change ManagementDiscovery/SearchSLA/QOS
Service Registry
ServicesServicesServices
"Bad" SOA
Reuse-Oriented Chargeback
Schema
Technical IssuesEnd-to-End Monitoring, Management & SecurityDynamic Service DiscoveryQuality of Service ManagementMetadata Management
A Few More 'Cans of Worms' You Will Have to Open (Sooner or Later)…
Governance IssuesOwnership:
Who owns the service interface?Who owns the service implementation?
Costs Allocation:Who pays for the SOA Backplane?Who pays for Services Implementation, Maintenance & Use?
Prioritization:Which services must be implemented first?Who takes the decision?
Getting Ready for Service-Oriented Architecture: Roles and ResponsibilitiesArchitecture Team
Update Architecture Blueprints to enable SOADefine SOA Patterns, Standards & GuidelinesSet up and manage the services definition processSelect proper technologies and tools
Development TeamImplement ServicesDevelop consumer applicationsChange Management
Integration TeamImplement the SOA BackplaneSupport Service DevelopersManagement of Service Registry
QA TeamEnd-to-End testing and validation
Operations TeamsServices and Consumers DeploymentEnd-to-End Monitoring and Administration
Recommendations
Endorse service-oriented architecture to be able to respond to both business and IT challenges.Justify upfront investments on SOA on the basis of three main anticipated benefits: architectural partitioning, incremental deployment and reuse.SOA is not only about Web services. Build knowledge about middleware and application integration technologies as well.SOA is a journey: Plan for multiyear, incremental implementation steps, but look for short-/medium-term payback. Avoid "wild" proliferation of services. Establish governance processes focused on maximizing reuse. While planning for SOA, build an understanding about events. They are the two sides of the same coin: the Business Component Architecture.
IT Service Convergence 2005
Notes accompany this presentation. Please select Notes Page view.These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e-mail — [email protected].
Applied SOA:Best Practices of the Best Practitioners
Steve Bittinger
IT Service Convergence 2005
Notes accompany this presentation. Please select Notes Page view.These materials can be reproduced only with Gartner's official approval. Such approvals may be requested via e-mail — [email protected].
Applied SOA:Best Practices of the Best Practitioners
Steve Bittinger
![Service Oriented Architecture (SOA) [5/5] : SOA Best Practices](https://static.fdocuments.us/doc/165x107/547a35e7b379593a2b8b494c/service-oriented-architecture-soa-55-soa-best-practices.jpg)
