Spatial SQL and spatial joins are now supported on Lakehouse//RT, bringing low-latency, high-concurrency geospatial queries directly to governed lakehouse data. Teams can run spatial workloads without copying data into a separate geospatial serving layer.
Key Highlights
- Up to 38x faster under high concurrency: In the reported SpatialBench comparison with 50 concurrent users, Lakehouse//RT delivered up to 38x faster performance than a traditional cloud data warehouse. Results vary by query and workload.
- Run spatial SQL on governed data: Use native GEOMETRY and GEOGRAPHY data types, spatial joins, and the broader Databricks spatial function library on Delta and Iceberg data.
- Reuse existing queries: Existing spatial SQL from Databricks SQL Serverless can run on Lakehouse//RT without query changes; create a Lakehouse//RT warehouse and point workloads to it.
- Support real-time geospatial use cases: Analyze coverage areas, store trade areas, energy infrastructure, insurance risk, delivery zones, and location-based security signals at higher concurrency.
- Keep the lakehouse architecture: Combine real-time performance with open formats, Unity Catalog governance, AI/BI maps, and the rest of the Databricks Data + AI Platform, without a separate serving stack.
- Available in Beta: Spatial SQL and spatial joins on Lakehouse//RT are available now in Beta. Check regional and feature availability before deployment.
๐ Read the full story here