Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Optimizing Microsoft Azure Workloads

You're reading from   Optimizing Microsoft Azure Workloads Leverage the Well-Architected Framework to boost performance, scalability, and cost efficiency

Arrow left icon
Product type Paperback
Published in Aug 2023
Publisher Packt
ISBN-13 9781837632923
Length 240 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Rithin Skaria Rithin Skaria
Author Profile Icon Rithin Skaria
Rithin Skaria
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Part 1: Well-Architected Framework Fundamentals
2. Chapter 1: Planning Workloads with the Well-Architected Framework FREE CHAPTER 3. Chapter 2: Distinguishing between the Cloud Adoption Framework and Well-Architected Framework 4. Part 2: Exploring the Well-Architected Framework Pillars and Their Principles
5. Chapter 3: Implementing Cost Optimization 6. Chapter 4: Achieving Operational Excellence 7. Chapter 5: Improving Applications with Performance Efficiency 8. Chapter 6: Building Reliable Applications 9. Chapter 7: Leveraging the Security Pillar 10. Part 3: Assessment and Recommendations
11. Chapter 8: Assessment and Remediation 12. Index 13. Other Books You May Enjoy

Introducing the reliability pillar

In general, the reliability pillar focuses on the following objectives:

  • Ensuring you have a highly available architecture and avoid any single point of failure (SPOF)
  • Business continuity and disaster planning in case of data loss, downtime, or catastrophic failures
  • Testing the high availability and recovery of workloads

Building reliability in the cloud requires a shift in mindset, as we learned at the beginning of this book. For example, in traditional application development, the prime focus was on increasing the average time between system breakdowns. This metric is called the mean time between failures (MTBF). The work was primarily devoted to attempts to stop the system from failing. In the cloud, we have distributed systems and the approach will be slightly different, and we will require a shift in our mindset because of the following factors:

  • The complexity of distributed systems is high and a single failure in...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image