Independent Guidance for Service Architecture and Engineering Convergent Architecture: Beyond SOA David Sprott

© 2010 Everware-CBDI International 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 St Denis Ambulatory 1140 AD High Gothic Chartres AD Rayonnant St Chapelle Paris AD Flamboyant Saint-Maclou, Rouen AD Why would software architecture be any different in principle?

© 2010 Everware-CBDI International 3 Pivot Point  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  Support for optimization and innovation.  Move to cloud

© 2010 Everware-CBDI International 4 Next Decade Business Drivers DriversExample GoalsBusiness and IT Architectural Response M&A completion Reduce post merger complexity Multi-channel Common services DemergerFacilitate separation.Componentization, ecosystem processes Cost Reduction Consolidate, eliminate duplicate resources. Focus on core business Application Modernization, layering, standardization and componentization Cloud deployment Specific business goals Reduce head count; Increase profitability; Increase resource utilization; Meet targets... Unconventional boundaries. Unconventional partners. Richer business process, event and service models Regulatory Compliance Automated policy implementation. Real time MI Standardized services Climate Change Reduce cost of energy; Optimize energy source. Smart systems, meters and sensors. Virtualization, resource sharing, cloud Collaborative processes

© 2010 Everware-CBDI International 5 Key Technology Enablers Service Oriented Architecture (SOA) Event Driven Architecture (EDA) Web 2.0SensorsAnalytics Complex Event Processing (CEP) A richer set of architectural patterns that potentially enable better achievement of principles and deliver business opportunity – in the Cloud!

© 2010 Everware-CBDI International 6 Technology Enablers - Service Oriented Architecture > Parcels System Schedule PickupPickup and Deliver Shipments Subcontractors 1.Parcels System makes asynch service call to Process Service - Schedule Pickup 2.Schedule Pickup makes asynch service call to Subcontractors Service (Operation: requestSchedule) 3.On reply, Schedule Pickup makes asynch service call to Shipments Service (Operation: scheduleShipment) Process Core Business SOA EXAMPLE > Parcels System Shipments Subcontractors 1.Subcontractors service subscribes to Shipments Service for shipmentRequestReceived 2.Parcels Systems makes call to Shipments Core Business Service which triggers shipmentRequestReceived event. 3.Subcontractors service responds to event by scheduling the shipment. This triggers the shipmentScheduled event. 4.The Shipments service responds to the shipmentScheduled event by changing the state of the shipment to Scheduled Core Business EDA EXAMPLE - Event Driven Architecture (EDA)

© 2010 Everware-CBDI International 7 Technology Enablers - 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.  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.

© 2010 Everware-CBDI International 8 Technology Enablers– Complementary Patterns EDA styleSOA style Independent process steps Events trigger services High ratio between event and possible event responses Dynamic and discretionary response to events Dynamic introduction of new events and subscribers Cross functional and inter organization processes Unpredictable orchestration requirements High business value in managing complex events Complex architecture, potentially difficult to test Agility by abstraction (context free) Triggered by events Can trigger events Predictable orchestration requirements Stable pre-conditional rules High integrity data requires extensive pre- conditions Facades for back end systems Cohesive process contained within a capability or composite application Internals of capabilities Deep architecture more moving parts Service component based testing Agility by loose coupling, contract and layer separation

© 2010 Everware-CBDI International 9 Technology Enablers - Complex Event Processing (CEP)  CEP  a separate pattern from EDA  constrained by the availability and quality of event data? Analytics Service

© 2010 Everware-CBDI International 10 Technology Enablers - Web 2.0 Shipments Subcontractors Core Business 5 > Parcels System 5. Shipments Service publishes event shipmentSpaceAvailable for route/date combination 6. Customers subscribe to shipmentSpaceAvailable 7. Customers place orders for space using hosted shopping cart SaaS 8. Order validation completed using commodity services including for address verification, sales tax calculation and amazonPayments 9. Parcels Mashup System makes Service call to Core Business Service Shipments (Operation: partLoadSale) 8 > Parcels Mashup amazonPayments SMSAlertsandNotificationsService globalAddressVerification salesTaxCalculator 7 6 9

© 2010 Everware-CBDI International 11 Ecosystem NOT Enterprise a set of business capabilities that collaborate to support a common purpose and exhibit high levels of interaction based on event relationships, shared services and information. Ecosystem ScopingExamples Benefits to real end user Power grid delivery ecosystem - nuclear, wind, coal, hydro etc generators, plus transmission grid operators and major consumers - coordinated systems deliver continuous power when required; minimize emissions. Process optimization across all participants Airport terminal ecosystem - airlines, airport security, airport logistics, ground transportation system operators, air traffic control etc - multiple transport operators, ticketing, package providers, tour operators, telecoms companies and security systems operators. Common goalBaggage ecosystem - reduce baggage losses; improve lost baggage retrieval time and cost - airlines, airports, security operators, logistics companies

© 2010 Everware-CBDI International 12 Logical Architecture Solution Layer Services Client

© 2010 Everware-CBDI International 13 Specification Architecture Solution Layer Underlying Services Core Business Services Process/Capability Services Common Components Service InterfaceThin ClientThick Client Utility Services Channel Event Services

© 2010 Everware-CBDI International 14 Specification Architecture – Sourcing Classification Solution Layer Underlying Services Core Business Services Process/Capability Services Common Components Service InterfaceThin ClientThick Client Utility Services Channel Event Services STANDARDIZED LEGACY COMMODITY ECOSYSTEM COMMODITY SPECIALTY

© 2010 Everware-CBDI International 15 Specification Architecture - Security Classification Solution Layer Underlying Services Core Business Services Process/Capability Services Common Components Service InterfaceThin ClientThick Client Utility Services Channel Event Services COMMUNITY PRIVATE PUBLIC PRIVATE COMMUNITY PRIVATE COMMUNITY PUBLIC PUBLIC PRIVATE

© 2010 Everware-CBDI International 16 Deployment Architecture - Cloud Infrastructure Managed by Infrastructure Owned by Infrastructure Located Accessible and Consumed by Public Third party provider Off premiseUntrusted PUBLIC COMMODITY SERVICES Private/ Community Enterprise or Third party provider Enterprise or Third party provider On premise Off premise Trusted STANDARDIZED PRIVATE; ECOSYSTEM AND COMMUNITY PRIVATE Hybrid Both Enterprise & third party provider Both on premise & off premise Trusted & untrusted COMMUNITY PUBLIC AND PUBLIC Based on ideas published by Cloud Security Alliance

© 2010 Everware-CBDI International 17 Conclusions – Beyond SOA  Collaborations of events, services, CE and Web 2.0  Organized around ecosystems  Enabling shared capability services  Integrated ecosystem business architecture driving Cloud deployment  More patterns...

© 2010 Everware-CBDI International 18 Everware-CBDI and CBDI Forum  Independent specialist AM/SOA firm  Located UK and USA  CBDI Forum  Practices CoE  Documented, published best practices, reference architecture, repeatable processes  Structured, meta model based, model driven, agile practices  Approach widely used by F1000 companies, consultancies/integrators and government departments  Facilitating SOA standards  25,000+ subscribing architects worldwide  Everware-CBDI  AM/SOA Solution Business including Consulting, Education and Knowledge products and tools Independent Guidance for Service Architecture and Engineering

© 2010 Everware-CBDI International Independent Guidance for Service Architecture and Engineering