Download presentation
Presentation is loading. Please wait.
Published byShawn Washington Modified over 9 years ago
2
PowerTier EJB in High-Performance Applications John Killoran European Technical Services Manager Persistence Software
3
Agenda l The need for a new approach l PowerTier architecture & benefits l Implementation example l Q & A
4
The need for a new approach l Time-to-Market – Developer productivity – Complexity – Skills shortage – Costs l Performance & Scalability – Good response times – Huge scalability – Realistic hardware platform – Costs
5
PowerTier Productivity l True Object-Oriented approach – Manage complexity through modelling CASE tool integrations CASE tool integrations – Easier maintenance l Code Generation – Code generation & re-generation – Container managed persistence l Increased Quality – Reduced testing
6
Code Generation Object Model Server Container EJB Bean/ C ++ Object EJB Bean/ C ++ Object Object Builder PowerTier provides much of the required application and infrastructure code automatically Servlet Engine JSP PowerPage Builder EJB Bean/ C ++ Object EJB Bean/ C ++ Object Database Schema Automating Development
7
Source: Reuters Equities benchmark Time required to implement auction benchmark 2 weeks - 426 lines of code PowerTier Automated Coding Competing Approach Hand Coding 1 day - 20 lines of code Developer Efficiency
8
Scalability Bottleneck Growing numbers of usersGrowing numbers of users Increasing need for common data & processesIncreasing need for common data & processes Real-time response challengeReal-time response challenge The Need for a New Architecture Transactions and Documents
9
The Need for a New Architecture 100%Write100%Read OLTP Client/Server eCommerce
10
Persistence Content Cache Web Server Java Servlet Engine Application Server Real-Time Server Synchronisation Object Caching The Persistence J2EE Solution
11
Dynamai Apache ServletMill PowerSync PowerTier Transactional Application Server The Persistence J2EE Solution
12
Performance & Scalability l Performance & scalability are similar - but not the same! l Performance – – That which affects the response time of your system to requests from a single user at a time l Scalability – – The ability of your system to maintain the same response times as the number of users increase
13
Data Sources Servlet Engines & App Servers Servlet Engine EJB Server cache Servlet Engine EJB Server cache Servlet Engine EJB Server cache Load Balance Cache Sync Web Servers Web Server Web Server Web Server DynamaiCaches cache Database Legacy Systems ERP Applications Scalable N-Tier Architecture
14
Component Architecture PowerTier EJB Server PowerTier Servlet Engine PSE plug-in PSE plug-in Apache Web Server Dynamai Dynamic Web Cache HTTP HTTP or PSE native protocol Native DB protocol or JDBC Database Dynamai protects against peak loads even for dynamically generated web pages. PSE plug-in provides load balancing and transparent failover support for SE requests Servlet Engine and EJB Server run in the same process to reduce communication lag Efficient native connections to databases
15
Source: Morgan Stanley OO-Fin Benchmark Customer Benchmark
16
Multi-User Scalability Number of Simultaneous Requests Access Time Per Request (ms) Source: Morgan Stanley OO-Fin Benchmark PowerTier is orders of magnitude more scalable than a stateless application server = PowerTier Legend = Stateless Server 0 100 200 300 400 500 1002501
17
Web Transactions Source: Persistence caching benchmark Read transactions per second 58,000 TPS 308 TPS PowerTier Shared Caching Competing Approach using standard JDBC drivers
18
Sample Product Features l Optimistic locking l Transactional multi-threading
19
Optimistic Locking l Automated feature of PowerTier l Object Versioning l Optimistic Control – Version number (Integer, Long) – Timestamp (datetime) l Automated runtime behaviour – Checking on commit – Increment
20
Optimistic Locking Server A Server B 1 1 1 1 2 1 2
21
Databa se Tx Cache Shared Cache Tx Cache Object Cache Transactional Multithreading Power Sync
22
Instinet Global Fixed Income Trading System
23
Business Background l Instinet Corporation – Reuters subsidiary since 1987 – Founded 1969 – Brokerage services in 30+ countries – Global customer base l Strategy – Innovative application of advanced IT – Agency broker - therefore neutral l Fixed Income Trading – Fixed income securities; esp. Euro bonds – New market for Instinet
24
Business Requirements l Global trading l Fair play – “Level playing field” – Anonymous trades l Time to market – Ready in 9 months l Future proof l Market share – Dominant market share through superior technology
25
Technical Requirements l Performance – ~1000 transactions/sec l Developer productivity – Nine month development cycle l Highly distributed – Service 1000s clients distributed globally l Flexible architecture – Future proofing l Availability – Very high availability l Security – Anonymity & restricted access
26
Core Ring Remote Ring DB Core Gateway GW Remote Site (Java clients) GW App GW App Systems Architecture GW App
27
London DB Core GW App DB Core New York Global Systems Architecture GW App GW App GW App GW App GW App
28
Architectural Features l Based on Async Messaging – Load balancing l Cache Synchronisation – Certified messaging – Remote caches l Hierarchical Caches – PowerTier “OpenAgent” – EJB Entity Beans Permanent storage is transparent to the application logic Permanent storage is transparent to the application logic
29
Q & A
Similar presentations
© 2024 SlidePlayer.com Inc.
All rights reserved.