Cyberstudy
PDF p.167 In progress

Cloud Architecture Features

Open PDF at p.167 33 flashcards

Summary

PDF p.167

Public cloud infrastructure offers features like data replication, auto-scaling, disaster recovery, and SLAs to ensure high uptime and minimal downtime. These features, along with considerations for cost, scalability, resilience, ease of deployment, and recovery, make cloud services highly reliable and efficient.

In plain words

Supplementary — not from your PDF

Public clouds offer replication, auto-scaling, disaster recovery services and SLAs with credits if uptime isn't met. When evaluating them, look at cost (consumption or subscription, CapEx shifting to OpEx), vertical vs horizontal scaling, resilience, ease of deployment and recovery, SLAs and ISAs, power efficiency (PUE), and compute and networking features.

Detailed explanation

PDF p.167
  • Data Replication and Redundancy
    • Definition: Replicating data across multiple servers and datacenters to ensure availability during failures.
    • Benefits: Ensures data availability and reliability.
  • Auto-Scaling
    • Definition: Automatically scales resources based on demand.
    • Benefits: Handles high traffic volumes without downtime.
  • Disaster Recovery Services
    • Definition: Tools and services to detect and respond to issues impacting availability.
    • Benefits: Proactive issue detection and response.
  • Service-Level Agreements (SLAs)
    • Definition: Guarantees a certain level of uptime and availability.
    • Benefits: Provides credits or refunds if commitments are not met.
  • Considerations
    • Cost
      • Models: Consumption-based or subscription-based.
      • CapEx to OpEx: Shift from capital expenses to operational expenses.
      • Optimization: Importance of optimizing resources to avoid high recurring costs.
    • Scalability
      • Vertical Scaling: Adding capacity to existing resources.
      • Horizontal Scaling: Adding more instances to work in parallel.
    • Resilience
      • Redundancy: Use of redundant hardware and fault tolerance.
      • Data Replication: Ensures data availability across multiple servers and datacenters.
    • Ease of Deployment
      • Automation: Reduces manual intervention.
      • Standardization: Simplifies deployment with standardized configurations.
      • Portability: Ensures applications can move between different cloud infrastructures.
    • Ease of Recovery
      • Backup and Restore: Automated backups and quick data restoration.
      • Redundant Architectures: Distributes data across multiple datacenters.
      • Disaster Recovery Services: Replicates environments in different regions.
    • SLA and ISA
      • SLAs: Define expected service levels and commitments.
      • ISAs: Establish security requirements and responsibilities.
    • Power
      • Energy Efficiency: Deploying energy-efficient hardware and optimizing cooling systems.
      • Redundant Power Infrastructure: Ensures high availability with multiple power feeds and backup systems.
      • Power Usage Effectiveness (PUE): Measures datacenter energy efficiency.
    • Compute
      • Capabilities: Elasticity, resource pooling, orchestration, automation, serverless computing.
      • Networking: Secure communication, traffic routing, load balancing, private and public connectivity.
      • Content Delivery Networks (CDNs): Efficient content delivery and high availability.

Important terms

taken from the text above
Data Replication and Redundancy
Replicating data across multiple servers and datacenters to ensure availability during failures.
Auto-Scaling
Automatically scales resources based on demand.
Disaster Recovery Services
Tools and services to detect and respond to issues impacting availability.
Service-Level Agreements (SLAs)
Guarantees a certain level of uptime and availability.
Models
Consumption-based or subscription-based.
CapEx to OpEx
Shift from capital expenses to operational expenses.
Optimization
Importance of optimizing resources to avoid high recurring costs.
Vertical Scaling
Adding capacity to existing resources.
Horizontal Scaling
Adding more instances to work in parallel.
Redundancy
Use of redundant hardware and fault tolerance.
Data Replication
Ensures data availability across multiple servers and datacenters.
Automation
Reduces manual intervention.
Standardization
Simplifies deployment with standardized configurations.
Portability
Ensures applications can move between different cloud infrastructures.
Backup and Restore
Automated backups and quick data restoration.
Redundant Architectures
Distributes data across multiple datacenters.
SLAs
Define expected service levels and commitments.
ISAs
Establish security requirements and responsibilities.
Energy Efficiency
Deploying energy-efficient hardware and optimizing cooling systems.
Redundant Power Infrastructure
Ensures high availability with multiple power feeds and backup systems.
Power Usage Effectiveness (PUE)
Measures datacenter energy efficiency.
Capabilities
Elasticity, resource pooling, orchestration, automation, serverless computing.
Networking
Secure communication, traffic routing, load balancing, private and public connectivity.
Content Delivery Networks (CDNs)
Efficient content delivery and high availability.
SLAs Service-Level Agreements PUE Power Usage Effectiveness CDNs Content Delivery Networks

Examples & real-world scenarios

Supplementary — not from your PDF
  • Horizontal scaling: adding more web server instances.
  • Vertical scaling: giving one database server more CPU and RAM.
  • An ISA setting out security responsibilities between two connected organizations.

Scenario

A company moves to the cloud expecting savings but gets a huge monthly bill from idle resources. Cost optimization, such as right-sizing and shutting down unused instances, is part of cloud architecture.

Common mistakes

Supplementary — not from your PDF
  • Mixing up vertical (bigger) and horizontal (more) scaling.
  • Mixing up SLA (service levels) and ISA (security requirements for an interconnection).

Practical skills

Supplementary — not from your PDF
  • Compare cloud offerings using the guide's considerations list.

What I should remember

Key Points PDF p.167
  • Data Replication: Ensures data availability.
  • Auto-Scaling: Handles high traffic volumes.
  • Disaster Recovery: Proactive issue detection.
  • SLAs: Guarantees uptime and availability.
  • Cost: Shift from CapEx to OpEx.
  • Scalability: Vertical and horizontal scaling.
  • Resilience: Redundant hardware and data replication.
  • Ease of Deployment: Automation, standardization, portability.
  • Ease of Recovery: Backup, restore, redundant architectures.
  • SLA and ISA: Service levels and security requirements.
  • Power: Energy efficiency and redundant infrastructure.
  • Compute: Elasticity, resource pooling, networking, CDNs.