1. Successful SOA with REST
Jim Webber
http://jim.webber.name
Twitter: @jimwebber

2. Or: A Billion Transactions Per Month
Using the Web for Enterprise Heavy Lifting
Jim Webber
http://jim.webber.name
Twitter: @jimwebber

4. Today’s Enterprise Architecture
Accounting Marketing
Product Development Support

6. “SOA: Principles of Service Design underwent
a thorough technical review involving over
60 reviewers from different vendors,
organizations, and professions across North
America, Europe, and Asia. The book has been
formally endorsed by members of major SOA
vendors, including IBM, Microsoft, Oracle,
BEA, and Intel.”
-- Thomas Erl

7. Tomorrow’s Enterprise Architecture
BPM
Services
Business Business Business
Service Service Service
Data Data Data Data Data
Service Service Service Service Service

8. Nirvana Enterprise Architecture, or…
BPM Business Business Business
Service Service Service Service
ESB
Basic Basic Basic Basic Basic
Service Service Service Service Service

9. ESB - Erroneous Spaghetti Box?
Enterprise Service Bus

13. But we still do it.

14. Why?
Because it’s “less risky”

15. Why?
Because that’s what the market does

16. Why?
Because we need the -ilities

17. So let’s talk about those -ilities

20. Web Scale!

21. Traditional Enterprise Security

22. End to End Secure
Messaging
End to End Secure
Conversations

23. Security Tokens
and claims
Federating access
with tokens

25. …you
wouldn’t
use it at
home!

29. Bottleneck
No trust
Crash Denial of
recovery? Service

31. <?xml version="1.0" encoding="UTF-8"?>
Hello World!
<definitions name="HelloService"
targetNamespace="http://www.ecerami.com/wsdl/HelloService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.ecerami.com/wsdl/HelloService.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<message name="SayHelloRequest">
<part name="firstName" type="xsd:string"/>
</message>
<message name="SayHelloResponse">
<part name="greeting" type="xsd:string"/>
</message>
<portType name="Hello_PortType">
<operation name="sayHello">
<input message="tns:SayHelloRequest"/>
<output message="tns:SayHelloResponse"/>
</operation>
</portType>
<binding name="Hello_Binding" type="tns:Hello_PortType">
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="sayHello">
<soap:operation soapAction="sayHello"/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:examples:helloservice"
use="encoded"/>
</input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:examples:helloservice"
use="encoded"/>
</output>
</operation>
</binding>
<service name="Hello_Service">
<documentation>WSDL File for HelloService</documentation>
<port binding="tns:Hello_Binding" name="Hello_Port">
<soap:address
location="http://localhost:8080/soap/servlet/rpcrouter"/>
</port>
</service>
</definitions>

32. The Web is a coordination platform
Media
Types

34. A Case Study
Client
• UK-based telecoms service provider
• Global customers (no easy downtime)
Problem
• Scalability and system resilience issues
• Huge growth curve to from a million to a
billion messages per month
• Costs

35. Platform Architecture
Where’s my
Bottleneck Nightmare!
file gone?
Carrier
Carrier Integration Shared
Carrier Gateway
Carrier Database Filesystem
Post Voice to Text
Processing Algorithms
Fix things
up here Shoehorn it in
that other
program

37. The £10* Million Solution
“Queue” Shared
Gateway
Database Filesystem
Carrier
Carrier
Carrier
Carrier Enterprise Service Bus
Post Voice to Text
Processing Algorithms
* Solution does not include actual implementation

39. ThoughtWorks was given the output from a
previous enterprise consultancy…
…and told to “do that, but cheaper”

41. Think
differently!
(or even just stop and think)

42. Architecture is still important

43. Agile EA: Prioritise Service Delivery
Start by
fixing
storage
Carrier
Carrier Integration Shared
Carrier Gateway
Carrier Database Filesystem
Post Voice to Text
Processing Algorithms

48. Storage Manager Project Delivery
Small team Java solution
3 Week Inception Performance testing
throughout
14 iterations – See Jones and Kua paper,
Agile 2009
Continuously built and
deployed for testing

49. Web-friendly Architecture
(mostly wallet-friendly too!)
Encapsulates
storage detail!
Fast!
Free!
Cacheable!
Jboss/Tomcat
Optimised disk Optimised
access!
Storage Manager server config
GPFS SAN
Spend £ on the
right
Infrastructure

52. What is going on
with these peaks?
here?

53. Hypothesis
Directories are becoming full, slowing
random access to files

54. Prediction
A single directory will result in
linearly degrading performance

56. Outcome
Adapt the directory structure to take
advantage of the underlying file
system

57. Improving Enterprise Architecture
Reduced Scalable!
Load
Carrier
Carrier Integration Storage
Carrier Gateway
Carrier Database Manager
Post Voice to Text
Processing Algorithms
“She’ll be
right” Just shoehorn it
in that other
program

58. Storage Manager Benefits
• Immediate reduced load on integration
database
• Enabled removal of code from systems
• Delivered business value by keeping
customers happy
• “The best software we have ever deployed”
– Operations director I’ll come back to this

60. What if…
We took our inspiration from
successful Web-scale companies?

61. What if…
And took the time to understand our
SLAs?

62. What if…
And picked the right technology
solution?
Not just the one we’re being sold?

63. What if…
We built a scalable compute
platform?

65. Grid Project Delivery
Larger team Java solution
3.5 Week Inception Performance testing
throughout
18 iterations
Continuously built and
deployed for testing

66. Web-friendly Architecture
(very wallet-friendly!) Fault
Tolerant
ASR ASR ASR ASR
Fault
Tolerant
Grid Pipeline
Embedded Jetty
Just Embedded Jetty
HTTP Embedded Jetty
Embedded Jetty Just
Embedded Jetty HTTP
Grid Manager
Grid Manager
Grid Manager
Grid Manager Sustainable
Grid Manager container for
business logic
ASR ASR ASR ASR
£0 Grid Pipeline
Software
Infrastructure

67. Improving Enterprise Architecture
Scalable Processing Platform
Massively
Reduced
Load Scalable!
Carrier
Carrier Integration Storage
Carrier Gateway
Carrier Database Manager
Post
Grid
Processing
“She’ll be
Scalable,
right”
sustainable!

68. Grid Benefits
• Scalable, resilient platform
• Aligned with business goals
• Further reduced load on integration database
• Set architectural patterns
• Deliver business value by processing more
messages at lower cost than ever before
• “The best software we have ever deployed”
– Operations director Better every time!

69. £10,000,000
Up-Front Cost of Bus Architecture

70. £1,000,000
Actual Cost of Completed Project

71. £0
Cost of Middleware

72. The Web works
And its economies
of scale eclipse
your vendors’