www.idc.com soa – you ain’t seen nothin’ yet: projections for a likely future rob hailstone...
TRANSCRIPT
www.idc.com
SOA – you ain’t seen nothin’ yet:projections for a likely future
Rob HailstoneDirector, European Software Infrastructure Research
2Copyright IDC 2005
TopicsTopics
Techniques & pratfalls of prediction
Hazards to the long-term success of SOA
Convergence with parallel trends
The central role of the repository
Can we really avoid replacing the legacy?
3Copyright IDC 2005
Predictions – learning from the mastersPredictions – learning from the masters
On eBusiness “Nevertheless electric telegraphy must have greatly
diminished the number of letters, for new improvements now permitted the sender to correspond directly with the addressee; secrecy of correspondence was thus preserved, and the most intricate deals could be transacted over long distances. - - - - permitted transmission of the facsimile of any form of writing or illustration; whether manuscript or print, and letters of credit or contracts could now be signed at a distance of 5,000 leagues.”
Jules Verne - ‘Paris in the Twentieth Century’ - 1863
Identify the innovation, project the trend, determine likely impact on business world
4Copyright IDC 2005
Predictions – learning from the mastersPredictions – learning from the masters
On ‘Calculating Machines’ “Instruments which did indeed resemble huge pianos: by
operating a sort of keyboard, sums were instantaneously produced, remainders, products, quotients, rules of proportion, calculations of amortisation and of interest compounded for infinite periods and at all possible rates. There were high notes that afforded up to 150%!”
Trend-spotting will miss disruptive innovations (in this case the CRT & the semiconductor)
Jules Verne - ‘Paris in the Twentieth Century’ - 1863
5Copyright IDC 2005
Predictions – learning from the mastersPredictions – learning from the masters
On Technophobes:
“Yet he felt an authentic joy at abandoning his calculating machine: he was proud of having operated it so poorly.”
Human factors – the best ideas can be misused or abused
Jules Verne - ‘Paris in the Twentieth Century’ - 1863
6Copyright IDC 2005
Predictions – learning from the mastersPredictions – learning from the masters
On Women “The Frenchwoman has become Americanised; she
speaks seriously about serious matters, she takes life seriously, she rides on the rigid saddle of modern manners, dresses poorly, tastelessly, & wears corsets of galvanised tin which can resist the most powerful pressures.”
Trends never go to a ludicrous extreme – every trend has a point of inflexion
Jules Verne - ‘Paris in the Twentieth Century’ - 1863
7Copyright IDC 2005
LessonsLessons
Identify the trends & business impact
Spot possible interactions with parallel trends
Look for disruptive innovations
Factor in the human angle
Decide what constitutes a ridiculous extreme
It doesn’t take 150 years now before it’s obvious you got it wrong!
8Copyright IDC 2005
TopicsTopics
Techniques & pratfalls of prediction
Hazards to the long-term success of SOA
Convergence with parallel trends
The central role of the repository
Can we really avoid replacing the legacy?
9Copyright IDC 2005
Assuming SOA delivers as promisedAssuming SOA delivers as promised
As long as business requirements continue to focus on responsiveness & adaptability, SOA will not be displaced by any architecture that focuses
purely on performance & scalability.
SOA is more likely to provide the foundation for whatever comes next: Policy-based computing?
10Copyright IDC 2005
Hazards to the SOA trendHazards to the SOA trend
Disruptive technologies Massive-scale, solid-state persistent memory RFID, “smart dust”, intelligent domestic devices All seem to add value to SOA rather than devalue it
Human Issues Running before walking – the need to gain experience Getting stuck on old best-practices – e.g. waterfall
methodologiesWhat is too extreme – where is the point of inflexion?
Is a reversal to monolithic applications likely? Potential performance issues with large-scale SOA Losing control of a large service portfolio
11Copyright IDC 2005
What do we have to ensure we get right?What do we have to ensure we get right?
Design/development methodologies
Tools to match the methodologies
End-to-end performance monitoring
Identity management & authorisations
Service granularity
12Copyright IDC 2005
TopicsTopics
Techniques & pratfalls of prediction
Hazards to the long-term success of SOA
Convergence with parallel trends
The central role of the repository
Can we really avoid replacing the legacy?
13Copyright IDC 2005
The search for the single viewThe search for the single view
All the information is there somewhere!
Needs a common way to connect the pieces
Independent of programming language
Independent of application platform
Independent of location
Independent of ownership
Tolerant of any legacy
Supportive of new innovations
Sounds pretty similar to SOA
14Copyright IDC 2005
Information Consumers
Content Provider Layer
Technologies for single viewTechnologies for single view
Virtual Information System
Metadata Repository
Virtual Database Optimization & Synchronization
Server OS
ObjectDBMS
Comp. AidedEngineeringApplication
Server OS
XMLDBMS
DocumentManagement
Server OS
ContentManagement
CollaborationApplication
Server OS
RDBMS
CustomIndustry
Application
Server OS
OLAPDBMS
AnalyticApplication
Server OS
RDBMS
ERPSuite
CollaborationView
OLAPView
Web ServicesView
RelationalView
ObjectView
TextView
Data Connector/Adapter Middleware
ApplicationsWeb
ServicesProcesses
BITools
PortalsSearchEngines
Plus ontology, semantic definitions, etc
15Copyright IDC 2005
SOA & Federated Database – common featuresSOA & Federated Database – common features
Monolithic approach unworkable
Multiple technologies exposed through standards
Reliant on metadata repository
Is a DBMS just a particular type of service?Would a single repository make sense?
16Copyright IDC 2005
TopicsTopics
Techniques & pratfalls of prediction
Hazards to the long-term success of SOA
Convergence with parallel trends
The central role of the repository
Can we really avoid replacing the legacy?
17Copyright IDC 2005
SOA and the role of repositorySOA and the role of repository
SOA is about exploiting heterogeneous environments Heterogeneous operating systems, databases, application
platforms, message brokers, integration technologies, service owners
SOA is also about enabling change Change assembly of services into composite applications,
change of choreography of business processes, piecemeal change of the underlying services themselves
This requires a degree of control that depends on a comprehensive repository of metadataMultiple, uncoordinated repositories will lead to chaos and ultimate failureThis will make the repository the central focus of SOA
But is a single repository a reasonable target?
18Copyright IDC 2005
Technologies for SOATechnologies for SOA
User PortalExternal Events ManagementInitiators &Endpoints
Business Rules Engine
Process Orchestration EngineProcess
Coordination
Se
curi
ty &
Ide
nti
ty M
gt.
Sy
ste
m &
Se
rvic
e M
gt.
SupportingInfrastruct.
Business to Service
Mapping
Mo
de
l/Co
ns
tru
ct
Bu
sin
es
s A
cti
vit
y M
on
.
Services Metadata Registry
Application Adapters
Message Broker (MOM)
Message TransformationMessagingFramework
Data Adapters
Database ServerApplication ServerApplicationInfrastructure
19Copyright IDC 2005
Classes of metadata that need to be managedClasses of metadata that need to be managed
Service metadata: UDDI & other descriptive information
Where-used and frequency of use metrics
Service performance metrics: actual experienced
Service to device mapping
User metadata: security & identity management, security policies
Process metadata: BPEL
Rules metadata: business rules
Federated content metadata
20Copyright IDC 2005
Good news / bad newsGood news / bad news
The good news: Most vendors permit 3rd-party repositories to be used
instead of the native repository delivered with the product But sometimes with a loss of functionality
The bad news: Standards for exchanging and federating information
across multiple repositories has mixed maturity. Good examples are
– Liberty Alliance for federated identity information– UDDI for service “find and use” metadata
21Copyright IDC 2005
Metadata repository optionsMetadata repository options
Use a commercial free-standing repository as strategic component of SOA
Build a custom repository using commercial tools
Use multiple native repositories delivered with toolsets & federate these into a single logical repository
Experience suggests most organisations will have a preferred, centrally managed repository, but federation will always be required (even if just to include external services)
22Copyright IDC 2005
TopicsTopics
Techniques & pratfalls of prediction
Hazards to the long-term success of SOA
Convergence with parallel trends
The central role of the repository
Can we really avoid replacing the legacy?
23Copyright IDC 2005
Service granularity – critical trade-offsService granularity – critical trade-offs
Fine-grained servicesGreatest adaptability
Limit impact of change
Coarse-grained servicesBest performance
Simplified management
Trend over time towards fine-grained servicesProlonged legacy replacement
24Copyright IDC 2005
Trend towards granular applicationsTrend towards granular applications
SAP xApps Stated vision to be 100% SOA by 2007
Microsoft Axapta Architecture built on components
Oracle Project Fusion Integration of Peoplesoft in SOA-style by 2008
Tier-2 vendors adopting same strategy but on 3rd party platforms
All vendors building comprehensive directory of application services
25Copyright IDC 2005
Physical architecture limitations on adaptabilityPhysical architecture limitations on adaptability
Use of a common, shared database
Data integrity rules implemented by database
Service components ‘joined at the hip’ through the database
Adds unwanted complexity to piecemeal service replacement
26Copyright IDC 2005
Possible platform for long-term SOA benefitsPossible platform for long-term SOA benefits
CompositeServices
Low-level Services/Data Persistence
BusinessProcesses
Me
tad
ata
Re
po
sit
ory
Ru
les
En
gin
e
27Copyright IDC 2005
Implications of the architectureImplications of the architecture
Potential for use of embedded technologies: Embedded application platform Embedded database
Data content addressable through the service
28Copyright IDC 2005
TopicsTopics
Techniques & pratfalls of prediction
Hazards to the long-term success of SOA
Convergence with parallel trends
The central role of the repository
Can we really avoid replacing the legacy?
www.idc.com
SOA – you ain’t seen nothin’ yet:projections for a likely future
Rob HailstoneDirector, European Software Infrastructure Research