1 / 72

The Enterprise Architecture you always wanted has been hiding in plain sight since 1991

The Enterprise Architecture you always wanted has been hiding in plain sight since 1991. Jim Webber http:// jim.webber.name Twitter: @ jimwebber. Or: A Billion Transactions Per Month Using the Web for Enterprise Heavy Lifting. Jim Webber http:// jim.webber.name Twitter: @ jimwebber.

yovela
Download Presentation

The Enterprise Architecture you always wanted has been hiding in plain sight since 1991

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Enterprise Architecture you always wanted has been hiding in plain sight since 1991 Jim Webber http://jim.webber.name Twitter: @jimwebber

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

  3. Today’s Enterprise Architecture

  4. SOA to the rescue!

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

  6. Tomorrow’s Enterprise Architecture

  7. Nirvana Enterprise Architecture, or…

  8. ESB - Erroneous Spaghetti Box? Enterprise Service Bus

  9. Architectural Fantasy

  10. Ungovernable

  11. Doesn’t Scale

  12. But we still do it.

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

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

  15. Why? Because we need the -ilities

  16. So let’s talk about those -ilities

  17. Scalability

  18. Enterprise Scalability?

  19. Web Scale!

  20. Traditional Enterprise Security

  21. End to End Secure Messaging End to End Secure Conversations

  22. Security Tokens and claims Federating access with tokens

  23. Enterprise security is awesome, but…

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

  25. Reliability

  26. Transactions

  27. Bottleneck Problem solved! Crash recovery? Denial of Service No trust

  28. Contracts

  29. <?xml version="1.0" encoding="UTF-8"?> <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:operationsoapAction="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> Hello World!

  30. The Web is a coordination platform Microformats Verbs hypermedia Status codes Media Types Semantics

  31. Pie in the sky? Not at all

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

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

  34. Three Months’ Enterprise Consulting Later…

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

  36. CEO’s Response

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

  38. Jim’s Response

  39. Thinkdifferently! (or even just stop and think)

  40. Architecture is still important

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

  42. This is how risk is mitigated. Not by buying middleware up-front!

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

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

More Related