---
title: #golang
description: 1 article about golang — guides and explainers from the WatchFor team.
canonical: https://watchfor.io/blog/tag/golang
---

[All posts](/blog)

# #golang

Articles tagged "golang".

[All](/blog)[Monitoring](/blog/category/monitoring)[Networking](/blog/category/networking)[Performance](/blog/category/performance)[Security](/blog/category/security)[Reliability](/blog/category/reliability)[Email](/blog/category/email)[DevOps](/blog/category/devops)[Engineering](/blog/category/engineering)

[All articles](/blog/all)

1 article

[EngineeringAug 06, 2026

## Scheduling 25 million checks with one Go binary — and no next_run_at column

Most schedulers store the next run time in a database and fight write amplification forever. Ours stores no per-run scheduling state at all: every job's schedule is a pure function, recomputable anywhere. Here's the design — a 256-shard time wheel, an append-only change log — and the honest numbers from load-testing it to 25 million active jobs.WatchFor Team6 min read](/blog/scheduling-25-million-checks-one-go-binary)

---

Canonical page: https://watchfor.io/blog/tag/golang · Site guide: https://watchfor.io/llms.txt