Convergent Architecture: Beyond SOA

1. Convergent Architecture:Beyond SOA David Sprott

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 1194 1224 AD Rayonnant St Chapelle Paris 1243-1248 AD Flamboyant Saint-Maclou, Rouen 1434-1521 AD Why would software architecture be any different in principle?

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

4. Next Decade Business Drivers

5. Key Technology Enablers 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!

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

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.

8. Technology Enablers– Complementary Patterns

9. Technology Enablers - Complex Event Processing (CEP) • CEP • a separate pattern from EDA • constrained by the availability and quality of event data? Analytics Service

10. Technology Enablers - Web 2.0 6 7 SMSAlertsandNotificationsService <<Application>> Parcels Mashup <<Application>> Parcels System globalAddressVerification 8 salesTaxCalculator amazonPayments 9 5 Shipments Core Business Subcontractors 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)

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.

12. Logical Architecture Solution Layer Client Services

13. Specification Architecture Channel Channel Channel Event Services Solution Layer Thick Client Thin Client Service Interface Common Components Process/Capability Services Core Business Services Underlying Services Utility Services

14. Specification Architecture – Sourcing Classification Channel Channel Channel SPECIALTY Event Services Solution Layer Thick Client Thin Client Service Interface Common Components COMMODITY Process/Capability Services ECOSYSTEM STANDARDIZED Core Business Services COMMODITY LEGACY Underlying Services Utility Services COMMODITY

15. Specification Architecture - Security Classification Channel Channel Channel PUBLIC COMMUNITY PUBLIC Event Services Solution Layer Thick Client Thin Client Service Interface PRIVATE Common Components Process/Capability Services COMMUNITY PRIVATE PRIVATE Core Business Services COMMUNITY PRIVATE PRIVATE Underlying Services Utility Services PUBLIC

16. Deployment Architecture - Cloud Based on ideas published by Cloud Security Alliance

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 . . .

18. Everware-CBDI and CBDI Forum • IndependentspecialistAM/SOAfirm • Located UK and USA • CBDI Forum • Practices CoE • Documented, published bestpractices,referencearchitecture,repeatableprocesses • Structured, meta model based, model driven, agile practices • Approach widely used by F1000 companies, consultancies/integrators and government departments • FacilitatingSOAstandards • 25,000+subscribingarchitectsworldwide • Everware-CBDI • AM/SOA Solution Business including Consulting, Education and Knowledgeproducts and tools Independent Guidance for Service Architecture and Engineering

19. www.cbdiforum.com Independent Guidance for Service Architecture and Engineering www.everware-cbdi.com 19