Autoscaling vs Manual Scaling: Availability‑Cost Trade‑off for Low‑Traffic Heroku Apps
Goal: Determine whether enabling Heroku autoscaling for a low‑traffic application yields lower monthly cost than running a single hobby dyno (with free dyno hours) when the app experiences intermittent requests. Constraints: Free dyno hours provide ≈550 h/month but cause the dyno to sleep after 30 minutes of inactivity, adding latency on wake‑up; autoscaling
heroku