Paging - GradedJestRisk/web-training GitHub Wiki

This page may be moved to design repository, as it's not specific to web, but to any client-server architecture.

If a full resource retrieval would either:

  • exhaust memory on server-side
  • last too long on server-side, thereby negatively influencing other queries duration
  • produce an oversized HTTP transfer
  • take too much time for front to process
  • exhaust front memory
Then it's time to put resource under paging. Query string best practice here

Note that you'll have to implement, in addition to simple paging retrieval:

  • go to first/last record
  • search (with paging)
Note: paging is a data segregation pattern, as data may be filtered in database / back-end repository / front-end repository (aka store)
⚠️ **GitHub.com Fallback** ⚠️