shouldiuse.io

VERDICT

Should I use Apache Iceberg?

High-performance format for huge analytic tables - iceberg.apache.org

Depends. Buy in if you run huge, multi-engine analytics on object storage with real data engineers on staff. Small teams with gigabytes — not terabytes — should skip the plumbing and use a managed warehouse, Postgres, or DuckDB.

Confidence

Medium. Based on 13 public sources; many were noise (unrelated 'Iceberg' results). No independent user review ratings found.

Ratings

  • Value for money
  • Ease of use
  • Feature depth
  • Support qualityNo support-quality evidence found
  • Security posture

Pricing

$0

Apache Iceberg (open source)

ModelNot disclosed
Monthly feesNot disclosed
HardwareNot disclosed
Free tierYes

Best for

  • Petabyte-scale analytics on S3/Azure/GCS
  • Multi-engine lakehouses (Spark, Trino, Flink)
  • Teams migrating off Hive or Delta Lake
  • Streaming-plus-batch data platforms

Not for

  • Small teams with gigabytes, not terabytes
  • Apps that just need a database — use Postgres
  • Anyone without dedicated data engineers
  • Buyers wanting vendor support or SLAs

Gotchas - check before you buy

high

Free format, expensive operations: storage bloat, compute waste, compaction overhead eat budgets

medium

Catalog choice (Glue, Hive, Nessie, JDBC) drives lock-in and migration pain

medium

Migrating from Hive or Delta Lake is its own documented project

low

You separately pick storage (S3, Dell ECS) and query engines

Pros and cons

Pros

  • High-performance format for huge analytic tables
  • Spark, Trino, Flink, Presto, Hive, Impala safely share the same tables
  • Free and open-source Apache project
  • Built-in schema evolution, partitioning, branching, encryption
  • Native support in AWS Athena and GCP BigLake

Cons

  • Format, not a product — you assemble storage, catalog, compute yourself
  • Real deployments need Kerberos, Kafka Connect, Flink configuration
  • Operating costs: storage bloat, compaction overhead, compute waste add up
  • No vendor SLAs; support is community or third-party

Sources & method

Analyzed 9/24/2026 - 11 sources - No known vulnerabilities found in the sources reviewed.

official x1review x5security x1news x4

Key stats

  • Value for money: 5/5

    Rating

  • $0

    Starting price

  • 11

    Sources

  • Analyzed

  • Value for money: 5/5. Free format; real costs sit in infrastructure
  • Ease of use: 2/5. Heavy setup: catalogs, Kerberos, engine configs
  • Feature depth: 5/5. Schema evolution, branching, encryption, partitioning in spec
  • Support quality. No support-quality evidence found
  • Security posture: 4/5. Encryption features and public security policy; no known issues
  • $0 Price Open-source Apache project
  • 2017 Created Built at Netflix
  • 6 Engine support Spark, Trino, Flink, Presto, Hive, Impala

Pricing

Apache Iceberg (open source)

$0

  • Full table format spec
  • All engine integrations
  • Community support only

Security

No known vulnerabilities found in the sources reviewed.

What users say

No substantive independent user reviews surfaced; evidence is mostly official docs, vendor tutorials, and academic citations.

Companies that use it

Full analysis

Based on 13 public sources; many were noise (unrelated 'Iceberg' results). No independent user review ratings found.

Free open table format that shines at petabyte scale; overkill plumbing for small teams — use a warehouse or DuckDB.

Methodology

Based on 13 public sources; many were noise (unrelated 'Iceberg' results). No independent user review ratings found.

Sources

  1. official
  2. security
  3. review
  4. TrustRadius overviewtr-web.stage.trustradius.com
    review
  5. review
  6. news
  7. news
  8. news
  9. review
  10. review
  11. news

Rate this review

Anonymous. You can change your vote.

Loading votes…

Comments

One queue. No nested comments. Give a display name first. Limit: 200 words per comment and 7 comments per day. You can edit or delete yours.

Save a name to write a comment.

0 / 200 words

No comments yet.