SOA - from the Enterprise to the Cloud
-
Upload
chris-swan -
Category
Technology
-
view
697 -
download
4
description
Transcript of SOA - from the Enterprise to the Cloud
![Page 1: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/1.jpg)
SOAfrom the Enterprise to the CloudFebruary 2010Version 1.0
Chris SwanCTO
![Page 2: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/2.jpg)
SOA – a personal journey that lasted 5 years
2
![Page 3: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/3.jpg)
Take a trip back to 2004
•SOA wasn’t new, but the emergence of Web Services gave it new life
•WS-* was still a smallish subset of ‘standards’• SOAP• WSDL• UDDI
•Applications could now loosely couple across boundaries that had been hard to bridge before
• Platform – Java or .Net• Language – managed code (more Java or .Net), unmanaged code (C++ etc.)
•The web had already solved plumbing problems at internet scale and in the enterprise
• This would piggyback on that success
•Infrastructure would expose lots of management services• This would result in LOTS of endpoint to manage in a large enterprise
3
![Page 4: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/4.jpg)
and this was what we ended up with…
4
WebServices
Management
Client Service
Registry
Reliable[WS-RM]
Fast
[XM
L Acceleration]
Sec
ure
[ES
F]
invoke
disc
over
register
![Page 5: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/5.jpg)
But it all went horribly wrong
5
![Page 6: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/6.jpg)
and we ended up with standards about standards
6
![Page 7: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/7.jpg)
Too many things trying to make up for the inadequacies of HTTP
7
WS-RM
WS-Addressing
WS-TransferWS-Eventing
WS-PolicyWS-Discovery
WS-MetadataExchange
WS-Security
WS-Federation
![Page 8: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/8.jpg)
When what was really needed was a better (or cheaper) MOM
8
Async SMTP AMQP
Sync HTTP IIOP
Unreliable Reliable
This is the‘magic quadrant’of SOA
But until recentlyonly proprietaryimplementations
![Page 9: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/9.jpg)
So the people who could live with HTTP retreated to simplicity
9
http://geekandpoke.typepad.com/geekandpoke/2009/11/service-calling-made-easy-part-1.html
http://www.infoq.com/articles/rest-introduction
![Page 10: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/10.jpg)
SOA doesn’t fail because of techie stuff
10
![Page 11: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/11.jpg)
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 likeyour architecture, or you’re doomed.
![Page 12: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/12.jpg)
SOA succeeds when you have
12
Command
and
Control
![Page 13: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/13.jpg)
An then everything as a service came along
13
![Page 14: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/14.jpg)
The Cloudburger
1414
Software as a service directly delivers business functionality.
Software as a service directly delivers business functionality.
Platform as a service has less direct value, but may help organizations build functionality cheaper and faster.
Platform as a service has less direct value, but may help organizations build functionality cheaper and faster.
Most of the value of Infrastructure as a Service is tied into the capital assets. Though some comes from operating efficiencies
Most of the value of Infrastructure as a Service is tied into the capital assets. Though some comes from operating efficiencies
Opex efficiency
Capex displacement
Infrastructure as a Service (IaaS)Infrastructure as a Service (IaaS)
Platform as a Service (PaaS)Platform as a Service (PaaS)
Software as a Service (SaaS)Software as a Service (SaaS)
Valu
e
![Page 15: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/15.jpg)
Back to the future – TheEGA Technical Reference Model
15
Business process /
service
Reference Data Risk Management Customer Portal
Virtualized Platform Data Grid Compute Grid Server Farm
Platform Instance Database App Server Web Server
Virtualized Operating
Environment
NFS, SMB, NAS Virtual Machine
Monitors
Load balancing, VIPs
Operating
Environment
File systems
e.g. NTFS, Ext3
Operating Systems
e.g. Linux, Windows
Network protocols
e.g. TCP/IP, UDP
Virtualized Physical LUNs Hypervisors VLANs
Physical Disks, Array
Controller, SAN
switches etc.
Servers,
Blades etc.
Switches,
Routers etc.
Storage Compute Network
Each physical layer provides Abstraction to the layer aboveEach Virtualized layer provides a flexible mapping/management point
![Page 16: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/16.jpg)
Where did the complexity go?
You chose to live without it
•Vanilla is good enough• SaaS – everybody gets the same
• Incremental upgrades• ‘Labs’ style features for the brave
or it gets squeezed out of one line of business (budget) and into another
• IaaS – S, M, L, XL• Complexities get pushed over the wall to application support
•Ops -> DevOps• How much of this can be absorbed into PaaS layer?
16
![Page 17: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/17.jpg)
The difference between ‘hosting’ and ‘cloud’
It’s all about the API• But API is maybe the wrong term
But it is all about the Interface• Invariably some kind of (HTTP) web service
• Usually REST has won out over SOAP
17
![Page 18: SOA - from the Enterprise to the Cloud](https://reader033.fdocuments.net/reader033/viewer/2022061119/5462fe43b1af9fbc4d8b53b5/html5/thumbnails/18.jpg)
18