Database / LanceDB Interview questions
List the storage backends supported by LanceDB?
LanceDB can store its underlying Lance-format data files on a local filesystem or directly on cloud object storage, without needing a separate data-loading step to move data between the two.
| Backend | Typical Use |
| Local filesystem | Development, prototyping, single-machine production workloads |
| Amazon S3 | Production deployments needing durable, scalable object storage |
| Google Cloud Storage (GCS) | GCP-based deployments |
| Azure Blob Storage | Azure-based deployments |
Connecting to any of these is largely a matter of changing the URI passed to lancedb.connect() — a local path for the filesystem backend, or an s3://, gs://, or az:// URI for the respective cloud backends — with the same table and query APIs working identically regardless of which backend is underneath.
Because Lance is designed for efficient random access directly against object storage (rather than requiring data to be downloaded locally first), a LanceDB table can serve queries directly from S3 or GCS, which is the foundation of the "lakehouse for AI" pattern where storage and compute stay decoupled.
More Related questions...