What is iceberg built with?

iceberg is a Java repo built with org.apache.flink:flink-table-api-java-bridge, Apache, jakarta.servlet:jakarta.servlet-api, org.eclipse.jetty.compression:jetty-compression-gzip, org.eclipse.jetty.compression:jetty-compression-server, and 1 more. It signs people in with sso, software.amazon.awssdk:auth, com.azure:azure-identity, and software.amazon.awssdk:sts, stores files in AWS S3, connects to Google, makes its content with mkdocs-material-extensions, validates its data with openapi-spec-validator, is tested with apiguardian-api, com.google.guava:guava-testlib, flink-test-utils-junit, hadoop-minicluster, junit-jupiter-engine, and 16 more, deploys with flink-metrics-dropwizard, slf4j-simple, and org.slf4j:slf4j-api, and uses azure-sdk-bom, calcite-druid, connect-json, flink-avro, hadoop-client, and 25 more. It has 1,428,615 written lines, with 2,566 test files.

Read on November 15, 2026, at commit 5b132c8. Read it as markdown

The card says what it's built with. Its whole map opens it up: every part of the code and how it connects to the rest.

Frontend

Backend

Data 28

16 more
  • com.aliyun.oss:aliyun-sdk-oss9 files
  • software.amazon.awssdk:kms9 files
  • org.apache.flink:flink-connector-files6 files
  • org.projectnessie.nessie:nessie-client6 files
  • software.amazon.s3.analyticsaccelerator:analyticsaccelerator-s33 files
  • org.apache.parquet:parquet-avro2 files
  • azure-sdk-bom
  • calcite-druid
  • connect-json
  • flink-avro
  • hadoop-client
  • hadoop-common
  • kafka-clients
  • s3
  • sqlite-jdbc
  • url-connection-client

Sign-in 4

Services 4

Support

The base 6

  • Apache174 files
  • org.apache.flink:flink-table-api-java-bridge704 files
  • jakarta.servlet:jakarta.servlet-api2 files
  • org.eclipse.jetty.compression:jetty-compression-gzip1 file
  • org.eclipse.jetty.compression:jetty-compression-server1 file
  • org.eclipse.jetty.ee10:jetty-ee10-servlet1 file

Content 1

  • mkdocs-material-extensions

Validation 1

  • openapi-spec-validator

Testing 21

  • org.apache.flink:flink-connector-test-utils6 files
  • com.google.guava:guava-testlib
  • org.junit.jupiter:junit-jupiter2,172 files
  • org.assertj:assertj-core2,074 files
  • org.mockito:mockito-core215 files
  • org.awaitility:awaitility108 files
  • org.testcontainers:testcontainers9 files
  • org.mockito:mockito-junit-jupiter5 files
  • org.junit.platform:junit-platform-suite-api4 files
  • org.apache.hadoop:hadoop-hdfs1 file
  • apiguardian-api
  • flink-test-utils-junit
9 more
  • hadoop-minicluster
  • junit-jupiter-engine
  • junit-pioneer
  • junit-platform-launcher
  • junit-platform-suite-engine
  • mockito-inline
  • mockserver-client-java
  • mockserver-netty
  • testcontainers-junit-jupiter

Deploy 3

Tools 9

  • datamodel-code-generator
  • mkdocs-macros-plugin
  • org.immutables:value58 files
  • antlr4
  • antlr4-runtime
  • jsr305
  • mkdocs-awesome-pages-plugin
  • mkdocs-redirects
  • yamllint

Other 27

  • org.apache.httpcomponents.client5:httpclient52 files
  • Esoteric Software1 file
  • com.google.guava:guava
  • Scala
  • com.fasterxml.jackson:jackson-bom84 files
  • com.fasterxml.jackson.core:jackson-core74 files
  • org.apache.datasketches:datasketches-java19 files
  • org.roaringbitmap:RoaringBitmap5 files
  • joda-time:joda-time3 files
  • software.amazon.awssdk:iam3 files
  • dev.failsafe:failsafe1 file
  • io.airlift:aircompressor1 file
15 more
  • arrow-memory-netty
  • bcpkix-jdk18on
  • bcprov-jdk18on
  • bcutil-jdk18on
  • bom
  • calcite-core
  • jackson-annotations
  • jackson-databind
  • jakarta.el-api
  • jaxb-api
  • jaxb-runtime
  • libraries-bom
  • lz4-java
  • microprofile-openapi-api
  • netty-buffer

Other repos with a similar stack

Ordered by how much of its stack they share with iceberg, then by stars.

Frequently asked questions

What language is iceberg written in?
iceberg is written in Java, with 1,428,615 written lines.
What framework does iceberg use?
iceberg is built with org.apache.flink:flink-table-api-java-bridge, Apache, jakarta.servlet:jakarta.servlet-api, org.eclipse.jetty.compression:jetty-compression-gzip, org.eclipse.jetty.compression:jetty-compression-server, and org.eclipse.jetty.ee10:jetty-ee10-servlet.
What does iceberg sign people in with?
iceberg signs people in with sso, software.amazon.awssdk:auth, com.azure:azure-identity, and software.amazon.awssdk:sts.
What services does iceberg use?
iceberg stores files in AWS S3, connects to Google, and uses azure-sdk-bom, calcite-druid, connect-json, flink-avro, hadoop-client, hadoop-common, Hive, kafka-clients, org.mongodb:bson, s3, sqlite-jdbc, url-connection-client, org.apache.hadoop:hadoop-mapreduce-client-core, org.apache.avro:avro, org.apache.arrow:arrow-vector, org.apache.orc:orc-core, com.github.ben-manes.caffeine:caffeine, org.apache.parquet:parquet-hadoop, software.amazon.awssdk:glue, software.amazon.awssdk:dynamodb, com.aliyun.oss:aliyun-sdk-oss, software.amazon.awssdk:kms, org.apache.flink:flink-connector-files, org.projectnessie.nessie:nessie-client, software.amazon.s3.analyticsaccelerator:analyticsaccelerator-s3, org.apache.parquet:parquet-avro, MongoDB, SQLite, Kafka, and Google Cloud Storage.

The proof: aws/src/main/java/org/apache/iceberg/aws/AwsClientFactory.java, line 23

Does iceberg have tests?
Yes. iceberg has 2,566 test files and is tested with apiguardian-api, com.google.guava:guava-testlib, flink-test-utils-junit, hadoop-minicluster, junit-jupiter-engine, junit-pioneer, junit-platform-launcher, junit-platform-suite-engine, mockito-inline, mockserver-client-java, mockserver-netty, testcontainers-junit-jupiter, org.junit.jupiter:junit-jupiter, org.assertj:assertj-core, org.mockito:mockito-core, org.awaitility:awaitility, org.testcontainers:testcontainers, org.apache.flink:flink-connector-test-utils, org.mockito:mockito-junit-jupiter, org.junit.platform:junit-platform-suite-api, and org.apache.hadoop:hadoop-hdfs.
Which repos have a stack like iceberg's?

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →

Is it your repo? Add its badge, keep it up to date or take it down →