WHEN NOT TO USE STREAM PROCESSING: MESSAGING AND APIS ARE OFTEN ENOUGH

Summary from the TLDR IT newsletter

Stream processing is valuable for continuous event-driven computation but is often the wrong architecture for request-response interactions, direct state queries and corrections, or work requiring locks. As evidence, Kestra rebuilt its messaging layer around plain queueing, and Confluent moved Control Center's metrics pipeline from Kafka Streams to Prometheus.