rogue wave presentation

Achieving High Performance in a Service Oriented Architecture (SOA)

Patrick Leonard

Vice President Product Development

Rogue Wave Software

2 Copyright © Rogue Wave Software, 2005

Agenda

1. Business Drivers for SOA2. Performance Challenges for SOA3. Practical Approaches4. Results


Rogue Wave Software provides reusable software components and services to professional developers enabling the creation of enterprise-class applications.

• Wall Street-Proven Quality – Most proven, trusted foundation for building enterprise C++ applications– Rogue Wave® components are used by each of New York's 15 largest

investment companies to power mission-critical business systems**

• Mind Bending Performance– Rigorous testing performed by the Carnegie Mellon Software Engineering

Institute shows Rogue Wave® tools outperform the competition*

• Unparalleled Flexibility– 50 platforms, 14 database combinations – in each release!– Interoperable with XML, Web services, and major message busses– Source code included with many products

Rogue Wave SoftwareServing the Professional Developer for 15 years

*Hari, L., Midha, A., Singh, R. (2005). “Rapid Integration Tools for Rapid Application Development.” Carnegie Mellon Software Engineering Institute**Crain’s New York Business, Book of Lists 2005


Common Business Goals for SOA

• Growth• M&A, new products and markets

• Agility • Outmaneuver competition, dazzle customers

• Reuse / Productivity• Cost and time savings

Business requirements are driving SOA adoption


2x

10x

EVEN

50x

Increase inData Dependency

and Volume

Performance Demand

Business Growth

SOA

THE CHALLENGE


Applications

• Performance• Low-latency applications• High throughput / volume• Batch to Real-time

• Flexibility / Agility• Migration from legacy applications• Combine multiple disparate systems• Application abstraction• Consistent data services layer


“For SOA implementations with large numbers of users, Services, or traffic, however, maintaining the necessary performance levels presents a substantial challenge…”

– Jason Bloomberg, Zapthinkhttp://www.zapthink.com/report.html?id=ZAPFLASH-2006920

http://www.zapthink.com/report.html?id=ZAPFLASH-2006920




Does SOA hurt Performance?

It doesn’t have to, but…

Common performance challenges• Tightly coupled Loosely coupled• XML use (10-15x increase in doc

size)• Central bus architectures• Asynchronous communication

How do you combine the agility of SOA with High Performance?


High Performance: 2 Dimensions

• Scale out – “Scalability”• The total throughput of the

system• “Can I add more servers to

help?”

• Scale up – “Performance”• The time a single message

take to flow through• “How quickly does the system

respond to a request?”


Combining High Performance and SOA – Practical Approaches

Scalability:• Do more than one thing at a time

– Parallel with Order guarantee for massive scale out (“Software Pipelines” )

• Distributed Data– Put the data close to where it’s needed

(“Distributed SDO”)


Software Pipelines

• Pipelines is a paradigm of software development and new approach to architecture

• Pipelines is a technology and methodology that exploits parallel processing from a software perspective…

• Software Pipelines allow for…– Finite, granular control for

execution of tasks at local level– Re-shuffling of tasks within a

process, without rewriting code– Analysis of data content to

decipher process inefficiencies and areas for segmentation for parallel processing

– Exploit multi-core architectures


Combining High Performance and SOA – Practical Approaches

Performance:• Fast processing of XML

– Fast parsing, avoid parsing, fast access, fast modification, distributed

• Low latency environment– Use an optimized infrastructure - native code

speeds things along

• Native services and Web services– There’s no “W” in SOA


Services – Web and Native


Results

• Can reduce memory footprint by 1/2 - 2/3 compared with traditional approaches*

• Parsing speed can be 2-4x*• “Pipelines” can bring 10x throughput gain**• Latency in the range of 15ms or less

* Based on internal benchmark testing with several commonly used products

** Compared with the same application running in serial

YMMV, but the answer is “Yes, you can combine SOA and High Performance.”


Rogue Wave® Hydra

Questions?

[email protected]

mailto:[email protected]


Financial ServicesUse case – Financial POC

The Need: Scalability and flexibility in processing equity trades

