Why are side effects risky in Java stream operations?

I separate computation from effects when failure matters. First I derive a bounded plan, then apply writes with explicit idempotency, transaction, retry, and observability decisions. This is especially important for database or network calls, where a partially consumed stream can produce partial external work. Metrics and tracing may be acceptable observational effects, but they still need thread-safe implementations and should not determine business correctness.