Embed Size (px)
DESCRIPTION
Citation preview
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Building Large Scaleable Client/Server Solutions!
David M. Walker
Technical Leader
Professional Services
Sequent Computer Systems
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Agenda!
Introduction
Requirements
The Large Scaleable Server
Networking
Backup & Recovery
Conclusion
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Introduction!
Databases in excess of 10Gb, normally 50Gb+
OLTP with 7 by 24 hour requirement
1000’s of enrolled users
100’s of concurrent users
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Requirements!
Architecture Led Design
Modular
Resilient
Scaleable
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
The Large Scaleable Server!
Database Server
(multi node cluster)
Batch/Print Server
(two node cluster)
Client Networks
Application
Server
(free standing)
Server Network
(FDDI)
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
The Database Server!
Traditional ‘Server’
Only Oracle RDBMS running
SQL * Net connections over FDDI
Resilience
!! Use OPS for fail over
!! Use disk mirroring
Scaleability
!! Use OPS for ‘out of box’ growth
–!Modular Application Design Useful
!! Use disk striping
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Application Server!
Two Type
!! ‘Host’ Based
!! ‘Client’ Based
Clone machines provide resilience and scaleability
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Host Based Application Server!
User logs onto server via telnet
User interface run on Application Server
‘Thin’ Clients
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Client Based Application Server!
Server acts only as file server
User Interface run on Local PC
‘Thick’ Clients
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Batch Server!
Manages batch queues
May run batch jobs on Application Server or locally
Standardize interface so all products can use it
Resilience options
!! Use database to hold queue
!! Cluster aware batch manager
!! Use fail over file systems to move queue
Scaleability
!! Design manager to run programs where resource is
available (e.g. Application or Batch Server)
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Print Server!
Manages system output
Resilience options
!! Use database to hold queue
!! Cluster aware print manager
!! Use fail over file systems to move queues
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Print Server (continued)!
Options
!! Distributed across application servers
–! Large number of complex queues to manage
–!Needs intelligent printers
–! Interferes with application server work
–!Not very scaleable or resilient
!! Centralized printer server
–! Single point queue management
–!Output must be sent to server for queuing which
increases network traffic
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Print Server (continued)!
Options (continued)
!! Hybrid print servers
–!Central Queue Manager (CQM)
–! Local queues on Application Servers address by CQM
only
–! Large number of simple queues to manage
–!No large network file transfers
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Networks!
Server Network (FDDI)
!! SQL * Net Traffic between Application Server and Database
Server
!! Batch and print requests
Client Networks
!! Users connections to Application Servers
System Administration Network
!! System Administrators
!! Database Administrators
!! SNMP MIBs for monitoring
Clusters Networks
!! Low Latency Interconnects for Lock Traffic
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Backup and Recovery!
PLAN & TEST FOR RECOVERY !
Database Server
!! Use ‘Hot’ & ‘Cold’ backups
!! Use OPBRU where available
!! Use resilient media (3480 or 3490)
!! Use low capacity media with tape managers
Application, Batch and Print Servers
!! Use standard Configurations
!! Keep transient files of separate file systems from static
code
Building Large Scaleable Client/Server Solutions - David M. Walker 13:45
Conclusion!
Large Client/Solutions are possible but not easy
Have an architecture and build in a modular fashion
Look for weaknesses in resilience and scaleability
Partner with your vendors - you will need their help
