Infrastructure Task Scheduling
Infrastructure Task Scheduling with Resilience
₩ 142,000 (informational)
Overview
Operators learn how to layer retries, centralize logging, and document failure domains without promising uptime miracles. Labs include Linux cron interoperability notes for hybrid teams.
Features
- ScheduledJob vs Task Scheduler decision matrix
- Retry ladders with capped backoff for noisy networks
- Cross-platform wake signals using lightweight HTTP pings
- Log shipping to existing analytics stacks without new vendors
- Warmup scripts for maintenance windows
- Failure domain maps for dependent batch files
- Operator checklists for daylight-saving drift
Outcomes
- Publish a dependency map for your top five scheduled jobs
- Reduce silent failures using shared transcript headers
- Deliver a stakeholder sign-off memo for new schedules
Lead mentor
Taeyang Lee
Training director covering reliability narratives for infrastructure teams.
FAQ
Do we cover Kubernetes cronjobs?
We reference them in the appendix only; Windows-focused labs take priority.
Are monitoring agents provided?
No. You wire outputs to whatever analytics stack your org already funds.
Refund window?
See the Cancellation Policy page for the 14-day window and exceptions.
Experience notes
Retry ladder worksheet is pinned above my desk. Still tweaking logging verbosity, which the course flags as a personal tuning task.