High Volume Web API Management with WSO2 ESB lean enterprise middleware

29 Pages·2011·1.23 MB·English

lean enterprise middleware
High Volume Web API Management
with WSO2 ESB
Paul Fremantle, CTO and Co-Founder
Hiranya Jayathilaka, Associate Technical Lead
© WSO2 2011. Not for redistribution.
WSO2 Offerings
• WSO2 Carbon
– On premise product platform
– Consistent products sharing the same OSGi core
• WSO2 Stratos
– A “Cloud-Enabled Application Platform” (CEAP)
– Multi-tenant, Elastic, Metered/Billed deployment
– An extension of the Carbon platform
– Same SVN code tree
• WSO2 StratosLive
– http://cloud.wso2.com
– A running Platform-as-a-Service (PaaS)
– An instance of Stratos
© WSO2 2011
ForresterWaveTM ESB Q2 2011 - Leader
WSO2 ESB 4.0
• Click to edit Master text styles
– Second level
– Third level
• Fourth level
– Fifth level
© WSO2 2011
WSO2 ESB Features
• The WSO2 Enterprise Service Bus offers:
– Easy configuration through an intuitive graphical
interface
– Lean, high-performance design conserves resources
through maximum efficiency.
– Built on the WSO2 Carbon OSGi platform: adding new
capabilities as you need them is a snap.
– Integrates with your existing systems, with support for
EDI, CSV, Files, FIX, HL7, SAP, JMS, etc
• Asynchronous architecture supports very high loads
with fixed resources
• Routing, mediation and transformation are
modular, extensible but provide most use-cases
simply by sequencing built-in mediators
• Full support for SOAP/WS-* and REST
© WSO2 2011
Key Features for High Volume Web API
• Load Balancing and Failover built-in
– Pluggable models can include affinity based LB
• Full REST Support (XML and JSON)
– Especially used in Mobile environments
– Can bridge into SOAP or other enterprise systems
• Message Relay Mode and Relay Transport
– Excellent performance for 100% streaming
• Priority Execution, Cache and Throttling
– Manage workloads within the ESB as well as throttle
backend
– Cache content locally if appropriate
• Service Chaining
– Asynchronous lightweight orchestration
© WSO2 2011
eBay Case Study – High Volume
• Requirements:
– “The solutions we were using no longer met our needs, so we considered
whether to build a new internal system or to adopt third-party technology”,
Abhinav Kumar, eBay
– Needed enhanced service mediation and orchestration capabilities
– Scalability and performance to sustain increasing loads
• Evaluation:
– eBay evaluated several industry leading hardware and software ESB
solutions, looking at open source, commercially licensed ESBs and hardware
– Test production during 2009 holiday season proved that our system was rock
solid
– 1m messages/day with zero downtime, zero memory growth
• Results
– Shared-nothing architecture on RedHat Linux on x86 hardware
– Currently running at more than 1 billion messages / day
– Low resource utilization and flat memory usage
• The benefits
– “Using the WSO2 ESBs, we've been able to provide customers and partners
with the quality experience they expect on eBay, even as our global
customer base has grown,” Abhinav Kumar
© WSO2 2011
Memory Usage at eBay
• Click to edit Master text styles
– Second level
– Third level
• Fourth level
– Fifth level
© WSO2 2011
Deployment
© WSO2 2011
Configuring for High Volume
• Operating System
• JVM
• ESB
• Management
© WSO2 2011