Eci Service Architecture Evolution 1


Published on

SOA is a core architecture that will persist for many decades to come. But the original enterprise SOA vision is unlikely to be realized in the expected manner. Rather SOA will morph and converge with other concepts and technologies. In this report we explore how architecture practice is evolving to respond to the prevailing business climate and to embrace emerging technology trends. Summarizes CBDI Journal Report, November 2009

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Eci Service Architecture Evolution 1

  1. 1. Service Architecture Evolution David Sprott Smart Practices for Application Modernization
  2. 2. Architecture and Time Gothic cathedral architecture style evolved over several centuries as techniques, materials and skills developed and as the buildings were erected in new environments that presented new challenges. Early Gothic High Gothic Rayonnant Flamboyant St Denis Ambulatory Chartres St Chapelle Paris Saint-Maclou, Rouen 1140 AD 1194 1224 AD 1243-1248 AD 1434-1521 AD Why would software architecture be any different in principle? © 2009 Everware-CBDI International
  3. 3. Business Requirements and Drivers Last decade: SOA = primarily an IT led strategy. Vendor led. “SOA projects” and technology infrastructure. The recession has had a major impact on IT project activity. “There is no business as usual – all architecture activity is focused on conventional integration.” Chief architect, Banking “EA function has been eliminated as a cost saving measure because it could not show short term ROI.” Chief architect, Pharmaceutical Company Next decade? Intense focus on cost reduction and support for optimization and innovation. © 2009 Everware-CBDI International
  4. 4. New Business Reality Business Example Goals Business and IT Architectural Response Drivers Cost Consolidate disparate, Application Modernization Reduction eliminate duplicate Separation of business process and back end systems. resources. Standardization on common processes. Componentization of back end systems. M&A Reduce complexity of panic Multi-channel business and technology architecture. completion post merger activity. Common services span and standardize multiple legacy silos. Reduce point to point integration. Demerger Reduce costs of, and Componentization, Layered architecture. facilitate ease of separation. Specific Reduce head count; Breaking down conventional (application) boundaries. business increase seat profitability; Engage with unconventional partners. goals increase resource Create richer business process, event and service models including (CSFs) utilization; meet emission management information and business intelligence. targets etc. Climate Reduce cost of energy; Smart systems fed by smart meters and sensors. Change Optimize energy source. Virtualization and shared resources. Collaborative processes across disparate supply chains. Regulatory Automated policy Standard compliance operations on all services. Compliance implementation. Real time MI © 2009 Everware-CBDI International
  5. 5. Key Technology Enablers and Influences Web 2.0 Sensors Analytics Complex Event Processing (CEP) Event Driven Architecture (EDA) Service Oriented Architecture (SOA) A richer set of architectural patterns that potentially enable better achievement of principles and deliver business opportunity – in the Cloud! © 2009 Everware-CBDI International
  6. 6. Technology Enablers and Influences - Cloud Cloud Description Examples Evolving Service Capability Architecture SaaS Multi-tenant software as a service Salesforce; Google Apps; Business Capability services architecture delivered as Web IBM LotusLive [Important note – Most SaaS services. vendors don’t use SOA today,] Utility Data center components accessed Amazon EC2; Sun Open Infrastructure Capability services Computing as Web services. Source Cloud; IBM Utility Computing Web services Web services hosting or broking Strike Iron, Xignite Commodity services brokers allows developers to assemble business and technology services from disparate sources. Business Enterprises offer Web based Amazon Web services; US Business services services business services as an integral Postal Service; DHL part of their business offering ExpediteShip; Platform as a Development, integration and Salesforce; Dynamic SOI Service operating environment allows use Google App Engine; BT of virtual infrastructure 21C Network; IBM Rational Business ESB in the cloud. BT Integrate; OpSource SOI Service Connect; Network © 2009 Everware-CBDI International
  7. 7. Technology Enablers and Influences - Complex Event Processing (CEP) Process Service RAW EVENT RAW Capability Service BUSINESS CEP EVENT EVENT RAW Core Business Service EVENT RULES CEP should be regarded as a separate pattern from EDA with very different objectives. EDA may or may not be adopted in conjunction with CEP. They are separate decisions. The development of CEP is largely constrained by the availability and quality of event data which probably explains why CEP is primarily deployed in point applications today. © 2009 Everware-CBDI International
  8. 8. Technology Enablers and Influences - Event Driven Architecture (EDA) <<Application>> <<Application>> Parcels System Parcels System 1 3 Process EDA EXAMPLE Schedule Pickup Pickup and Deliver 3 2 2 5 Shipments 4 Shipments 1 Subcontractors Core Business Subcontractors Core Business 1. Parcels System makes asynch service call to 1. Subcontractors service subscribes to Shipments Process Service - Schedule Pickup Service for shipmentRequestReceived 2. Schedule Pickup makes asynch service call to 2. Shipments service subscribes to Subcontractors Service shipmentsScheduled (Operation: requestSchedule) 3. Parcels Systems makes call to Shipments Core 3. On reply, Schedule Pickup makes asynch Business Service which triggers service call to Shipments Service shipmentRequestReceived event. (Operation: scheduleShipment) 4. Subcontractors service responds to event by scheduling the shipment. This triggers the shipmentScheduled event. SOA EXAMPLE 5. The Shipments service responds to the shipmentScheduled event by changing the state of the shipment to Scheduled. © 2009 Everware-CBDI International
  9. 9. Technology Enablers and Influences - EDA Patterns Publish/Subscribe (Pub-Sub). Consumers subscribe to events. Event emitters have no knowledge of subscriber behavior. Services will normally register through a 3rd party (an event service) rather than directly with each other, adding a level of decoupling to the architecture. This would involve services registering as an Event source and then another service subscribing for the event. Capability Service – Services offer complete capability relating to a business resource independent from other services. State Change Precedence – Minimum pre condition requirement prior to change of state. Pre conditions become post conditions wherever possible. (see below) Instead of: “When creating a shipment if a customer is not provided, create a new customer.” We have: “When a shipment has been created, if a customer was not provided, create a new customer.” Based on work published by: Udi Dahan, The Architecture Journal 2009 © 2009 Everware-CBDI International
  10. 10. Technology Enablers and Influences – Complementary Patterns EDA style SOA style Independent process steps Predictable orchestration requirements Cross functional and inter organization processes Cohesive process contained within a (ecosystems) capability or composite application Requirement for dynamic and discretionary response Facades for back end systems to events High integrity data requires extensive pre- Dynamic introduction of new events and subscribers conditions High business value in managing complex events Stable pre-conditional rules High ratio between event and possible event Service requests and responses can responses trigger events Events trigger services The SOA style will increasingly be used to architect the internals of business capabilities which have a high level of stability. EDA will be adopted increasingly where response to events is highly dynamic and orchestration requirements are less predictable. It will also be very relevant in situations where new events and particularly new subscribers may be required on a dynamic basis. Whilst there is lower orchestration required for EDA there is the potential for extremely complex architecture which is very hard to test because there is no statement of how things in the architecture are linked. © 2009 Everware-CBDI International
  11. 11. Technology Enablers and Influences - Web 2.0 8 <<Application>> <<Application>> SMSAlertsandNotificationsService Parcels System Parcels Mashup 9 globalAddressVerification salesTaxCalculator amazonPayments 6 10 7 Shipments Subcontractors Core Business 6. Customers subscribe using SMSAlertsandNotificationsService to shipmentSpaceAvailable 7. Shipments Service publishes event shipmentSpaceAvailable for route/date combination 8. Customers place orders for space using hosted shopping cart SaaS 9. Order validation completed using commodity services including for address verification, sales tax calculation and amazonPayments 10. Parcels Mashup System makes Service call to Core Business Service Shipments (Operation: partLoadSale) © 2009 Everware-CBDI International
  12. 12. Technology Enablers and Influences - Sensors Infrastructure Service Bus (ISB) Resource-level Infrastructure Services Infrastructure Data Resources Server Router Switch Grid Store A rich source of events that allow enterprise systems to respond to events on the ground. Example Systems Management - revolutionized by devices such as servers, network switches etc that emit events and offer services in order that their entire function was completely automatic Rather than waiting for the problem to occur, and going further to automatically provisioning alternative resources on demand according to preset policy © 2009 Everware-CBDI International
  13. 13. Ecosystem NOT Enterprise Benefits of Ecosystem Examples Scoping Focuses on outcomes of a Power grid delivery ecosystem involving nuclear, wind, coal, hydro etc collaboration that delivers generators, plus transmission grid operators and major consumers allows benefits to the real end user coordinated management systems to deliver continuous power when required and or higher order goals and to minimize emissions. Encourages process Airport terminal ecosystem involving airlines, airport security, airport logistics, optimization across all ground transportation system operators, air traffic control etc facilitates potential participants enhanced security through coordinated CEP systems. Transportation systems ecosystem involves multiple transport operators, value adding service providers such as ticketing, package providers, tour operators, telecoms companies and security systems operators. Focus on a common goal Reduce airline baggage losses and improve lost baggage retrieval time and cost. Baggage ecosystem involving airlines, airports, security operators, Define an ecosystem as a set of business capabilities that collaborate to support a common purpose and exhibit high levels of interaction based on event relationships, shared information and data concepts. An ecosystem may include part or whole of one or many business processes; may span one or more enterprise. . . © 2009 Everware-CBDI International
  14. 14. Conclusions Event Driven Architecture patterns may increase loose coupling and may reduce or increase complexity. The CEP pattern adds new dimension to SOA that can potentially add business value. Services will continue to be widely used because they are a real world concept. Events occur in the real world Architecture must comprehend and respond to them appropriately. Integrating enterprise systems into Web 2.0 can offer more sophisticated behaviors to business processes and consumers; capture richer set of raw and complex events. Same applies to integrating sensors and analytics systems. Cloud deployments will increasingly become normal. Ecosystems will probably be early adopters of Cloud Computing Enterprise systems and enterprise architecture are less relevant to today’s business goals; may be widely replaced with goal centric systems that focus on unconventional boundaries (ecosystem) spanning enterprises and business processes. . Conventional boundaries no longer automatically apply. Ecosystems model the real world. © 2009 Everware-CBDI International
  15. 15. This presentation summarizes the CBDI Journal report published November 2009: Service Architecture Evolution SOA is a core architecture that will persist for many decades to come. But the original enterprise SOA vision is unlikely to be realized in the expected manner. Rather SOA will morph and converge with other concepts and technologies. In this report we explore how architecture practice is evolving to respond to the prevailing business climate and to embrace emerging technology trends. By David Sprott Read the full report: Subscribe to the CBDI Journal or license the SOA Process Toolkit at: . © 2009 Everware-CBDI International
  16. 16. Smart Practices for Application Modernization 16 © 2009 Everware-CBDI International