Cloud Weekly

Cloud Weekly Substack focuses on educating Cloud Engineers by discussing best practices, architectural decisions, and technologies in cloud computing and engineering. It covers serverless architecture, disaster recovery, DevOps principles, fault tolerance, performance optimization, and the importance of monitoring and autoscaling in cloud environments.

Cloud Computing Serverless Architecture Disaster Recovery Database Scalability Fault Tolerance DevOps and Automation Performance Optimization Monitoring and Autoscaling

The hottest Substack posts of Cloud Weekly

And their main takeaways
52 implied HN points 10 Jun 23
  1. Think twice before using Lambdas for training ML/AI models due to limitations and complexities.
  2. Serverless infrastructure can be powerful, but choose the right tools for ML tasks, like EC2 instances for training.
  3. Design decisions in the wrong direction can be costly and time-consuming to change, especially in AI and Cloud systems.
26 implied HN points 27 May 23
  1. There are 4 main disaster recovery techniques: Backup & Restore, Pilot Light, Warm StandBy, and Multi-Site Active/Active.
  2. The techniques aim to optimize for RPO (Recovery Point Objective) and RTO (Recovery Time Objective), which determine how much data loss and downtime are acceptable.
  3. The choice of technique depends on factors like cost, recovery speed, and the criticality of the application, with each method having its own advantages and trade-offs.
17 implied HN points 17 Jun 23
  1. Scaling a database like MySQL for big companies involves challenges like read and write scalability.
  2. To scale reads, common solutions include using read replicas and Master-Slave replication.
  3. Sharding is a method for achieving horizontal scalability in databases by splitting data into multiple databases, which can introduce complexities but resolves write scalability issues.
Get a weekly roundup of the best Substack posts, by hacker news affinity:
8 implied HN points 03 Jun 23
  1. Autoscaling allows you to adjust resources automatically based on traffic, ensuring your application stays performant and resilient.
  2. Auto Scaling Groups in AWS help manage resources by defining minimum, desired, and maximum instances, allowing for easy scaling up and down.
  3. AWS Auto Scaling Groups provide strategies like simple scaling, target scaling, and step scaling to optimize costs and react to traffic based on predefined metrics.
8 implied HN points 29 Apr 23
  1. Load balancing is important for distributing traffic across servers.
  2. Stateless services are preferred over stateful ones for easier scaling.
  3. Different load balancing algorithms like Round Robin, Weighted Round Robin, Least Connections, and Least Time offer various ways to distribute traffic efficiently.