1 Answer
- Newest
- Most votes
- Most comments
0
Take a look at this article: https://aws.amazon.com/graphql/graphql-dynamodb-data-modeling/
A lot has to do with table design, single vs. multi-table. Pagination is not a bad thing, especially for mobile or web clients who may not scroll through 1000's of record. I would make the pagination parameter configurable, do some testing based on how the client uses the front end. If this is an analytics apps, then a relational app with more complex SQL might be better.
answered a year ago
Relevant content
- Accepted Answerasked a year ago
- asked 2 years ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago