You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: data-explorer/multi-tenant.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ For instance, if a tenant performs many compute-intensive queries or ingestions,
25
25
26
26
The next sections explore deployment architectures in detail. This section contrasts the architectures to facilitate decision making.
27
27
28
-
|Architecture|Strenghts|
28
+
|Architecture|Strengths|
29
29
|---|---|
30
30
|One tenant per database|- Tenants' isolation: no need for proxy<br />- Can have different policies, such as retention policies, per tenant<br />- Flexibility in schema evolution per tenant<br />- Easy and quick removal of tenant data|
31
31
|One table for many tenants|- Efficient data consolidation and extent management<br />- Simplified schema evolution<br />- Best suited for materialized views<br />- Ideal for partitioning|
0 commit comments