B8: Building and Deploying a Highly Available Application

David EddySenior Solution Consultant

© 2008 Progress Software Corporation2

What part is the most important?

© 2008 Progress Software Corporation3

Agenda

Highly Available Application (HAA) – what it means today & tomorrow

Definitions Levels of Recovery

© 2008 Progress Software Corporation4

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

Where does a Highly Available Application start?

Development

Development Deployment Management

Application development & deployment timeline

Deployment

Management

© 2008 Progress Software Corporation6

Where does a Highly Available Application start?

Development Deployment Management

Application development & deployment timeline

© 2008 Progress Software Corporation7

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

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 hoursFour 9's 99.99% Factories 59 minutesFive 9's 99.999% Hospitals 5 minutesSix 9's 99.9999% Banks 32 secondsSeven 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

Agenda

Highly Available Application ( HAA) – what it means today & tomorrow

Definitions Levels of Recovery

© 2008 Progress Software Corporation10

Definitions: Complete Application

User Interface Middleware (Application Server / Sonic™) Data (database) Common Infrastructure

Presentation

Business Services

Data Access

Data Sources

Com

mon Infrastructure

Enterprise Services

© 2008 Progress Software Corporation11

Definitions: Complete Application An Example

User Interface Middleware (Application Server / Sonic) Data (database)

User Interface

Application Server

Data Access

Databases

Operations / H

W

ESB

© 2008 Progress Software Corporation12

Definitions: The Example Application

4 Application Configurations• Hosted (single server)• Client Server• N-Tier• SaaS

User Interface

Application Server

Databases

Ops / H

W

ESB

© 2008 Progress Software Corporation13

Logical vs. Physical Outlook

AS

ASDB

AS

AS

Web

Sv

rW

eb

Svr

WS

WS

DB

AS

AS

Web

Sv

r

WS

AS

AS

WS

Client / Server

N-TierSaaS

Hosted (Single Server)

© 2008 Progress Software Corporation14

Agenda

Highly Available Application ( HAA) – what it means today & tomorrow

Definitions Levels of Recovery

© 2008 Progress Software Corporation15

Levels of Recovery

Level 1: Bicycle Recovery

Level 2: VW Recovery

Level 3: Race Car Recovery

© 2008 Progress Software Corporation16

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

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

Level 1: Technology Choices

Backup • Infrastructure

– Hardware– Software

• Application– Configuration files– Properties files

Where is your recovery location?

© 2008 Progress Software Corporation19

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

Level 2: Choosing The Right Tool

Which tool would you choose…

© 2008 Progress Software Corporation21

Level 2: Technology Choices

After imaging Replication or clusters SAN solutions Recovery offsite?

© 2008 Progress Software Corporation22

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

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

Level 3: Technology Choices

Replication Clusters SAN solution with complete redundancy Sonic ESB / CAA

© 2008 Progress Software Corporation25

Backup(Site 2)

OpenEdge Replication

ApplicationServer(Site 2)

Web Server

Nam

e Server(L

oad balancing)Client

ApplicationServer(Site 1)

Reporting

Nam

e Server(L

oad balancing)

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

Level 3: Technology Choices: Sonic CAA

Q2

Q1

Q2a

Q1a

© 2008 Progress Software Corporation27

Web Server

Nam

e Server(L

oad balancing)Client

ApplicationServer(Site 1)

ApplicationServer(Site 2)Reporting

Backup(Site 2)

Nam

e Server(L

oad balancing)

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

Wrap-up

Recovery Level

Business Requirements

Technology Requirements

1 < One Day Backup of complete system(s)Utilize exiting toolsDev & Depl not critical (mostly done by AP)All architectures apply

2 < 60 Minutes Duplicate HW – Available and loadedSome existing and possibly new toolsDev shared, Depl & Maint. in-houseAll architectures apply

3 < 5 Minutes Complete Redundancy (total HA)Advanced tools requiredComplete cycle critical (Dev, Depl, Maint.)All architectures apply

© 2008 Progress Software Corporation29

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

For More Information

Sonic CAAhttp://www.psdn.com

OpenEdge Reference Architecturehttp://www.psdn.com/library/kbcategory.jspa?categoryID=230

Disaster Recovery Resourceshttp://www.attanium.nethttp://www.redorbit.com/news/technology/507076/uk_emergency_preparedness_a_step_in_the_right_direction/index.htmlhttp://www.emdat.be

© 2008 Progress Software Corporation31

Questions?

© 2008 Progress Software Corporation32

Thank You

© 2008 Progress Software Corporation33