OPS-7: Building and Deploying a Highly Available Application Brian Bowman Sr. Solution Engineer

What part is the most important?

Agenda Highly Available Application (HAA) – what it means today & tomorrow Definitions Levels of Recovery

HAA – What is it? Ensuring complete application availability during the required business time (5-9’S) Meeting Business Needs Recovery Time Objective (RTO) Recovery Point Objective (RPO) Eliminating all Single Point of Failures (SPF) (While including as many TLA’s as possible in one presentation…)

Where does a Highly Available Application start? Development Application Development We will not discuss this… Deployment Packaging Installation Configuration Management Monitoring Upgrading Managing Development Deployment Management Application development & deployment timeline

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

Agenda Highly Available Application ( HAA) – what it means today & tomorrow Definitions Levels of Recovery

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) ...” (Source: http://searchdatacenter.techtarget.com/sDefinition/0,,sid80_gci761219,00.html#) 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://www.cps-corp.net/9s.htm)

It’s all about perspective…

Definitions: Complete Application Presentation Enterprise Services Business Services Common Infrastructure Data Access Data Sources Don’t tie logical structure to physical structure We don’t recommend collapsing the verticle User Interface Middleware (Application Server / Sonic™) Data (database) Common Infrastructure

Definitions: Complete Application An Example User Interface ESB Operations / HW Application Server Data Access Databases Don’t tie logical structure to physical structure We don’t recommend collapsing the verticle User Interface Middleware (Application Server / Sonic) Data (database)

Definitions: The Example Application 4 Application Configurations Hosted (single server) Client Server N-Tier SaaS Explain N-tier first (most difficult) and then move back to the more basic. I will focus on n-tier for the rest of this presentation because it is the most detailed User Interface Application Server Databases Ops / HW ESB

Logical vs. Physical Outlook Hosted (Single Server) Web Svr WS AS Client / Server Web Svr WS DB AS AS DB SaaS N-Tier

Agenda Highly Available Application ( HAA) – what it means today & tomorrow Definitions Levels of Recovery

Levels of Recovery – Planning What is the Business Requirement? Deployability Maintainability Upgradability Supportability

Levels of Recovery Level 1: Bicycle Recovery Level 2: El Camino Recovery Level 3: Race Car Recovery

$ 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:

Level 1: Technology Dependence NO RPO or RTO Have never had an incident Not using their existing resources Don’t rely completely on technology!

Level 1: Technology Choices Backup Infrastructure Hardware Software Application Configuration files Properties files Where is your recovery location?

$ $ 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:

Level 2: Choosing The Right Tool Which tool would you choose…

Level 2: Technology Choices After imaging Replication or clusters SAN solutions Recovery offsite?

$ $ $ $ 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:

Level 3: Thinking Ahead Of The Game Rick Mears 4 Time Indianapolis 500 winner 6 Times – Poll position 11 Times – Front row The right products The right tools The right people

Level 3: Personnel Choices Technical staff Required Knowledgeable Personnel are key to success Preparation Eliminating Human Error!

Level 3: Technology Choices Replication Clusters SAN solution with complete redundancy Sonic ESB / CAA

Level 3: Technology Choices: Application Availability – eliminating SPF’s Application Server Tier Client Enterprise Services Direct Connect (Load balancing) Name Server Data Tier Application Server (Site 1) TCP/IP Production (Site 1) Web Server Backup (Site 2) OpenEdge Replication User Interface Application Server (Site 2) (Load balancing) Name Server Client Reporting SQL

Level 3: Application Server Choices State* is important Application plays a critical part here! Load balancing / configuration What is the perception of the USER?

Level 3: Technology Choices: Sonic CAA Q1 Q1a Q2 Q2a

Level 3: Technology Choices: SaaS – Same Rules Apply except Web Server Application Server Tier Enterprise Services Direct Connect (Load balancing) Name Server Data Tier Application Server (Site 1) TCP/IP Production (Site 1) Client Web Server User Interface OpenEdge Replication (Load balancing) Name Server Client Backup (Site 2) Application Server (Site 2) Reporting SQL

Business Requirements 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 3 < 5 Minutes Complete Redundancy (total HA) Advanced tools required Complete cycle critical (Dev, Depl, Maint.) $ $ $ $ $ $ $

Summary Business Requirements are critical! Different Architectures Levels of recovery Business Requirements Solutions It is the complete process Development, Deployment, Maintenance

For More Information Sonic CAA OpenEdge Reference Architecture http://www.psdn.com OpenEdge Reference Architecture http://www.psdn.com/library/kbcategory.jspa?categoryID=230 Disaster Recovery Resources http://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

? Questions

Thank You