Architecture Lakehouse - thekaveh/atlas GitHub Wiki

8.9. Data Engineering Lakehouse Flow

MinIO, Iceberg REST, Supabase Postgres, Spark, JupyterHub, Zeppelin, Airflow, Trino, and Redpanda.

1. Diagram

Data Engineering Lakehouse Flow architecture diagram

Open the full-size diagram.

2. Notes

Iceberg REST keeps its catalog metadata in Supabase Postgres through a JDBC catalog, not a Hive metastore. Atlas sets CATALOG_URI to jdbc:postgresql://supabase-db:5432/iceberg. The fixture uses in-memory SQLite when the catalog URI is absent; a restart loses that metadata. A supplied URI is used as configured; invalid connections can prevent startup. Trino runs one coordinator and no workers, by design. Spark still starts with ICEBERG_REST_SOURCE=disabled for ML-only use; only lakehouse SQL fails.

3. Source Files

  • services/jupyterhub/service.yml
  • services/zeppelin/service.yml
  • services/airflow/service.yml
  • services/redpanda/service.yml
  • services/minio/service.yml
  • services/trino/service.yml
  • services/iceberg-rest/service.yml
  • services/spark/service.yml
  • services/supabase/service.yml