www.idc.com Service Oriented Architecture Inevitable? What next? Rob Hailstone Director, European Software Infrastructure Research [email protected]
Www.idc.com Service Oriented Architecture Inevitable? What next? Rob Hailstone Director, European Software Infrastructure Research [email protected].
Dec 14, 2015
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
www.idc.com
Service Oriented ArchitectureInevitable? What next?
Rob HailstoneDirector, European Software Infrastructure Research
TopicsTopics
Is Service Oriented Architecture Inevitable? Just one of several linked initiatives
Adoption status Recent survey results
Disruption ahead? What are the knock-on effects of SOA?
The problem with IT today ….The problem with IT today ….
I can’t reconcile my IT costs with the business value I’m deliveringI have systems with spare capacity and systems that need more resources, but I can’t shift the work from one to anotherAll the information I need is here somewhere, but it’s hidden, fragmented & inconsistentWhat the business sees as a minor change always turns into a significant development projectComplex requirements take so long to implement that IT gets further out of step with the businessI can’t justify the resources for running occasional compute-intensive modelling & analysis workI spend so much effort tackling IT issues I lose focus on the businessI’m meeting all my IT SLAs, but users still complain of poor performance
The more IT resources I accumulate,
the less I can do with them
ServiceOriented
Architecture
New initiatives for new expectations of ITNew initiatives for new expectations of IT
Virtual Platform: Exploiting available physical resources & payment options to best serve a variable workload
EII: Delivering meaningful information from many sources to many consumers
SOA: Delivering IT functionality as reusable, interoperable, location independent services
Autonomic: self-managing, self-healing, self-tuning, self-securing
Dynamic IT: giving users all the resources they need at the time they are needed, at a cost that is related to the business value delivered
VirtualPlatform/
Grid
EnterpriseInformationIntegration
AutonomicComputing
Dynamic IT:enabling
deployment ofconcurrentinitiatives
TopicsTopics
Is Service Oriented Architecture Inevitable? Just one of several linked initiatives
Adoption status Recent survey results
Disruption ahead? What are the knock-on effects of SOA?
European SOA survey, Q1 2005European SOA survey, Q1 2005
At what stage of adoption is your organisation with respect to the following IT initiatives?
0% 20% 40% 60% 80% 100%
Web services
XML messaging
Service OrientedArchitecture
Compositeapplications
Business ProcessAutomation
Don't know No plans Investigating Pilot projectLimited live use Some live use Significant live use
UK SOA conference survey, March 2005UK SOA conference survey, March 2005
How important is each of these as a driver of SOA in your organisation?
0% 20% 40% 60% 80% 100%
App. Integrationeffectiveness
Reuse of ITinvestments
Create richapplications
Business processautomation
Respond tobusiness change
Enableoutsourcing
No importance Low priority Medium priority High priority
UK SOA conference survey, March 2005UK SOA conference survey, March 2005
If your organisation has no plans to implement SOA, how important are the following reasons for not implementing?
0% 20% 40% 60% 80% 100%
Lack of knowledge of SOA
No benefits seen in SOA
Immature SOA technology
Insuficient industry experience
No budget
Not relevant Minor consideration Major consideration Primary reason
UK SOA conference survey, March 2005UK SOA conference survey, March 2005
How well do you feel the concepts and potential benefits of SOA are understood within your organisation?
0% 20% 40% 60% 80% 100%
IT Strategists
IT Technical staff
Businessstrategists
Line of businessmanagers
Excellent Good Partial Not at all
UK SOA conference survey, March 2005UK SOA conference survey, March 2005How have the following challenges impacted your SOA work to-date?
0% 20% 40% 60% 80% 100%
Exposing legacyapplications as services
Development effort ofcomposite applications
Complexity of integratingservices
Modelling businessrequirements
Mapping businessrequirements to services
Defining businessprocess flows
Message transformation
Providing appropriatelevel of security
Managing service levelagreements
Delivering appropriateperformance/throughput
Managing servicesmetadata
Not a problem Slight problem Significant problem Show stopper
TopicsTopics
Is Service Oriented Architecture Inevitable? Just one of several linked initiatives
Adoption status Recent survey results
Disruption ahead? What are the knock-on effects of SOA?
SOA & EII – common featuresSOA & EII – common features
Monolithic approach unworkable
Multiple technologies exposed through standards
Equivalent architectures: Distributed, component-based Reuse of legacy source systems Connector/adapter layer Multiple composite delivery for different consumers Reliant on metadata registry
Is a DBMS just a particular type of service?Will SOA and EII ultimately converge?
Would a single metadata registry make sense?
SOA and the role of registrySOA and the role of registry
SOA & EII exploit heterogeneous environments Heterogeneous operating systems, databases, application
platforms, message brokers, integration technologies, service & data owners
SOA & EII also enable & encourage 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 metadata registryMultiple, uncoordinated registries will lead to chaos and ultimate failureThis will make the registry the central focus of SOA
But is a single registry a reasonable target?
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
Semantic metadata / Ontologies
Don’t forget – SOA is bi-directionalDon’t forget – SOA is bi-directional
Not just reassembling existing assets into new composites
Also replacing old assets piecemeal when they no longer deliver business value
Question: What sort of application architecture will best suit a piecemeal replacement strategy?
Traditional architecture limits adaptabilityTraditional architecture limits adaptability
Use of a common, shared database & data model
Data integrity rules implemented by database
Service components ‘joined at the hip’ through the database – compromises service autonomy
Adds unwanted complexity to piecemeal service replacement
Possible platform for long-term SOA benefitsPossible platform for long-term SOA benefits
CompositeServices
Low-level Services-Embedded application
& data platforms
BusinessProcesses
Me
tad
ata
Re
po
sit
ory
Ru
les
En
gin
e
A return to master list maintenance?
TopicsTopics
Is Service Oriented Architecture Inevitable? Just one of several linked initiatives
Adoption status Recent survey results
Disruption ahead? What are the knock-on effects of SOA?
www.idc.com
Service Oriented ArchitectureInevitable? What next?
Rob HailstoneDirector, European Software Infrastructure Research
Related Documents
