Copyright IBM Corporation 2006. All Rights Reserved.

1,540 views
1,443 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,540
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Copyright IBM Corporation 2006. All Rights Reserved.

  1. 1. Software SOA for the Web and Extreme SOA… Jerry Cuomo gcuomo@us.ibm.com IBM Fellow WebSphere Chief Technology Officer © 2006 IBM Corporation
  2. 2. Software Topics – Radically Simplifying Middleware  SOA and Web 2.0  XD Business/Object Grid  Real-time and Event- Driven SOA  SOA Registry and Governance 2
  3. 3. Software Web 2.0 – What does it mean to me ? technology Radical Simplification Mash-ups HTTP ATOM PHP REST AJAX JSON RSS Networking Wikis Blogs People Behavior Harnessing Collective Intelligence sociology 3
  4. 4. Software Technology Attributes of Web 2.0 Mash-ups A website or Web 2.0 application that uses content from more than one source to create a completely new service. Content used in mashups is typically sourced from a third party via a public interface or API. Other methods of sourcing content for mashups include Web feeds (e.g. RSS or Atom) and JavaScript. Lightweight XML data over HTTP, in a lightweight approach sometimes referred to Programming as REST (Representational State Transfer) as an alternative to SOAP Model Feeds RSS/ATOM allows someone to link not just to a page, but to subscribe to it, with notification every time that page changes. Wikis Control over unique, hard-to-recreate data sources that get richer as more people use them. "SQL is the new HTML." Database and content management is a core competency of Web 2.0 companies. Rich User AJAX incorporating: XHTML and CSS, DOM, XML and XSLT;, Experience XMLHttpRequest and JavaScript allowing information to be mashed up into new interactive portals." 4
  5. 5. Software Core Competencies of Web 2.0 Companies The Web is about content - HTML, forms, images, audio, … Content Application interfaces and data surface through Web pages and feeds. Mashups are an additional, personal approach to integration that builds on content and complements WS-*. Services Services, not packaged software, with cost-effective scalability Collective intelligence Harnessing collective intelligence Users Trusting users as co-developers Leveraging Leveraging the long tail through – Communities and Customer Long-Tail self-service and ad hoc B2B Users must be treated as co-developers, in a reflection of open source Perpetual Beta development practices. The open source dictum, "release early and release often 5
  6. 6. Software Global SOA Enterprises are exposing more services and feeds to the Web …and consuming more services and feeds from the Web Web REST JSON ATOM XML RSS “Bridging Web and Enterprise SOA” mashups JMS SOAP WS-* MOM WPS, ESB, Portal Legacy App Server CICS WAS, CE, Tomcat DB2 IMS J2EE Composite Applications Enterprise Enterprise mashups 6
  7. 7. Software eBay APIs – Driving volumes of transactions  eBay Web Services supports some 2.5 billion API calls per month  Approximately half of all listings on eBay.com involve eBay Web Services  25,000 outside developers are using the APIs  Participating developers have produced more than 1,600 applications
  8. 8. Software Bridging Web and Enterprise SOA Web SOA Enterprise SOA J2SE AJAX J2EE FE Ruby JSON ATOM WS-* WSDL ED JDBC S PHP XML RSS JMS Web SOA SOAP FEEDS Bridge MOM REST .NET S Enterprise CICS ED FE MASHUPS 8
  9. 9. Software Components of the Web.Zero platform The “Zero” extension after Java, PHP, etc., implies a level of consistency and shared convention in the areas of programming & component models, shared-services, deployment and management Java.Zero Lightweight Java Environment (CGI-Like), MVC Framework plus Framework for creating and access Feeds (ATOM) & Services (REST) PHP.Zero IBM PHP distribution, built on open source from php.net, plus MVC framework and IBM utilities for Rest/Atom Services AJAX.Zero Dojo toolkit, plus IBM utilities for Web-based Pub/Sub DATA.Zero Services and tools for access data and caching data from any of the .0 platforms. Language integrated SQL for Java and PHP SOA.Zero Services and tools for creating simple work flow (bpel--), mediations and simple business rules MASHUP.0 Services and tools need to client-side and server side mash-ups XD.0 Quality of Services utilities for overload protection (data-base connection manage, session cache, virtual machine pool, application load balancing MGMT.0 Consistent management of “.0” assets. 9
  10. 10. Software PRELIMINARY STRATEGY - IBM Web.Zero Platform SOA meets the Web Web.Zero Platform as a bridge between Web and Enterprise SOA Technology Components of Web.Zero can be embedded in the IBM SOA platform allowing a simple on-ramp Strategy to Enterprise SOA Web.Zero Platform as an entry level SOA Platform Appeal to customers and partners with basic SOA needs (e.g., Departments and SMB) Create Situational Applications using PHP, Java and AJAX Create Mash-up style applications without programming Web.Zero as a development methodology Affiliated Open Source project defining conventions for constant programming model, deployment Sociology model, administration for PHP, Java, Ajax based Web 2.0 applications Strategy Use public Blogs and Wikis to discuss product development, Source code, Examples, Bugs, etc. Web.Zero Market-place provides a place for customers and partners to collaborate around a common platform Vibrant collections of skills and services Subscription-based model to access high-value components 10
  11. 11. Software PRELIMINARY - IBM Web.Zero Platform Architecture Web.Zero Web.Zero Enterprise SOA Composition and Mashups Service Platform Web.0 Common Browser SQL Services& Libraries Platform AJAX.0 Session DB2 dojo Data Access Messaging SOAP Legacy CICS REST SendMail IMS XD.0 (QoS) PHP.0 REST-SOAP ATOM SOAP MASHUP.0 … Java WPS, ESB, Portal QEDWiki SOA.0 Java.0 Workflow J.0 App Server WAS, CE, Tomcat Mediations J2EE Rules Ruby.0, … Web 2.0 Management & Deployment Tools 11 IBM Confidential
  12. 12. Software Java Zero: Simplifying Assumptions  Application-centric (Where’s the container ?)  Simplified Runtime Model (Think CGI)  “Pay as you go” approach with libraries for extension (Think C/C++)  Goal is for base-footprint to be smaller than Tomcat  Simplified Programming Model (Think PoJos)  PoJo’s plus annotations with Injection (Think Spring)  Simple MVC Framework (Think RoR)  RESTful (Where’s the WSDL ?)  Methods on Objects can be exposed as a REST Service with a single annotation (Think SCA-lite)  Convention over configuration  Everything done using code, annotations and simple property files  Configuration is optional – reasonable behavior without any configuration 12
  13. 13. WebSphere Service Registry and Repository Topics – Radically Simplifying Middleware  SOA and Web 2.0  XD Business/Object Grid  Real-time and Event- Driven SOA  SOA Registry and Governance 13 SOA on your terms and our expertise
  14. 14. WebSphere Service Registry and Repository ObjectGrid – Information Fabric Characteristics  High end, mission critical OLTP applications  High Write/Low Read Ratios Elements 5. Partitions: WebSphere Partitioning Facility (WPF) 6. Caching: XD Object Grid 7. WLM: Partition aware routing in ODR, EJBs 8. HA: High Availability Manager 9. Autonomics: Partition Manager MBean, Application Placement Controller 14 SOA on your terms and our expertise
  15. 15. WebSphere Service Registry and Repository On-Line Transaction Processing (OLTP) Traditional OLTP Pattern Requests Object Grid (XD) Data – DB2 Router 1. Requests are evenly sprayed to WAS 2. Transactions are pushed back to the database to endure consistency 3. Database becomes bottleneck and prevents scaling 15 SOA on your terms and our expertise
  16. 16. WebSphere Service Registry and Repository WebSphere Information Fabric– Partitioning using XD Object Grid Requests Object Grid (XD) Data – DB2 Router 1. Partitioning 16 SOA on your terms and our expertise
  17. 17. WebSphere Service Registry and Repository WebSphere Information Fabric – Caching using XD Object Grid Requests Object Grid (XD) Data – DB2 Router 1. Partitioning 2. Caching 17 SOA on your terms and our expertise
  18. 18. WebSphere Service Registry and Repository WebSphere Information Fabric – WLM using XD Object Grid Requests Object Grid (XD) Data – DB2 Router 1. Partitioning 1. WLM 2. Caching 18 SOA on your terms and our expertise
  19. 19. WebSphere Service Registry and Repository WebSphere Information Fabric – High Availability using XD Object Grid Requests Object Grid (XD) Data – DB2 HA Manager Router X 1. Partitioning 1. WLM 2. Caching 2. High Availability 19 SOA on your terms and our expertise
  20. 20. WebSphere Service Registry and Repository WebSphere Information Fabric – Repartitioning using XD ObjectGrid Requests Object Grid (XD) Data – DB2 HA Manager Router X 1. Partitioning 1. WLM 1. Re-Partitioning 2. Caching 2. High Availability 20 SOA on your terms and our expertise
  21. 21. WebSphere Service Registry and Repository XD Object Grid - Test Results from the Lab Total TPS (cluster) 3500 Over 3000 transactions 3000 Linear Scaling (over 6 blades) 2500 Heavy weight- Transactions 2000 Total TPS (cluster) 1500 1000 Topology 500 0 1x14 2x14 3x14 4x14 5x14 6x14 MxN means M boxes with N threads driving work. Average response time is 31ms All networks are Gb ethernet using the blade switch on the center. 21 SOA on your terms and our expertise
  22. 22. WebSphere Service Registry and Repository Topics – Radically Simplifying Middleware  SOA and Web 2.0  XD Business/Object Grid  Real-time and Event- Driven SOA  SOA Registry and Governance 22 SOA on your terms and our expertise
  23. 23. Software Dimensions / Levels of Event Infrastructure Capability Responsiveness Event Throughput Event Pattern Programming Scalability Msgs DB Richness Ease of use Hard real 100,000’s Inductive Internet scale responsiveness/capability events/sec/server Time Homeland security Untrained patterns analysis and - information 100,000’s endpoints (deterministic, us) reduction detect - trained pattern Online Gaming Increasing Soft real Tools for Collaborating domains Time Financial market information and program trading integrating content (scheduled, ms) behavior models, Agile enterprise integrated C and C RFID, retail, distribution, Near real manufacturing Home healthcare monitoringwith Tools for 1000’s events/sec/server Integration Managed ESB with event services Time processes, distributed (< sec) workflows deployment Transactional 100’s General multi CEP Event Event Server clusters OLTP events/sec/server Stream pattern net Specifications assembly OLAP Sequences threshholds, groups Single server Datamining Data Message at a time filter / route Warehouse 23
  24. 24. Software Current IBM Middleware and advanced technology coverage Responsiveness Event Throughput Event Pattern Programming Scale Out Msgs DB Richness Ease of use Hard real 100,000’s Inductive Internet scale events/sec/server Time - Untrained patterns 100,000’s endpoints (deterministic, us - trained pattern detect responsiveness/capability Soft real Tools for Collaborating domains GAP Time integrating content (scheduled, msec GAP behavior models, Increasing GAP Near real 1000’s events/sec/server Integration with Tools for Managed ESB with event services Time processes, distributed subsec WII Dstream workflows deployment GAP WMQ Transactional 100’s General multi CEP Event Event Server clusters ACT2 DB2 OLTP BPM events/sec/server Stream pattern net in WBI Specifications assembly Derby WPM OLAP Sequences threshholds, groups Single server ESB CEI Datamine routing warehouse Message at a time filter / route 24
  25. 25. Software EDA Approach and Progress  SWG approach to event-driven applications will focus on three basic thrusts:  Highlight existing event-driven application capabilities to clients around existing product set  Invest in enhancements to existing run-times, programming model and tools to support specific classes of EDAs and improve ease of implementation  Invest in new “real-time” middleware stack (and potentially appliances) to meet specific QoS attributes not possible with existing middleware stack.  Progress to date:  Project Marian • Addressing the requirement for real-time messaging (right up to microseconds response time) for Financial Market Data – being piloted by several top financial companies • Industry vertical solution combining research code and products – SWG MQ Event Broker + Research RMM (Reliable Multicast Messaging)  WebSphere Real-time Deployments • Real-time Garbage Collection, Real-time Messaging, Class-Pre Compile, Real-time Linux • Government projects currently piloting technology  Acquisition of Datapower • Gigabit SOA processing • XML, Web Services, Transforms, Routing, Integration 25
  26. 26. Software SWG will continue to invest in enabling event-driven applications on its current platform as well as make investments in real-time middleware solutions, patterns Realtime solutions, patterns Programming model Programming model RT Middleware Composition Composition Increasing response time Decreasing predictability Application Hosting Realtime Application Hosting ESB and DataPower Realtime ESB messaging Realtime messaging JVM Realtime Java Metronome Realtime operating system operating system Linux with extensions Current stack Real-time stack Optimized for high throughput Optimized for time-dependent predictable sub-second response Partial Supported In Development support and Pilot 26
  27. 27. Software Example: Telecom  Focused on infrastructure for telecom services  Not billing, operations, etc – those are traditional IBM strengths  Instead, think call handling, media delivery, online services  Industry is moving quickly to IP-based networks  Voice over IP the most prominent example but also text, data, audio, video, and online services such as conferencing or presence  Also convergence of fixed and mobile services  Divided into service, control and transport planes  Each with their own speed and reliability characteristics  IBM focused on middleware and services for the “service” or application hosting plane – key pain point today is inadequately low and predictable latency  Converged J2EE/SIP container for services plane  Based on JSR 116 SIP servlets  Targeting 20ms latency per SIP message (8-16 messages for a call setup)  Targeting 100ms latency for failover detection  Hoping to use off the shelf hardware and OS 27
  28. 28. Software RTJ Garbage Collection Benefits for WAS SIP Existing Garbage Collection With RTJ Garbage Collection Input Rate Input Rate Processed Data Processed Data WAS SIP WAS SIP Garbage Garbage Collection Collection t=0 t=0 t=0 t=0 t=0 t=0  Existing Java garbage collection (GC)  Metronome garbage collection stops all processing activity amortizes the GC cost  SIP messages use an unreliable transport  Tunable, periodic garbage collection  Long GC activity will cause SIP messages to be dropped  Many, small GC activities  Even with large message queue buffers  Messages are queued during GC  Message retransmission adds additional activity load to heavily burdened server  No loss  Positive feedback results in network storm 28
  29. 29. Software Detailed Naval Scenario Description This scenario represents a sequence of events necessary for a Naval ship to defend its self against a missile threat. This ship has 10 seconds to react and destroy the missile, in that time our Real-Time Event Driven Architecture must assess, correlate, transform, enrich and route a multitude of complex event streams across three time epochs from sensors to command and control (C2) and finally weapons across its associated Real-time Enterprise Service Bus (ESB). Phased C2 Array RADAR RAM Impact point ECM Missile Silkworm ss Launcher ms SPD : 820 mph = 1203 ft/sec µs SPD : 1000 mph = 1467 ft/sec RT- ESB 1000m = .5 NM 6000m = 3 NM RT EDA-SOA T0 + 10 sec T0 t0 T0 + 1 T0 + 2 T0 + 3 T0 + 4 T0 + 5 T0 + 6 T0 + 7 T0 + 8 T0 + 9 Destroy Normal Ops Detection Correlation Classification Tracking Validation Assess Confirm Task Execute SENSORS COMMAND & CONTROL WEAPONS (C2) 29
  30. 30. WebSphere Service Registry and Repository Topics – Radically Simplifying Middleware  SOA and Web 2.0  XD Business/Object Grid  Real-time and Event- Driven SOA  SOA Registry and Governance 30 SOA on your terms and our expertise
  31. 31. Software WebSphere Service Registry & Repository Solution View FIND DISCOVER PUBLISH Service Service Endpoint Development Registries / Lifecycle Repositories WebSphere Service Registry and Repository Model Build Discover Assemble Change and Operational Release Efficiency and Management Mediate Bind Resilience Test Runtime Integration Manage Deploy AGILITY GOVERN MANAGE NOTIFY 31
  32. 32. Software WSRR – Development Support: Publish and Find  Publish and find services  Publish and find services capabilities  Publish and find service lifecycle stage Publish Find Describe Discover Populate Configure Search Retrieve  Publish and find service interactions Classify Organize  Publish and find service dependencies and redundancies 32
  33. 33. Software WSRR - Publish and Find Interactions Development 4 Validation Tool 1 Search WSDL 2 Create XSD …. 3 Publish Service Registry & Repository 5 Search/select Assembly/ 7 Publish Admin 6 Assemble Tool 1. Search is performed for a service or mediation or policy to (re)use 2. Development tools are used to create a new service metadata artifact 3. The new service metadata artifact is published to the Service Registry & Repository 4. Validation and conformance policies are enforced. 5. Search is performed for a service or mediation or policy to use and one is selected for use 6. The service is configured/wired and policy relationships are established. 7. The assembled service is (re) published using the Service Explorer during deployment. 33
  34. 34. Software WSRR – Enable Runtime Support  Manage dynamic and efficient access to services information by runtimes  Identify users of metadata  Notify users of changes Agility  Manage end user access to the repository Identify based on roles Notify Secure Access  Securely transmit service information Runtime 34
  35. 35. Software WSRR Runtime selection and invocation interactions Dynamic selection 1 Retrieve requester 2 3 service definition Mediation Message Message 5 Service Registry Match Retrieve candidate & Repository ESB 4 requester/ provider service provider definitions terms and terms Select provider 6 Transform & Route Message Service 1. A Message is received by an ESB. 2. The ESB invokes a selection mediation. 3. The Mediation retrieves the service description for the requested operation from the Business Service Repository. 4. The Mediation retrieves service descriptions for candidate providers 5. The Mediation executes its matching algorithm to identify the provider service that is the best fit 6. The inbound message is transformed and routed to the selected endpoint. 35
  36. 36. Software WSRR – Management Support – Manage & Monitor  Classify services into meaningful groupings based on business objectives  Manage service interactions, dependencies, relationships and redundancies  Manage policies for service usage and governance  Manage additional service metadata Manage information Policies Change  Business metrics collected Version Classify  Summarized associated business metrics Analyze Promote  Analyze services usage, history and business impact  Promote and encourage optimal services usage 36
  37. 37. Software WSRR - Operational Monitoring Interactions 1 Message Received 2 Invoke 3 Get service Service Registry logging monitoring mediation metadata Repository message message Intermediary n monitor ESB message Record desired alerts 4 Record 5 Invoke data message Service Operational Data 1. During service invocation a message is received by the ESB 2. The ESB routes the message to an intermediate logging mediation or agent 3. The monitor / mediation retrieves the monitoring policy for the message from the WSRR 4. The monitor / mediation records the operational data about the running service 5. The ESB then continues with the invocation of the service. n. Asynchronously, performance and health alerts are generated based on operational data; desired summary alerts are recorded in the Service Registry and Repository 37
  38. 38. Software WSRR – Governance Support – Change Management  Infrastructure to help organize and discover services assets, govern access and monitor service vitality  Policies for publishing, using and retiring services Govern Approve Retire  Change management Validate Conform  Manage change and versioning of services 38
  39. 39. Software WebSphere Service Registry & Repository Roadmap  The Approach:  Incremental development process • Field-based development model General and Iterative code availability Availability  Linkage across SWG for key 2H 2006 components and integration • Key technologies from Early Access Information Management and Q2 2006 Rational  GA Offering • First class consumption and  Tooling and Utilities supporting Tech Preview • Metamodel, Lifecycle, Policy exploitation across the SOA Q1 2006 Foundation Assets  Early Access with Technology Preview Q4 2005  Meta model and APIs published to enable exploitation  Basic UI  Whitepapers and Major Release Collateral to socialize Incremental Code Drops / Previews WebSphere Service Registry & Repository All plans and proposed timelines subject to change 39
  40. 40. WebSphere Service Registry and Repository THANKS – QUESTIONS ??? Radically Simplifying Middleware  SOA and Web 2.0  XD Business/Object Grid  Real-time and Event- Driven SOA  SOA Registry and Governance 40 SOA on your terms and our expertise

×