Q: 16
HOTSPOT You need to recommend a Fabric streaming solution that will use the sources shown in the following table. 
Your Answer
Discussion
Nah, I think Eventstream is the better call for all sources. Minimizing development effort usually means picking low-code when you can, and maybe the message size limit could be worked around depending on the ingestion scenario. Am I missing some technical blocker?
Hmm, I'd pick Eventstream for all three sources. Saw a similar question in practice and minimizing dev effort usually takes priority.
Apache Spark Structured Streaming for all three sources. Not totally sure since dev effort is a factor, but the message sizes rule out Eventstream here.
All three sources have message sizes way over the 1 MB cap for Eventstream, so Apache Spark Structured Streaming is the only fit here, even if it needs more code. If minimizing dev effort was stricter than message size support, I might say Eventstream-so is there any chance smaller messages are allowed or is >1 MB guaranteed?
Be respectful. No spam.
