Schedule design patterns
Build the schedule pattern each environment needs, including the ones that cannot simply be switched off.
5 lessons. 1 quiz.
Read in order, or jump to what you need.
Four envs: dev / test / stage / prod
By the end of this lesson, you will be able to assign the right schedule pattern to each of dev/test/stage/prod, estimate the cost reduction from environment-aware scheduling, and adapt the patterns for global / async / 24/7 teams.
Scale-to-one weekend pattern
By the end of this lesson, you will be able to apply the scale-to-one pattern for weekend cost reduction without full shutdown, choose between scale-to-zero, scale-to-one, and always-on, and handle the edge cases (quorum, sharding, health checks).
Rolling test environment
By the end of this lesson, you will be able to implement rolling test environments that scale up per-test and down after, calculate the cost savings vs always-on, and mitigate the cold-start latency for engineer experience.
Freeze windows
By the end of this lesson, you will be able to implement schedule freeze windows for holidays and special events, choose the right granularity (org-wide / targeted / per-resource), and communicate freezes to the team to avoid surprise.
Demo / prod-like environments
By the end of this lesson, you will be able to distinguish demo-prod from staging/dev/prod, configure the right schedule pattern for sales demos / training / investor showcases, and recover the often-forgotten cost from idle demo environments.
Module quiz.
Take it once the lessons are done.