Replayable telemetry ingestion for independent consumers

Challenge brief

Harbourline Marine streams telemetry from 400,000 hull sensors; each unit emits a reading every two seconds, and bursts during storm season triple the rate without warning. The diagnostics team needs the readings from a single sensor in the order they were emitted, because a pressure alarm only means something after the preceding temperature trend. Two applications must read the same feed at the same time without slowing each other: a live operations dashboard and a batch anomaly detector. After a detector bug is fixed the team must re-read the last seven days of readings, and the platform group wants whichever design adds the least operational overhead. Which ingestion design should the platform group choose?

Success criteria

• 1.Add one Kinesis data stream partitioned by sensor ID so each sensor's records stay in one shard.
• 2.Add both consumer applications; they read the same stream independently rather than sharing one queue.
• 3.Connect the stream to each consumer so both read the same records.
• 4.Remove the work queue; a drained queue splits the feed and keeps nothing to replay.

Service palette