330 likes | 429 Views
OPS-13: 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?.
E N D
OPS-13: Building and Deploying a Highly Available Application Brian Bowman Sr. Solution Engineer
What part is the most important? OPS-13: Building & Deploying a Highly Available Application
Agenda • Highly Available Application (HAA) – what it means today & tomorrow • Definitions • Levels of Recovery 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) OPS-13: Building & Deploying a Highly Available Application
Where does a Highly Available Application start? • Development • Deployment • Management Development Deployment Management Application development & deployment timeline OPS-13: Building & Deploying a Highly Available Application
Where does a Highly Available Application start? Development Deployment Management Application development & deployment timeline 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 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) ...” (Source: http://searchdatacenter.techtarget.com/sDefinition/0,,sid80_gci761219,00.html#) (Source: http://www.cps-corp.net/9s.htm) OPS-13: Building & Deploying a Highly Available Application
Agenda • Highly Available Application ( HAA) – what it means today & tomorrow • Definitions • Levels of Recovery OPS-13: Building & Deploying a Highly Available Application
Business Services Data Sources Definitions: Complete Application • User Interface • Middleware (Application Server / Sonic™) • Data (database) • Common Infrastructure Enterprise Services Presentation Common Infrastructure Data Access OPS-13: Building & Deploying a Highly Available Application
ESB User Interface Operations / HW Data Access Application Server Databases Definitions: Complete Application An Example • User Interface • Middleware (Application Server / Sonic) • Data (database) OPS-13: Building & Deploying a Highly Available Application
ESB User Interface Ops / HW Application Server Databases Definitions: The Example Application • 4 Application Configurations • Hosted (single server) • Client Server • N-Tier • SaaS OPS-13: Building & Deploying a Highly Available Application
WS AS Web Svr AS AS AS DB DB Web Svr AS AS AS WS WS Web Svr AS WS Logical vs. Physical Outlook Hosted (Single Server) Client / Server N-Tier SaaS OPS-13: Building & Deploying a Highly Available Application
Agenda • Highly Available Application ( HAA) – what it means today & tomorrow • Definitions • Levels of Recovery OPS-13: Building & Deploying a Highly Available Application
Levels of Recovery Level 1: Bicycle Recovery Level 2: VW Recovery Level 3: Race Car Recovery 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: 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! 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? 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: OPS-13: Building & Deploying a Highly Available Application
Level 2: Choosing The Right Tool Which tool would you choose… OPS-13: Building & Deploying a Highly Available Application
Level 2: Technology Choices • After imaging • Replication or clusters • SAN solutions • Recovery offsite? 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: 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 OPS-13: Building & Deploying a Highly Available Application
Level 3: Technology Choices • Replication • Clusters • SAN solution with complete redundancy • Sonic ESB / CAA OPS-13: Building & Deploying a Highly Available Application
Enterprise Services Client OpenEdge Replication Backup (Site 2) Application Server (Site 2) Level 3: Technology Choices: Application Availability – eliminating SPFs Application Server Tier Direct Connect Name Server (Load balancing) Data Tier Application Server (Site 1) TCP/IP Production (Site 1) Web Server User Interface Name Server (Load balancing) Client Reporting SQL OPS-13: Building & Deploying a Highly Available Application
Level 3: Technology Choices: Sonic CAA Q1 Q1a Q2 Q2a OPS-13: Building & Deploying a Highly Available Application
Level 3: Technology Choices: SaaS – Same Rules Apply except Web Server Application Server Tier Direct Connect Enterprise Services Name Server (Load balancing) Data Tier Application Server (Site 1) TCP/IP Production (Site 1) Client Web Server User Interface OpenEdge Replication Name Server (Load balancing) Client Backup (Site 2) Application Server (Site 2) Reporting SQL OPS-13: Building & Deploying a Highly Available Application
Wrap-up 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 OPS-13: Building & Deploying a Highly Available Application
For More Information • Sonic CAA 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 OPS-13: Building & Deploying a Highly Available Application
? Questions OPS-13: Building & Deploying a Highly Available Application
Thank You OPS-13: Building & Deploying a Highly Available Application