Ctrl K
Backend · Mid-level · Theory

How would you implement pagination in a feed API with millions of records where new ones are constantly being added? What options do you know, and how do they differ?

~4 min by voice

How to approach it

The interviewer checks whether the candidate understands why naive LIMIT/OFFSET pagination breaks on large, constantly changing data, and whether they can properly design keyset (cursor) pagination with all the details: a unique key, an index, the cursor format, the limitations.

Have you seen this question in a real interview?
Answers0
Avg. score—
Strong—
Practiced0
Topics
Similar questionsКак вы выстроите защиту API, через которое мобильное приложение получает данные о счетах клиента, — на всём пути от приложения до базы? SeniorDesign a rate limiter for a public API: for example, no more than 100 requests per minute per API key. The service runs on several instances. Mid-levelLet's say you need to build a REST API for a simple notes service. What endpoints would you create, and what would they look like? JuniorA client sends a POST request to create a payment, the response never arrives because of a timeout, and the client retries the request. How do you make sure the money isn't charged twice? Mid-levelYou have a public API used by hundreds of external integrations, and you need to change the format of a key resource in a backward-incompatible way. How would you go about it? Senior

Answer by voice

The interviewer will ask this question and listen. Think out loud and ask for a hint if you need one. When you're done, pause or tap “That's my answer”. In about a minute, your score and the points you covered show up here.

Sign in to answer

Best with headphones · ~4 min