How API Pagination Design Affects Performance and Developer Experience episode artwork

EPISODE · Jun 1, 2026 · 9 MIN

How API Pagination Design Affects Performance and Developer Experience

from The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers · host Fexingo

Episode 24 of The Developer Tools Podcast explores how API pagination design directly impacts both backend performance and frontend developer experience. Lucas and Luna break down the trade-offs between offset-based and cursor-based pagination, using real-world examples from GitHub and Twitter's APIs. They discuss why cursor-based pagination is often preferred for large datasets, how inconsistent pagination can break client code, and what developers should consider when choosing a strategy. The episode also covers common pitfalls like unstable ordering and the hidden costs of deep offsets. Specific data: GitHub's API defaults to 30 results per page with cursor-based pagination; Twitter's deprecated v1.1 API used offset-based pagination, leading to performance issues for high-volume queries. Hosts also touch on pagination's impact on mobile apps and GraphQL. A concise episode for engineers designing or consuming APIs. #API #Pagination #CursorBased #OffsetBased #DeveloperExperience #Performance #GitHub #Twitter #GraphQL #Backend #Frontend #APIArchitecture #WebDev #SoftwareEngineering #TechPodcast #Business #BusinessAndTechnology #FexingoBusiness Keep every episode free: buymeacoffee.com/fexingo

Episode 24 of The Developer Tools Podcast explores how API pagination design directly impacts both backend performance and frontend developer experience. Lucas and Luna break down the trade-offs between offset-based and cursor-based pagination, using real-world examples from GitHub and Twitter's APIs. They discuss why cursor-based pagination is often preferred for large datasets, how inconsistent pagination can break client code, and what developers should consider when choosing a strategy. The episode also covers common pitfalls like unstable ordering and the hidden costs of deep offsets. Specific data: GitHub's API defaults to 30 results per page with cursor-based pagination; Twitter's deprecated v1.1 API used offset-based pagination, leading to performance issues for high-volume queries. Hosts also touch on pagination's impact on mobile apps and GraphQL. A concise episode for engineers designing or consuming APIs. #API #Pagination #CursorBased #OffsetBased #DeveloperExperience #Performance #GitHub #Twitter #GraphQL #Backend #Frontend #APIArchitecture #WebDev #SoftwareEngineering #TechPodcast #Business #BusinessAndTechnology #FexingoBusiness Keep every episode free: buymeacoffee.com/fexingo

NOW PLAYING

How API Pagination Design Affects Performance and Developer Experience

0:00 9:29

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

Frequently Asked Questions

How long is this episode of The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers?

This episode is 9 minutes long.

When was this The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers episode published?

This episode was published on June 1, 2026.

What is this episode about?

Episode 24 of The Developer Tools Podcast explores how API pagination design directly impacts both backend performance and frontend developer experience. Lucas and Luna break down the trade-offs between offset-based and cursor-based pagination,...

Can I download this The Developer Tools Podcast with Fexingo: APIs, Infrastructure, and Software for Engineers episode?

Yes, you can download this episode by clicking the download button on the episode player, or subscribe to the podcast in your preferred podcast app for automatic downloads.
URL copied to clipboard!