# Five situations, what to check in each

Situations, read 10 Nov 2026

**The short answer.** Five buyer situations, each with the checks a team in that situation should run and the published facts that answer them: a Spark bill that doubled on EMR or EKS, nightly pipelines that miss the morning, AI data preparation, leaving Databricks or Snowflake, and daily Iceberg compaction cost.

## Five situations

- [Spark bill doubled on EMR or EKS](/situations/bill-doubled/): What to check when an EMR or EKS Spark bill doubled: billing units, cost claims, code changes, settings that move spend, and region, with published facts.
- [Nightly pipelines finish after the morning deadline](/situations/late-pipelines/): For nightly pipelines that miss the morning: published runtimes, who ran them, whether a reader can repeat them, failure behavior on large jobs, and Spark versions.
- [AI and feature pipelines wait on data preparation](/situations/ai-data-prep/): For AI training and feature pipelines that wait on data prep: table formats, unchanged Spark code, UDF and fallback behavior, and where data has to live.
- [Leaving Databricks or Snowflake for an open stack](/situations/leaving-managed/): For a team weighing a move from Databricks or Snowflake to an open stack: what you own afterward, shared table formats, Spark changes and cloud coverage.
- [Large Iceberg tables with daily compaction cost](/situations/iceberg-compaction/): For teams paying for daily Iceberg compaction: who runs it, the published unit prices, strategies, delete handling and the benchmarks that exist.

Last reviewed 10 Nov 2026. Canonical: https://datalakehousecompare.com/situations/
