1 / 11

Architecting no downtime databases

This presentation focuses on designing databases that ensure high availability for online e-commerce applications, crucial for systems that must operate 24/7 without downtime. Leveraging over 7 years of experience as a Development DBA for a Fortune 500 company in Austin, Texas, we will explore three high-availability options and discuss their pros and cons, providing a foundational understanding. The session will also highlight how SQL Server Denali simplifies high availability with features like multiple read-only and synchronous replicas.

hamish-bryan
Télécharger la présentation

Architecting no downtime databases

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. Architecting no downtime databases

  2. Introduction • Development DBA for Fortune 500 company in Austin, Texas. • Responsible for database architecture of highly transactional online e-commerce applications. • Over 7 years experience working with SQL Server and Oracle RDBMS systems. Architecting no downtime databases

  3. Agenda • We will see 3 high availability options. • We will discuss the pros and cons of these options. • This will not be a comprehensive list of options but provides a foundation of understanding. • We will see how Denali will make high availability easier. Architecting no downtime databases

  4. Problem Statement • You have an online e-commerce system that must be available 24/7 with no downtime. • Database must stay online while patching is occurring. • Database must be able to sustain failure of a datacenter with no downtime. • Application is largely read-only but must have write access available. • Priority is availability of read-only traffic. Architecting no downtime databases

  5. Application Caching Architecting no downtime databases

  6. Cluster and Database Mirroring Solution Architecting no downtime databases

  7. Replication Solution Architecting no downtime databases

  8. Hybrid Solution Architecting no downtime databases

  9. Denali Features • Multiple read-only replicas. • Multiple synchronous replicas. Architecting no downtime databases

  10. Questions? Architecting no downtime databases

  11. Thank you for attending • Please feel free to contact me at russ@johnsonville.net if you more questions. • Please take the time to rate me as a speaker and provide me feedback: http://speakerrate.com/russjohnson Architecting no downtime databases

More Related