Redshift and Databricks: querying across platforms
Interoperability is becoming a practical alternative to consolidating every analytical workload onto one platform.
What happened
AWS documented how United Airlines uses AWS Glue Data Catalog federation to query data governed by Databricks Unity Catalog directly from Amazon Redshift Serverless. The architecture allows SQL access without duplicating the underlying data and uses AWS Lake Formation and catalog federation for governance.
Why it matters
Large organisations frequently run multiple analytical platforms for legitimate reasons. The traditional answer has often been another ingestion pipeline or another copy of the data. Federated catalog and query architectures offer a different model: preserve platform specialisation while making governed data discoverable across boundaries.
Who it affects: Enterprise data architects, AWS and Databricks customers, platform engineers and organisations operating multi-engine lakehouse environments.
What to do next
Inventory places where datasets are copied mainly because another engine needs to query them. Evaluate whether federation, open table formats and common governance can eliminate some of those copies without creating unacceptable latency or dependency risks.
Signal Take
The modern data stack may not converge into one engine. It may converge around shared metadata, open formats and interoperable governance. That is a materially different architecture.
Scope and limitations
This analysis interprets the linked vendor material. No independent product benchmark or deployment test was performed.
Sources and editorial record
AWS — United Airlines catalog federation (opens in a new tab)- Source type
- Vendor documentation or announcement
- Source published
- 15 Sept 2026
- Source checked
- 19 Sept 2026
Prepared with AI assistance and checked against the linked source. This is editorial interpretation, not an independent product benchmark. How we work.