Process streams correctly: aggregate on event-time with watermarks (not processing-time), window deliberately (tumbling/sliding/session), handle late data explicitly, checkpoint and TTL-bound state, join with aligned time, and design for backpressure.
Scanned 9/23/2026
Skills Directorynpx -y skills add mcorbett51090/RavenClaude --skill stream-processing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Stream Processing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-stream-processing)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: stream-processing
description: "Process streams correctly: aggregate on event-time with watermarks (not processing-time), window deliberately (tumbling/sliding/session), handle late data explicitly, checkpoint and TTL-bound state, join with aligned time, and design for backpressure."
---
# Stream Processing
## Event-time + watermarks
Aggregate on the event's timestamp; a **watermark** closes windows correctly. Processing-time breaks on late/out-of-order events.
## Windows
Tumbling (fixed) / sliding (overlapping) / session (activity gap) — the window IS the question.
## Late data
Allowed lateness + side output, or accept the drop — **never silently** lose late events.
## State & backpressure
Checkpoint stateful operators; **TTL-bound** state (unbounded = OOM). Joins align event-time + hold state. Handle backpressure; monitor consumer **lag** -> observability-sre.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