Customer: Business tripled in last 3 years, expected to triple in the next three. Need flexibility to support new types and

strategies for trades.

Process: Existing customers, evaluated several competitors, selected RW for POC

Why RW: High-performance C++ framework, peer-to-peer distribution, Java/C++ interoperability


High Performance – Traditional Approaches

• Hardware:– CPU performance improvements– Dual / Multi-Core CPUs

• SMP & Clustering• Network Routing – ‘Round Robin’• Grid Computing


SCA – Service Component Architecture

• Next major enterprise architecture spec for SOA– Comparable to Microsoft WCF

• Hydra is the first product to support SCA concepts with high performance– Rogue Wave has been planning for SCA-

compatible capabilities for some time• Hydra SCA will complement and improve

runtimes from major vendors:– Pipelines for ultra-scalability and parallelization– Cross-language Service Data Objects (SDO)

with integrated Java/C++ memory model


• “Rogue Wave Software… has carved out a new top-end niche in SOA.” – Dana Gardner, Interarbor Solutions

http://blogs.zdnet.com/Gardner/index.php?p=2270

• “SCA Is a Winner in the Quest to Establish a Common Notation for SOA” – Jess Thompson, VP, Gartner Group

Industry Leadership

http://blogs.zdnet.com/Gardner/index.php?p=2270


PARALLEL PROCESSING FOR BUSINESS

Compute-Grid Real-World


TRADING SERVICE – SINGLE PIPELINE


TRADING SERVICE – THREE PIPELINES


TRADING SERVICE – “n” PIPELINES


Introducing Rogue Wave® Hydra

The next-generation SOA product suite with a focus on performance and scalability, meeting the most challenging demands of growth-oriented enterprises.


HydraAgent…


Eclipse-based tools…


• Service Data Objects– An IBM/BEA SOA specification for accessing different

data formats in a consistent manner– Now supported in version 2.0 by Oracle, SAP, Iona,

Siebel, Sybase as part of Service Component Architect (SCA)

– XML style API in both Java and C++

• HydraSDO implementation– Lightweight and distributed for high-performance– Optimized for Shared Memory Access (SMA) between

Java/C++

Introducing HydraSDO™


• Data Access Service (DAS) for parsing data and populating a DataGraph consisting of DataObjects and a Change Summary

• Application retrieves DataGraph using the SDO API, modifies the data graph as required, and applies any changes back through DAS

• The data is parsed just once, after which it can be navigated using XPath expressions

SDO in Action


Java and C++ APIs

Customer Examples


ISV / OEM / SI / ASP

• Sell fairly complex products– BMC, BO, Avaya, hardware solutions

• Focus on immediate value– More throughput = sell to big accounts– Easy to embed, less complexity– Available source code– Controlled costs up front and ongoing

• Significant future marketing


ISV / OEM / SI / ASP Use case – Customer Relationship vendor

The Need: Customer data in batch nightly, they are out of batch window, overall IT cost is 15% of revenue and 40% is Oracle license

Customer: Reduce Oracle dependency, improve performance 10x to 20x, increase batch to grow business and increase revenue

Process: Executive champion with former relationship with Quovadx team leveraged

Why RW: Scalability, flexibility, cost-effectiveness – practical approach


Healthcare

• Providers & Payers have new IT/ business requirements for interoperability– Heterogeneous environment with multiple

core systems and applications

• Growing trend toward consumer-driven healthcare– Millions of healthcare consumers, billions of

transactions, highly data-intensive

• Vendor lock-in is high


HealthcareUse case – Healthcare POC

The Need: Many 3rd party technologies & components, need flexibility to accommodate dynamic business rules, existing preferred application is handling only 5% (consumer driven healthcare) of their business volume today

Customer : Claims volume expected to grow by 20 to 40 times in the next 24 months

Process: Existing QUOVADX relationship, existing vendor presented proprietary offering

Why RW: Avoid vendor lock-in due to multiple technology support, parallel processing performance capabilities, business process flexibility

rogue wave presentation

Documents

years rogue wave software

rogue wave tools

rogue wave softwareserving

software pipelinespipelines

reusable software components

high performance

new products

soa implementations