View
217
Download
0
Category
Tags:
Preview:
Citation preview
SOA in the Real World“How to get SOA right the first time.
David S. Linthicum
www.davidlinthicum.comdavid@davidlinthicum.com
Time to Make Something Work
• We’ve been working with the notion of SOA for over 5 years now.
• We’ve proven that SOA can work, if you approach it correctly.
• We need to start doing, but never stop learning.
• They hype is officially over.
• Time to make something work!
2© David S. Linthicum LLC
What worked?
• “We changed our leadership to change the culture to make way for new approaches, such as SOA.”
• “We took the time to understand the business first, then the technology.”
• “We focused on the architecture.”• “We made some quick wins which provided creditability,
and built more complex and far reaching projects around that very positive foundation.”
• “We created a common team across the organizations which broke down any political barriers.”
• “We spent a hell of a lot of money.”
3© David S. Linthicum LLC
What went wrong?
“We could not get the culture to shift to accommodate the disruptive changes we needed for SOA.”
- Name withheld upon request
“We put our trust into a single large vendor and our technology solution was not the right fit.”
- “Do not use my name”
“We service-enabled everything…now what?”
- “I’m a complete idiot.”
4© David S. Linthicum LLC
So, how do I win with SOA the first time?
1. Make sure there are advocates with budgets, at the executive level.
2. Begin with architecture, not with technology.
3. Get the talent and knowledge you need now.
4. Understand that SOA is ongoing (journey not a project).
5. Focus on understanding the business.
6. Define the ROI up front, and make sure it’s there upon delivery.
7. Follow a repeatable process (later in this presentation).
8. Build your SOA with the emerging Web in mind (WOA).
9. Define incremental successes, and make sure to get there.
10. Follow everything in this presentation.
5© David S. Linthicum LLC
Architecture is not About the Technology
•It’s about what you’re building, then how you build it.•It’s about understanding first, then building.
6© David S. Linthicum LLC
SOA Challenges
Source: Wipro
7© David S. Linthicum LLC
Data Abstraction
Data Data
Data Services
LegacyLegacy LegacyLegacy
Services
Process/Orchestration/Composites
Monitoring/Event Management
Govern
ance
Rep
Secu
rity
Internet-
Based
Services
New Services
SOA Meta Model
8
5 Things to Avoid
1. Using the wrong people.
2. Selecting the technology too early.
3. Not considering “service design.”
4. Not factoring in the business.
5. Not thinking long term, and strategic.
9© David S. Linthicum LLC
Using the Wrong People
• Perhaps this is something you should not outsource.
– This is architecture, not development.
– This is strategic, not tactical.
• Existing talent may not be up to speed.
– You may love your current team, but perhaps they are not up for the job.
– Make the cuts now, not later.
• Don’t let consultants or vendors drive the project.
10© David S. Linthicum LLC
Selecting the Technology too Early
• Don’t “manage by magazine.”• Don’t overuse “comfort
vendors.”• Avoid VDA (vendor driven
architecture)• Business -> Requirements ->
Analysis -> Technology. Now repeat!
• Make sure to do a POC, and other testing.
• Never be afraid to toss out technology.
11© David S. Linthicum LLC
Not Considering “Service Design”
• Services are not applications.
• Services are not APIs.• Services are services,
and should be designed properly.
– Consider granularity.– Consider repeatable
design.– Consider testing.
12© David S. Linthicum LLC
Not Factoring in the Business
• Always do ROI analysis before you begin work on your SOA.
• Understand core business processes, and what needs to improve.
• Understand core business drivers, and be able to sell them within the organization.
• Make sure business analysts have input at various stages.
13© David S. Linthicum LLC
Not Thinking Long Term, and Strategic
• SOA has a positive impact after years, not months.
• SOA is not a development project, it’s a journey.
• SOA requires a systemic change in how you do architecture, it’s not just an instance of an architecture.
• SOA requires long term corporate commitment to be successful.
14© David S. Linthicum LLC
Understand your business objectives and define success.
ROIROIDefine ROI
Create Business Case
BusinessCase
BusinessCase
15© David S. Linthicum LLC
Define your problem domain
SystemDescriptions
SystemDescriptions
System Complexity Analysis
SOA POC
POCResults
POCResults
DomainDescriptions
DomainDescriptions
Vendors
16© David S. Linthicum LLC
Understand all applicationsemantics in your domain.
SOAMetadata
SOAMetadata
Meta data analysis
Data abstraction layer definition
DataAbstraction
Layer
DataAbstraction
Layer
Data services definition
DataServices
DataServices
LegacyMetadata
LegacyMetadata
ExternalMetadata
(B2B)
ExternalMetadata
(B2B)
17© David S. Linthicum LLC
Understand all services in your domain.
CandidateServices
CandidateServices
Service analysis
Metadata andservices analysis
ServicesAnd
Information
ServicesAnd
Information
Performance analysis
ServicesAnd
Performance
ServicesAnd
Performance
LegacyServices
LegacyServices
ExternalServices
(B2B)
ExternalServices
(B2B)
SOAMetadata
SOAMetadata
18© David S. Linthicum LLC
Understand all processes in your domain.
CandidateProcesses
CandidateProcesses
Process analysis.
Define metadata, services,and processes
Processes,Services,
AndInformation
Processes,Services,
AndInformation
Process integrationanalysis.
ProcessIntegrationDiagrams
ProcessIntegrationDiagrams
CandidateServices
CandidateServices
ExternalProcesses
(B2B)
ExternalProcesses
(B2B)
SOAMetadata
SOAMetadata
19© David S. Linthicum LLC
Define new services.
CandidateProcesses
CandidateProcesses
Service definition.
Service design.
Processes,Services,
AndInformation
Processes,Services,
AndInformation
Service implementation.Process
IntegrationDiagrams
ProcessIntegrationDiagrams
SOAMetadata
SOAMetadata
CandidateServices
CandidateServices
ServiceDefinition
ServiceDefinition
ServiceDesign
ServiceDesign
ServiceImplementation
ServiceImplementation
20© David S. Linthicum LLC
Define new processes.
CandidateProcesses
CandidateProcesses
Process definition.
Process design.
Processes,Services,
AndInformation
Processes,Services,
AndInformation
Process implementation.• Pro
cess
• Integration
• Diagrams
• Process
• Integration
• Diagrams
MetadataMetadata
CandidateServices
CandidateServices
ProcessDefinition
ProcessDefinition
ProcessDesign
ProcessDesign
ProcessImplementation
ProcessImplementation
21© David S. Linthicum LLC
Select your technology set.
TechnologyRequirements
TechnologyRequirements
Define requirements.
Technology analysis.
Technologysolution
Technologysolution
Vendors
Define candidate technology.
Technology selection.
Technology validation.
22© David S. Linthicum LLC
“SOA is Good…”
• Pay me now, or pay me later. Make sure you do it right the first time…get the help you need.
• Don’t be afraid to experiment, and admit you’re wrong…backup and try again.
• Keep your vendors working with you.• Empower those working, so they can work to get things
done. Avoid politics, if possible.• Learn all you can, but don’t get caught up in the hype. • Put standards in their proper place. • Small battles win the war…Keep that in mind.• Give yourself plenty of time, never skimp on any of the
steps.
23© David S. Linthicum LLC
Thanks!
• Blogs:– InfoWorld “Real World SOA”
• Weekly Podcast– InfoWorld SOA Report
• Columns– SOA Journal– SD Times– Web 2.0 Journal– eBizq.net
• Follow me on Twitter (DavidLinthicum)
24© David S. Linthicum LLC
Recommended