Skip to content
Beta

Architecture Asset: Sovereign Lakehouse Data Platform on STACKIT

Last updated on

Overview

Section titled “Overview”

This pattern is a typical target for a governed, sovereign data platform. Raw data lands in Object Storage as the data lake, is processed on Kubernetes, and is served through managed PostgreSQL and OpenSearch for analytics and search.

Typical use case

Section titled “Typical use case”
  • Central data foundation: consolidate data from many sources into a governed lakehouse.
  • Analytics and search: serve curated data for BI, reporting, and full-text or vector search.
  • Sovereign hosting: keep all storage and processing on a sovereign cloud with clear residency.

Architecture diagram

Section titled “Architecture diagram”
Source SystemsSTACKIT Data PlatformPlatform ServicesApplicationsOperational DBsFiles & ExportsIngestion & IntegrationData Lake (Object Storage)Processing (Kubernetes)Serving LayerSecret ManagerObservabilityPostgreSQLOpenSearch

Design best practices

Section titled “Design best practices”
  • Treat data as a product: assign ownership, documentation, and quality SLAs per dataset.
  • Separate raw, curated, and serving layers: keep clear boundaries and lineage between zones.
  • Use Secret Manager by default: never embed credentials in jobs or manifests.
  • Standardize observability: monitor pipeline health, freshness, and cost from day one.

Related data & AI assets

Section titled “Related data & AI assets”
Asset historyActive 5 of the last 12 weeksTMUpdatedNo updates · 1 bar = 1 week i
Maintainers
TMTobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 12 of the last 12 weeks · 168 updatesSTACKITwww.linkedin.com/in/tobias-müller-011304172Contributed in STACKIT
Show full history (4 more)