From stream to summary
Many notifications are low value individually but useful together. A digest collects events over a period and sends one combined message: your daily activity summary.
How batching works
- Events are appended to a per user buffer keyed by digest type.
- A scheduler fires on a cadence, hourly or daily, and flushes each buffer into one rendered message.
- Empty buffers send nothing, avoiding pointless mails.
Triggers
A digest can flush on time, on a count threshold, or on both. A user with fifty events might get a digest early because the buffer filled.
Benefits and trade offs
Digests cut volume and fatigue but add latency, so they suit non urgent categories. Urgent events skip the buffer and send immediately.
Key idea
Digests batch many low urgency events into one periodic summary, flushing on time or count to reduce notification fatigue.