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: modules/learn/pages/services-and-indexes/indexes/global-secondary-indexes.adoc
-19Lines changed: 0 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,32 +20,16 @@ endif::[]
20
20
[abstract]
21
21
{description}
22
22
23
-
Global Secondary Indexes provide the following:
24
-
25
-
* _Advanced Scaling_: GSIs can be assigned independently to selected nodes, without existing workloads being affected.
26
-
* _Predictable Performance_: Key-based operations maintain predictable low-latency, even in the presence of a large number of indexes.
27
-
Index-maintenance is non-competitive with key-based operations, even when data-mutation workloads are heavy.
28
-
* _Low Latency Querying_: GSIs independently partition into the Index Service nodes: they do not have to follow hash partitioning of data into vBuckets.
29
-
Queries using GSIs can achieve low latency response times even when the database scales out; since GSIs do not require a wide fan-out to all Data Service nodes.
30
-
* _Independent Partitioning_: The Index Service provides partition independence: data and its indexes can have different partition keys.
31
-
Each index can have its own partition key, so each can be partitioned independently to match the specific query.
32
-
As new requirements arise, the application will also be able to create a new index with a new partition key, without affecting performance of existing queries.
0 commit comments