A city operations center needs Kafka-compatible streaming so several existing consumer apps can share the same topics, while a separate telemetry lane only needs an AWS-native stream. How should the architect choose?
Select an answer to reveal the explanation.
Short Explanation
Think of MSK as renting a Kafka neighborhood the city’s existing consumer apps already know how to walk. Kinesis is the AWS-native stream when you don’t need that Kafka handshake.
Full Explanation
Amazon Managed Streaming for Apache Kafka (MSK) provides a Kafka-compatible cluster so multiple consumers can use familiar Kafka clients and topic semantics. Amazon Kinesis Data Streams is the purpose-built AWS-native streaming service when Kafka compatibility is not required. Mixing the two backwards, substituting SQS for continuous multi-consumer streaming, or assuming Amazon MQ speaks Kafka natively misses the ecosystem-driven selection.