Upload
brendan-payne
View
215
Download
0
Tags:
Embed Size (px)
Citation preview
OPS-13: Building and Deploying a Highly Available Application
Brian Bowman Sr. Solution Engineer
© 2008 Progress Software Corporation2 OPS-13: Building & Deploying a Highly Available Application
What part is the most important?
© 2008 Progress Software Corporation3 OPS-13: Building & Deploying a Highly Available Application
Agenda
Highly Available Application (HAA) – what it means today & tomorrow
Definitions Levels of Recovery
© 2008 Progress Software Corporation4 OPS-13: Building & Deploying a Highly Available Application
HAA – What is it?
Ensuring the complete application is 100% available during the required business time
Meeting Business Needs• Recovery Time Objective (RTO)
• Recovery Point Objective (RPO)
Eliminating all Single Point of Failures (SPF) Including as many TLA’s as possible in one
presentation…
(TLA = Three Letter Acronyms)
© 2008 Progress Software Corporation5 OPS-13: Building & Deploying a Highly Available Application
Where does a Highly Available Application start?
Development
Development Deployment Management
Application development & deployment timeline
Deployment
Management
© 2008 Progress Software Corporation6 OPS-13: Building & Deploying a Highly Available Application
Where does a Highly Available Application start?
Development Deployment Management
Application development & deployment timeline
© 2008 Progress Software Corporation7 OPS-13: Building & Deploying a Highly Available Application
What does a HAA look like to the user?
The application is always available* Performance is always acceptable Data is NEVER lost New functionality is timely
© 2008 Progress Software Corporation8 OPS-13: Building & Deploying a Highly Available Application
Definitions: High Availability (HA)
“… high availability refers to a system or component that is continuously operational for a desirably long length of time.
Availability can be measured relative to "100% operational" or "never failing." A widely-held but difficult-to-achieve standard of availability for a system or product is known as "five 9s" (99.999 percent) ...”
Reliability OK For Expected
Outages/Year
Three 9's 99.9% Homes 9 hours
Four 9's 99.99% Factories 59 minutes
Five 9's 99.999% Hospitals 5 minutes
Six 9's 99.9999% Banks 32 seconds
Seven 9's 99.99999% Digital Markets 30 msec
(Source: http://searchdatacenter.techtarget.com/sDefinition/0,,sid80_gci761219,00.html#)
(Source: http://www.cps-corp.net/9s.htm)
© 2008 Progress Software Corporation9 OPS-13: Building & Deploying a Highly Available Application
Agenda
Highly Available Application ( HAA) – what it means today & tomorrow
Definitions Levels of Recovery
© 2008 Progress Software Corporation10 OPS-13: Building & Deploying a Highly Available Application
Definitions: Complete Application
User Interface Middleware (Application Server / Sonic™) Data (database) Common Infrastructure
PresentationPresentation
Business ServicesBusiness Services
Data AccessData Access
Data SourcesData Sources
Co
mm
on
Infrastru
cture
Co
mm
on
Infrastru
cture
Enterprise ServicesEnterprise Services
© 2008 Progress Software Corporation11 OPS-13: Building & Deploying a Highly Available Application
Definitions: Complete Application An Example
User Interface Middleware (Application Server / Sonic) Data (database)
User InterfaceUser Interface
Application ServerApplication Server
Data AccessData Access
DatabasesDatabases
Op
eration
s / HW
Op
eration
s / HW
ESBESB
© 2008 Progress Software Corporation12 OPS-13: Building & Deploying a Highly Available Application
Definitions: The Example Application
4 Application Configurations• Hosted (single server)
• Client Server
• N-Tier
• SaaS
User InterfaceUser Interface
Application ServerApplication Server
DatabasesDatabases
Op
s / HW
Op
s / HW
ESBESB
© 2008 Progress Software Corporation13 OPS-13: Building & Deploying a Highly Available Application
Logical vs. Physical Outlook
AS
ASDB
AS
AS
Web
S
vrW
eb
Svr
WS
WS
DB
AS
AS
Web
S
vr
WS
AS
AS
WS
Client / Server
N-TierSaaS
Hosted (Single Server)
© 2008 Progress Software Corporation14 OPS-13: Building & Deploying a Highly Available Application
Agenda
Highly Available Application ( HAA) – what it means today & tomorrow
Definitions Levels of Recovery
© 2008 Progress Software Corporation15 OPS-13: Building & Deploying a Highly Available Application
Levels of Recovery
Level 1: Bicycle Recovery
Level 2: VW Recovery
Level 3: Race Car Recovery
© 2008 Progress Software Corporation16 OPS-13: Building & Deploying a Highly Available Application
Level 1: Business Case
Easiest environment to work in RTO and RPO < 1 day Typically
• Host-based
• Client-Server
Development left to the Application Partner (usually)
Cost Scale:
© 2008 Progress Software Corporation17 OPS-13: Building & Deploying a Highly Available Application
Level 1: Technology Dependence
NO RPO or RTO Have never had an incident Not using their existing resources
Don’t rely completely on technology!
© 2008 Progress Software Corporation18 OPS-13: Building & Deploying a Highly Available Application
Level 1: Technology Choices
Backup • Infrastructure
– Hardware– Software
• Application– Configuration files– Properties files
Where is your recovery location?
© 2008 Progress Software Corporation19 OPS-13: Building & Deploying a Highly Available Application
Level 2: Business case
RTO and RPO < 60 minutes Typically
• Host-based
• Client-server
• N-tier
Development shared between AP and User Deployment shared as well
Cost Scale:
© 2008 Progress Software Corporation20 OPS-13: Building & Deploying a Highly Available Application
Level 2: Choosing The Right Tool
Which tool would you choose…
© 2008 Progress Software Corporation21 OPS-13: Building & Deploying a Highly Available Application
Level 2: Technology Choices
After imaging Replication or clusters SAN solutions Recovery offsite?
© 2008 Progress Software Corporation22 OPS-13: Building & Deploying a Highly Available Application
Level 3: Business Case
RTO and RPO < 5 minutes Typically
• All Deployment Models (Host-based, Client-server, N-tier, SaaS)
Real-time and near real-time Large development organization Deployment important (and difficult)
Cost Scale:
© 2008 Progress Software Corporation23 OPS-13: Building & Deploying a Highly Available Application
Level 3: Thinking Ahead Of The Game
Rick Mears • 4 Time Indianapolis 500 winner
• 6 Times – Poll position
• 11 Times – Front row
© 2008 Progress Software Corporation24 OPS-13: Building & Deploying a Highly Available Application
Level 3: Technology Choices
Replication Clusters SAN solution with complete redundancy Sonic ESB / CAA
© 2008 Progress Software Corporation25 OPS-13: Building & Deploying a Highly Available Application
Backup(Site 2)
OpenEdge Replication
ApplicationServer(Site 2)
Web Server
Nam
e Server
(Load b
alancin
g)Client
ApplicationServer(Site 1)
Reporting
Nam
e Server
(Load b
alancin
g)
Production(Site 1)
User Interface
Application Server Tier
Data Tier
Direct Connect
TCP/IP
SQL
Level 3: Technology Choices: Application Availability – eliminating SPFs
Client
EnterpriseServices
© 2008 Progress Software Corporation26 OPS-13: Building & Deploying a Highly Available Application
Level 3: Technology Choices: Sonic CAA
Q2
Q1
Q2a
Q1a
© 2008 Progress Software Corporation27 OPS-13: Building & Deploying a Highly Available Application
Web Server
Nam
e Server
(Load b
alancin
g)Client
ApplicationServer(Site 1)
ApplicationServer(Site 2)Reporting
Backup(Site 2)
Nam
e Server
(Load b
alancin
g)
Production(Site 1)
User Interface
Application Server Tier
Data Tier
Direct Connect
TCP/IP
OpenEdge Replication
SQL
Level 3: Technology Choices: SaaS – Same Rules Apply except Web Server
Client
EnterpriseServices
© 2008 Progress Software Corporation28 OPS-13: Building & Deploying a Highly Available Application
Wrap-up
Recovery Level
Business Requirements
Technology Requirements
1 < One Day Backup of complete system(s)
Utilize exiting tools
Dev & Depl not critical (mostly done by AP)
All architectures apply
2 < 60 Minutes Duplicate HW – Available and loaded
Some existing and possibly new tools
Dev shared, Depl & Maint. in-house
All architectures apply
3 < 5 Minutes Complete Redundancy (total HA)
Advanced tools required
Complete cycle critical (Dev, Depl, Maint.)
All architectures apply
© 2008 Progress Software Corporation29 OPS-13: Building & Deploying a Highly Available Application
Summary
Business Requirements are critical! Different
• Architectures
• Levels of recovery
• Business Requirements
• Solutions
It is the complete process• Development, Deployment, Maintenance
© 2008 Progress Software Corporation30 OPS-13: Building & Deploying a Highly Available Application
For More Information
Sonic CAAhttp://www.psdn.com
OpenEdge Reference Architecturehttp://www.psdn.com/library/kbcategory.jspa?categoryID=230
Disaster Recovery Resourceshttp://www.attanium.net
http://www.redorbit.com/news/technology/507076/uk_emergency_preparedness_a_step_in_the_right_direction/index.html
http://www.emdat.be
© 2008 Progress Software Corporation31 OPS-13: Building & Deploying a Highly Available Application
Questions?
© 2008 Progress Software Corporation32 OPS-13: Building & Deploying a Highly Available Application
Thank You
© 2008 Progress Software Corporation33 OPS-13: Building & Deploying a Highly Available Application