---
title: "Notifications"
description: "2 posts about Notifications, summarised, each linking to the original."
---

# Notifications
> 2 posts about Notifications, summarised, each linking to the original.

## Articles

### [How Zillow runs 100 million daily notifications on AWS Step Functions](https://yomu.fyi/post/how-zillow-runs-100-million-daily-notifications-on-aws-step-functions.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Nishita Kheur
- Published: Nov 11, 2026
- Type: Problem & solution

Zillow sends over 100 million daily notifications using a centralized, configuration-driven orchestration layer called Campaign Orchestrator. It runs each notification as a short-lived workflow on AWS Step Functions Express Workflows, chosen for being serverless and lower cost than alternatives. A router applies campaign controls like queue polling, batching, and circuit breakers before starting each workflow. The workflows call reusable, schema-driven content modules from the Universal Content Generator library, with JSONata expressions validated via the TestState API. The new architecture cut build effort from 32 to 9 weeks and lowered ongoing maintenance from 8 to 2 hours per week.


### [Expanding Customer Notifications for ClickHouse Managed Postgres](https://yomu.fyi/post/expanding-customer-notifications-for-clickhouse-managed-postgres.md)
- Company: [Clickhouse](https://yomu.fyi/company/clickhouse.md)
- Published: Oct 26, 2026
- Type: Announcement

ClickHouse Managed Postgres launched storage alerts in August, warning at 85% disk usage, and those alerts have already helped customers identify issues like unused replication slots. The service now adds five targeted notifications: inactive replication slots, planned switchovers, unplanned failovers, long-running transactions, and connection-usage warnings. The replication-slot notification triggers when a logical slot retains over 10 GiB of unconfirmed WAL data for two hours, excluding managed CDC slots, and includes slot names. Planned-switchover and unplanned-failover notifications each specify the affected service and completion time, distinguishing scaling events from failure recovery. Long-running transactions open for at least two hours and connection usage at 95% of the limit trigger warnings with transaction age, helping operators check idle sessions, locks, or pool settings before impact, with delivery via console, email, or Slack.
