|
|
Transaction Oriented Design
London, March 8th-11th
Objective:
- Designing reliable, scalable, enterprise applications is hard. There is no perfect textbook solution, just a series of compromises that balance time, features and cost. This course focuses on the ambiguities of complex transactional systems and, using real world examples from different industries and applications, prepares attendees to navigate the maze.
Prerequisites:
- Familiarity with J2EE technologies including Servlets, EJBs and Message Queues
Programming experience with J2EE is useful but not required
Understanding of networking components such as firewalls, load-balancers, directories, and databases
This content is aimed at enterprise architects and senior developers responsible for the design of mission critical systems.
|
|
Presenters:
Dain Sundstrom
Jeremy Boynes
Where:
Renaissance Chancery Court
252 High Holborn
London WC1V 7EN, United Kingdom
When:
March 8-11, 2004
9:00 AM - 5:00 PM
Cost:
£1995 for early registration
£2200
For more information or to sign up, please contact
|
Syllabus:
- Day 1 -- What it's really about
- Clarifying the Key Issues: Scalability and Reliability
- The Role of Open Source: Managing TCO
- Defining the Business: Identifying Business Transactions
- Concurrency: Managing Isolation Issues
- Day 2 -- The Presentation Layer
- Processing Outside the Transaction
- MVC Designs: Struts, JSF and other frameworks
- Effective Security: The Three A's
- Day 3 -- The Business Layer
- To EJB or Not To EJB ...
- EJB Design Patterns
- Persistence: BMP, CMP, JDO, OJB, Hibernate and Alternatives
- Messaging: Leveraging JMS
- Day 4 -- Production Environments
- Clustering: Making 1 + 1 nearly 2
- Change Management
- Case Study: How far can $100,000 go?
Map to Hotel:
|
|
|
|
© 2003 Core Developers Network Ltd
"Core Developers Network", the stylized apple logo and "Core Associates" are trademarks of Core Developers Network Ltd. All other trademarks are held by their respective owners. Core Developers Network Ltd is not affiliated with any of the respective trademark owners.
|
|