Anuj Shrivastav’s Post

View profile for Anuj Shrivastav, graphic

PySpark | Hadoop | SQL | Python | Big Data | Azure | Databricks | Azure Data Factory | Data Lake Storage (ADLS) Gen2 | Hive | ETL | Machine Learning Engineer @ Tata Consultancy Services | Ex-Oracle | 🔥 Data Enthusiast

💡 Understanding Azure: Availability Set vs Availability Zone 💡 In Azure, ensuring high availability for your virtual machines (VMs) is critical. Here’s a quick breakdown of Availability Sets and Availability Zones, and how they protect your applications from failures: 🔹 Availability Set: Protects your VMs from hardware failures within the same datacenter. It uses: Fault Domains: Physical groupings (e.g., racks with servers) that safeguard against power or hardware failures. Update Domains: Logical groupings to minimize disruption during maintenance or system updates. Example: With 6 fault domains and 12 update domains, deploying VMs across these ensures minimal downtime due to faults or updates. 🔹 Availability Zone: Takes protection a step further by shielding from datacenter-level failures. When you distribute your VMs across multiple zones, even if one zone experiences a failure, your app stays up in another. 💻 Uptime SLAs:(https://uptime.is/) Single VM: 99.9% (8 hours 45 minutes of downtime per year) Two or more VMs in an Availability Set: 99.95% (4 hours 22 minutes downtime) Two or more VMs in different Availability Zones: 99.99% (52 minutes downtime) Maximizing uptime and reliability is crucial in cloud architecture. Excited to keep learning more about Azure's robust infrastructure! #Azure #CloudComputing #HighAvailability #AvailabilitySet #AvailabilityZone #TechLearning #CloudInfrastructure

To view or add a comment, sign in

Explore topics