You're reading from Amazon DynamoDB - The Definitive Guide Explore enterprise-ready, serverless NoSQL with predictable, scalable performance

Product type Paperback

Published in Aug 2024

Publisher Packt

ISBN-13 9781803246895

Length 414 pages

Edition 1st Edition

Languages

Java

Tools

AWS

Concepts

Databases

Author (1):

Aman Dhingra

View More author details

Table of Contents (24) Chapters

Preface

1. Part 1:Introduction and Setup

2. Chapter 1: Amazon DynamoDB in Action FREE CHAPTER

3. Chapter 2: The AWS Management Console and SDKs

4. Chapter 3: NoSQL Workbench for DynamoDB

5. Part 2: Core Data Modeling

6. Chapter 4: Simple Key-Value

7. Chapter 5: Moving from a Relational Mindset

8. Chapter 6: Read Consistency, Operations, and Transactions

9. Chapter 7: Vertical Partitioning

10. Chapter 8: Secondary Indexes

11. Part 3: Table Management and Internal Architecture

12. Chapter 9: Capacity Modes and Table Classes

13. Chapter 10: Request Routers, Storage Nodes, and Other Core Components

14. Part 4: Advanced Data Management and Caching

15. Chapter 11: Backup, Restore, and More

16. Chapter 12: Streams and TTL

17. Chapter 13: Global Tables

18. Chapter 14: DynamoDB Accelerator (DAX) and Caching with DynamoDB

19. Part 5: Analytical Use Cases and Migrations

20. Chapter 15: Enhanced Analytical Patterns

21. Chapter 16: Migrations

22. Index

Why subscribe?

23. Other Books You May Enjoy

Global secondary indexes

Contrary to LSIs, GSIs offer the flexibility to provide a different view of the DynamoDB table data, including the ability to use a different partition key from the base table. This means that GSIs can have entirely different partition keys and sort key attributes compared to the base table, offering significant flexibility. DynamoDB indexes the complete table data in a different view specified by your GSI key schema.

Think of a GSI as a materialized view of your DynamoDB base table data. When creating a GSI, you specify the partition key and sort key attributes, and DynamoDB handles the creation of this materialized view on demand.

To illustrate, in the e-wallet use case, if you needed to retrieve all transactions across users for a particular currency, this could be achieved by using the currency as the GSI’s partition key attribute, with the sort key being a combination of walletID and transactionID. This functionality may not be possible to...