Skip to content
Lakehouse Compare

Method, read 10 Nov 2026

How Lakehouse Compare works

Open the Compute BillSee the platforms

What the site does and does not do

The site lists facts about ten ways to run Spark batch work on a lakehouse and about Apache Iceberg, Delta Lake and Apache Hudi. It does not recommend an option and does not say which one a reader should choose. Pages end with facts, not with a pick.

A buyer situation page says what a team in that situation should check and which published facts answer each check.

How facts are sourced, dated and labelled

Each fact has a source URL and a read date in the form YYYY-MM-DD. The read date is the day the page was fetched, and facts are re-read when a page is updated.

A claim made by a vendor is written as the vendor's claim ("DualBird says", "per Databricks documentation", "AWS states"). Every vendor, DualBird included, is labelled the same way. A claim stays a claim until a named party other than the vendor has repeated it, and then the page names that party.

The none-found rule

When a fact was looked for in the sources named and was not there, the page says "none found on 2026-11-10" (or the date of the search). The page does not write that a vendor has no such feature, because the absence applies to the pages read, not to the product.

The benchmark rule

A benchmark appears only as a number that a named party published, with the link, the publication date and who ran the test. Numbers are not derived, averaged across sources or estimated. A result run by the vendor of the product tested is marked as such, together with whether the method is published.

Order rules

  • Platforms are listed alphabetically by name, and so are vendors inside every situation check.
  • Table formats are listed alphabetically.
  • The Compute Bill has two groups: lines that price the same ten EC2 nodes (the open stack on EC2, EMR on EKS, EMR on EC2, EMR Serverless and Databricks on AWS) and lines whose billing unit is mapped to the job by a stated assumption (the other seven). Both groups are alphabetical, and a line with no total is shown in place with the missing price stated. Totals in the mapped group are read against their own assumptions, not against each other.
  • Guides, glossary entries and news items are ordered by date or alphabetically, as each page states.

Corrections

A reader who finds a wrong fact, a broken source link or an out-of-date price can write to editor@datalakehousecompare.com. A correction is made on the page, with the date of the change, and the correction page lists it.

Sources

  1. AWS EMR pricing page, read 10 Nov 2026

Last reviewed 10 Nov 2026.