Asset
12 lines, 11 with a total
Lakehouse Compute Bill
Published unit prices times one stated workload, with the formula and what each line leaves out.
Open the Compute BillCompared, read 10 Nov 2026
The Compute Bill, one job priced 12 ways
Same ten EC2 nodes
Billing unit mapped by a stated assumption
US dollars, on-demand prices read 10 Nov 2026. Formulas and assumptions.
The bill beside the headline prices the same ten EC2 nodes first, then the platforms whose own billing unit is mapped to the job by a stated assumption. Both groups are alphabetical. Lines in the second group bill different units and engines, so each total is read against its own assumption, not against the other lines. 1 of 12 lines has no total (Onehouse); the Compute Bill page says why.
Asset
12 lines, 11 with a total
Published unit prices times one stated workload, with the formula and what each line leaves out.
Open the Compute BillFormats
3 formats, 8 rows each
The three open table formats in the same rows: releases, engines, compaction, catalogs.
Read the formatsUpkeep
5 pages
What compaction, snapshot expiry and table services do, and which platforms run them for you.
Read the maintenance pagesProfiles
10 entries
Same fields in the same order for every entry: what it does well, where it is limited, the published facts.
Read the profiles| Platform | Kind | Does well | Limited |
|---|---|---|---|
| Amazon EMR plus Athena on Iceberg | Spark and SQL engines on AWS | Per AWS documentation, the EMR runtime for Spark is 100% API-compatible with open-source Spark, so existing jobs need no rewrite (read 2026-11-10). | Per AWS documentation, Athena compaction is manual (you run OPTIMIZE ... REWRITE DATA USING BIN_PACK and VACUUM), and Glue Iceberg compaction is off by default for new tables. |
| Databricks | Managed lakehouse built around Delta Lake | Per Databricks documentation, Photon keeps the Spark Catalyst planner, works with existing Spark API code and falls back to the Spark runtime for unsupported operations (read 2026-11-10). | Per Databricks documentation, serverless compute supports only Spark Connect APIs, so RDD APIs, R and Maven coordinates are unsupported, and ANSI mode on by default can change results of existing jobs. |
| Dremio | Lakehouse with its own SQL engine | Per Dremio documentation, Iceberg tables in the Open Catalog get automatic optimization: data file compaction, row-level delete handling, clustering, partition evolution and manifest rewriting (read 2026-11-10). | Per Dremio documentation, queries run on its own columnar engine, not on Spark, and the pages read describe no mode that runs existing Spark jobs. |
| DualBird | FPGA Spark plugin for AWS F2 | DualBird says onboarding is two changes: switch the EC2 instance type to F2 and add the DualBird Spark plugin, with Spark still handling planning and scheduling (read 2026-11-10). | DualBird is not a lakehouse. It speeds up Spark on EMR and EKS; a team on a fully managed platform cannot add it. |
| Google BigQuery and BigLake | Serverless Google Cloud data warehouse | Per Google documentation, BigQuery Iceberg managed tables store data in buckets you own, support DML and streaming, and run automatic compaction, clustering and garbage collection (read 2026-11-10). | Per Google documentation, BigQuery Omni on S3 does not support DML or CREATE TABLE, so it does not run write-heavy Spark batch ETL on S3. |
| Microsoft Fabric | SaaS analytics on Azure with Spark | Per Microsoft Learn, the native execution engine (Apache Gluten and Velox) needs no code changes, falls back to JVM Spark for unsupported operators and supports Parquet and Delta (read 2026-11-10). | Per Microsoft Learn, Fabric runs over OneLake on Azure and the region page lists Azure regions only, so Spark compute does not run inside AWS. |
| Onehouse | Managed lakehouse in your cloud account | Per Onehouse documentation, its jobs are fully compatible with Apache Spark and EMR code can be reused unless it uses AWS-specific features (read 2026-11-10). | Per Onehouse documentation, billing is in OCUs on a bring-your-own-cloud model, and no dollar rate per OCU was found on 2026-11-10. |
| Open stack on EMR and EKS | Self-run Spark with open table formats | Per AWS documentation, EMR 7.14.0 packages Spark 3.5.8-amzn-0, Delta 3.3.2-amzn-3, Iceberg 1.10.1-amzn-1 and Hudi 1.0.2-amzn-3, so all three formats are available (read 2026-11-10). | Per the Apache Iceberg documentation, users run table maintenance themselves: expire snapshots, remove orphan files and compact with rewriteDataFiles as jobs they schedule (read 2026-11-10). |
| Snowflake | Cloud data platform with PySpark support | Per Snowflake documentation, Snowpark Connect runs existing PySpark DataFrame code against the Snowflake engine over Spark Connect, and batch jobs are submitted with the Snowpark Submit CLI (read 2026-11-10). | Per Snowflake documentation, Snowpark Connect supports Apache Spark 3.5 only, and DayTimeIntervalType, YearMonthIntervalType and user-defined types are unsupported (read 2026-11-10). |
| Starburst | Managed Trino service for Iceberg | Per Starburst documentation, Galaxy creates and writes Iceberg tables (Parquet, ORC or Avro) and runs maintenance with ALTER TABLE ... EXECUTE optimize, expire_snapshots and remove_orphan_files (read 2026-11-10). | Per Starburst documentation, Galaxy runs SQL on Trino, not Spark, so DataFrame code, UDFs and PySpark would be rewritten as Trino SQL or kept on Spark (read 2026-11-10). |
A lakehouse keeps data as open files, usually Parquet, in object storage such as Amazon S3, and adds a table format over the files. The table format records which files make up a table, so engines can read and write it with transactions. Apache Iceberg, Delta Lake and Apache Hudi are the three open table formats covered here.
Any engine that understands the format can use the same table. The Apache Iceberg home page names Spark, Trino, Flink, Presto, Hive and Impala as engines that work with the same tables at the same time. The Delta Lake home page lists a similar set, and the Hudi home page lists Spark, Flink and others under data processing.
The platforms on this site differ in who runs the engine, who maintains the tables (compaction, snapshot cleanup, file layout) and what they bill for. A team that owns the Spark cluster bill needs those three facts side by side, each with its source and read date.
Data catalogs in the governance sense, lineage, semantic layers and MCP servers for data are outside the subject of this site.
Last reviewed 10 Nov 2026.