Presentation to Oracle Higher Education SOA round table (Feb 2010)

1. SOA from the Enterprise to the Cloud February 2010 Version 1.0

2. SOA – a personal journey that lasted 5 years 2

4. WS-* was still a smallish subset of ‘standards’

5. SOAP

6. WSDL

7. UDDI

8. Applications could now loosely couple across boundaries that had been hard to bridge before

9. Platform – Java or .Net

10. Language – managed code (more Java or .Net), unmanaged code (C++ etc.)

11. The web had already solved plumbing problems at internet scale and in the enterprise

12. This would piggyback on that success

13. Infrastructure would expose lots of management services

14. This would result in LOTS of endpoint to manage in a large enterprise3

15. and this was what we ended up with… 4 Registry Web Services Management discover register Secure [ESF] Fast [XML Acceleration] Client Service Reliable [WS-RM] invoke

16. But it all went horribly wrong 5

17. and we ended up with standards about standards 6

18. Too many things trying to make up for the inadequacies of HTTP 7 WS-Federation WS-Addressing WS-Security WS-RM WS-Eventing WS-Transfer WS-MetadataExchange WS-Policy WS-Discovery

19. When what was really needed was a better (or cheaper) MOM 8 This is the ‘magic quadrant’ of SOA But until recently only proprietary implementations

20. So the people who could live with HTTP retreated to simplicity 9 http://www.infoq.com/articles/rest-introduction http://geekandpoke.typepad.com/geekandpoke/2009/11/service-calling-made-easy-part-1.html

21. SOA doesn’t fail because of techie stuff 10

22. SOA fails because of Conways Law 11 “...organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations” Or… your org chart had better look like your architecture, or you’re doomed.

23. SOA succeeds when you have 12 Command and Control

24. An then everything as a service came along 13

25. The Cloudburger 14 Opex efficiency Software as a service directly delivers business functionality. Software as a Service (SaaS) Platform as a service has less direct value, but may help organizations build functionality cheaper and faster. Value Platform as a Service (PaaS) Infrastructure as a Service (IaaS) Capex displacement Most of the value of Infrastructure as a Service is tied into the capital assets. Though some comes from operating efficiencies 14

26. Back to the future – TheEGA Technical Reference Model 15 Each physical layer provides Abstraction to the layer above Each Virtualized layer provides a flexible mapping/management point

28. SaaS – everybody gets the same

29. Incremental upgrades

31. Complexities get pushed over the wall to application support

32. Ops -> DevOps

33. How much of this can be absorbed into PaaS layer?16

35. Usually REST has won out over SOAP17

36. 18