mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-20 18:52:28 +00:00
Brendan Clement
198812fd53
The existing docs have 254 findings from our shared Vale rules. Contributors would otherwise inherit these when editing the same lines. Clean up the prose across 80 pages: correct product names and a repeated word, simplify a few phrases, and replace dashes with punctuation that fits each sentence. The pinned Vale scan now reports zero findings, with no suppressions.
21 lines
802 B
Plaintext
21 lines
802 B
Plaintext
---
|
|
title: "Enterprise architecture"
|
|
sidebarTitle: "Architecture"
|
|
description: "The tiers a deployment runs, and how they scale independently."
|
|
icon: cubes
|
|
keywords: ["architecture", "control plane", "data plane", "indexer"]
|
|
---
|
|
|
|
<Badge color="red">Enterprise</Badge>
|
|
|
|
This page describes a LanceDB Enterprise capability. The embedded form
|
|
of LanceDB has no server to provide it. See
|
|
[Architecture](/architecture) for what differs between the two.
|
|
|
|
A deployment separates compute from storage so each scales on its own: table
|
|
data and indexes live in object storage, while query serving and background work
|
|
run on machines that can be replaced without any of them owning the data.
|
|
|
|
[Architecture](/architecture) covers this alongside the embedded form, which is
|
|
the comparison most readers want first.
|