1 / 35

OPS-7: Building and Deploying a Highly Available Application

What part is the most important?. . . Agenda. Highly Available Application (HAA)

milla
Download Presentation

OPS-7: Building and Deploying a Highly Available Application

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. OPS-7: Building and Deploying a Highly Available Application

    2. What part is the most important?

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

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

    5. Where does a Highly Available Application start? Development Application Development We will not discuss this Deployment Packaging Installation Configuration Management Configuration Monitoring Upgrading Managing Development Application Development We will not discuss this Deployment Packaging Installation Configuration Management Configuration Monitoring Upgrading Managing

    6. 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

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

    8. Definitions: High Availability (HA)

    9. Its all about perspective

    10. Definitions: Complete Application User Interface Middleware (Application Server / Sonic) Data (database) Common Infrastructure Dont tie logical structure to physical structure We dont recommend collapsing the verticleDont tie logical structure to physical structure We dont recommend collapsing the verticle

    11. Definitions: Complete Application An Example User Interface Middleware (Application Server / Sonic) Data (database) Dont tie logical structure to physical structure We dont recommend collapsing the verticleDont tie logical structure to physical structure We dont recommend collapsing the verticle

    12. 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 detailedExplain 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

    13. Logical vs. Physical Outlook

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

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

    16. Levels of Recovery Level 1: Bicycle Recovery

    17. 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)

    18. Level 1: Technology Dependence NO RPO or RTO Have never had an incident Not using their existing resources

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

    20. 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

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

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

    23. 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)

    24. Level 3: Thinking Ahead Of The Game Rick Mears 4 Time Indianapolis 500 winner 6 Times Poll position 11 Times Front row

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

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

    27. Level 3: Technology Choices: Application Availability eliminating SPFs

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

    29. Level 3: Technology Choices: Sonic CAA

    30. Level 3: Technology Choices: SaaS Same Rules Apply except Web Server

    31. Wrap-up

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

    33. 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

More Related