DataEngPrep.tech
QuestionsPracticeAI CoachDashboardPacksBlog
ProLogin
Home/Questions/Spark/Big Data/Can Presto work with Near Real-Time Data (Streaming Data Source)?

Can Presto work with Near Real-Time Data (Streaming Data Source)?

Spark/Big Datahard0.5 min read

**Why this matters**: Presto/Trino is an MPP query engine—designed for ad-hoc queries over *stored* data. **Native streaming**: No—Presto does not consume Kafka/Kinesis directly. **Near real-time options**: (1) Query frequently updated tables (e.g., Delta with 1-min...

🤖 Analyze Your Answer
Frequency
Low
Asked at 1 company
Category
452
questions in Spark/Big Data
Difficulty Split
88E|81M|283H
in this category
Total Bank
1,863
across 7 categories
Asked at these companies
Walmart
Key Concepts Tested
lakehousespark

Why This Question Matters

This hard-level Spark/Big Data question appears frequently in data engineering interviews at companies like Walmart. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (lakehouse, spark) will help you answer variations of this question confidently.

How to Approach This

This is a senior-level question that tests architectural thinking. Lead with the high-level design, then drill into specifics. Discuss trade-offs explicitly - there is rarely one correct answer. Show awareness of scale, fault tolerance, and operational complexity.

Expert Answer
101 words

Why this matters: Presto/Trino is an MPP query engine—designed for ad-hoc queries over stored data. Native streaming: No—Presto does not consume Kafka/Kinesis directly. Near real-time options: (1) Query frequently updated tables (e.g., Delta with 1-min micro-batches); (2) Kafka connector for bounded reads ( snapshot queries); (3) Materialized views refreshed on schedule. Latency = refresh interval + query time. Scalability trade-offs: Streaming = Kafka Streams, Flink, Spark Structured Streaming. Presto for batch/interactive over lake/warehouse. Cost implications: Running Presto over streaming tables = repeated full scans; incremental tables reduce cost. Best practice: Use Presto for lakehouse querying; separate streaming stack for sub-minute latency.

dataengprep.techdataengprep.techdataengprep.techdataengprep.tech
dataengprep.techdataengprep.techdataengprep.techdataengprep.tech
dataengprep.techdataengprep.techdataengprep.techdataengprep.tech
dataengprep.techdataengprep.techdataengprep.techdataengprep.tech
dataengprep.techdataengprep.techdataengprep.techdataengprep.tech
dataengprep.techdataengprep.techdataengprep.techdataengprep.tech

Want feedback on your answer?

Paste your answer to this question and our AI Coach scores it, finds gaps, and shows you the FAANG-level version.

Try Answer Analyzer →
Want all answers as a PDF for offline study?
1,863 questions across 7 categories — Interview Packs →

Free: Top 20 SQL Interview Questions (PDF)

Get the most asked SQL questions with expert answers. Instant download.

No spam. Unsubscribe anytime.

Related Spark/Big Data Questions

mediumWhat is the difference between repartition and coalesce in Apache Spark?FreehardWhat is the difference between SparkSession and SparkContext in Spark?FreemediumWhat is the difference between cache() and persist() in Spark? When would you use each?FreemediumWhat is the difference between groupByKey and reduceByKey in Spark?FreemediumWhat is the difference between narrow and wide transformations in Apache Spark? Explain with examples.Free

Companies that ask this Spark/Big Data question

Walmart interview questions →

Want to know if YOUR answer is good enough?

Paste your answer and get instant AI feedback with a FAANG-level improved version.

Analyze My Answer — Free

According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.

← Back to all questionsMore Spark/Big Data questions →