jay/notes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added part2 & chapter3
All checks were successful
Build and Deploy MkDocs / deploy (push) Successful in 11s
Details

Browse Source
This commit is contained in:
John Gatward
2026-03-10 12:22:47 +00:00
parent b2a1f705a9
commit 3a49c14cfa
3 changed files with 48 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/books/api_design_patterns/part1/chapter2.md
View File

@@ -21,4 +21,11 @@ A **software design *pattern*** is a particular design that can be applied over
- Rigid interfaces make it much more difficult to iterate toward a great design.
- We are often stuck with all design decisions, both good and bad.
Page 20: 2.3.3 Overview
**Pagination Pattern**: The pagination pattern is a way of retrieving a long list of items in smaller, more manageable chunks. The pattern relies on extra fields on both the request and response.
Moving from a non-paginated to paginated response pattern:
Q. What happens if we don't start with the pattern?
1. All previously written clients are expected all the data in one list - it has no way of getting subsequent pages.
2. Clients are left to think they have all the data - which can lead to incorrect conclusions.