# pagination Published articles for pagination. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 【kube-apiserver】List、Pagination 与一致性 List：continue token 与 etcd Range 成本 DevFeed: [【kube-apiserver】List、Pagination 与一致性 List：continue token 与 etcd Range 成本]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [API](), [Cache](), [version]() Tags: [410-gone](), [apiserver](), [cacher](), [continue-token](), [distributed](), [etcd](), [etcd-range](), [http](), [kubernetes](), [limit](), [list](), [pagination](), [range](), [resourceversion](), [v1-30-3]() ### AI overview This article examines Kubernetes v1.30.3 List pagination in kube-apiserver, explaining continue-token semantics, limit-and-continue etcd Range behavior, resourceVersion consistency, and the different costs of cacher and etcd3 paths. It also explains how label and field selectors affect scanning and filtering. ### Source excerpt 钉 Kubernetes v1.30.3 List 分页的 continue token 编码语义、limit+continue 多轮 etcd Range 行为、resourceVersion 对一致性语义的影响，以及 label/field selector 在 cacher 与 etcd3 路径上的不同成本。 ## kube-apiserver / Kubernetes 控制面内核：storage、cacher、Admission 与 APF DevFeed: [kube-apiserver / Kubernetes 控制面内核：storage、cacher、Admission 与 APF]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [etcd](), [Caching](), [API](), [site-reliability-engineering](), [Authentication](), [Authorization](), [rbac]() Tags: [admission](), [apf](), [apiserver](), [authentication](), [authorization](), [cacher](), [control-plane](), [distributed](), [etcd](), [kubernetes](), [oidc](), [pagination](), [plan](), [rbac](), [resourceversion](), [storage](), [v1-30-3](), [watch](), [watch-cache](), [webhook]() ### AI overview This article introduces a 16-part series on the kube-apiserver production request path, covering storage.Interface and etcd3, resourceVersion, watch cache behavior, List and Watch operations, Admission and Webhooks, authentication, authorization, auditing, APF, and extension boundaries. It explains how to distinguish failures across these layers and when to investigate kube-apiserver instead of directly querying etcd. The discussion is anchored to Kubernetes v1.30.3 and etcd v3.5.33, with experiments explicitly noted as not yet run. ### Source excerpt 补齐 etcd 系列 K8s 耦合篇之上的 kube-apiserver 生产内核：storage.Interface、watch cache、resourceVersion、Admission/Webhook、APF，并以排障与相对 etcd 的分层收束。 ## 【kube-apiserver】resourceVersion 与 Revision 映射：mod revision、continue 与一致性读期望 DevFeed: [【kube-apiserver】resourceVersion 与 Revision 映射：mod revision、continue 与一致性读期望]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [API](), [Caching]() Tags: [410-gone](), [api](), [apiserver](), [cache](), [consistency](), [continue-token](), [distributed](), [etcd](), [kubernetes](), [pagination](), [resourceversion](), [revision](), [v1-30-3](), [watch]() ### AI overview This article explains how Kubernetes resourceVersion maps to etcd mod_revision, including the different semantics for individual objects and List responses. It covers Watch starting points, continue-token pagination and its costs, compaction-related 410 Gone errors, and consistency differences between watch-cache and etcd read paths. The discussion is anchored to Kubernetes v1.30.3 and etcd v3.5.33. ### Source excerpt 钉 Kubernetes resourceVersion 字段与 etcd mod revision 的对应关系；分析 continue token 的分页语义与成本；说明不同 List 路径的一致性期望差异；以及 410 Gone 与 ErrCompacted 的分列。版本锚定 Kubernetes v1.30.3 / etcd v3.5.33。 ## Pagination at Scale: Why OFFSET and SKIP Will Eventually Break Your API DevFeed: [Pagination at Scale: Why OFFSET and SKIP Will Eventually Break Your API]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-17T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [API](), [Database](), [MongoDB]() Tags: [api](), [api-design](), [b-tree](), [cursor](), [database-performance](), [latency](), [mongodb](), [pagination](), [scalability](), [scale](), [sql]() ### AI overview This article explains why OFFSET and SKIP pagination become slower and more memory-intensive as page depth increases. It presents cursor-based, or keyset, pagination as an alternative that uses an indexed range seek and reads a fixed number of rows, keeping fetch cost largely constant with list depth. The trade-off is that cursor pagination does not provide reliable absolute page numbers. ### Source excerpt OFFSET does not seek. The engine fetches offset plus limit rows, sorts them, and discards the first N, so cost grows linearly with page depth. Cursor pagination passes the last seen key instead of a page number, letting the B+ tree seek in logarithmic time and read a fixed number of rows, which keeps latency flat at any depth. The price is losing absolute page numbers. ## Year in Review: 2024 DevFeed: [Year in Review: 2024]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2025-03-27T00:00:00Z Content type: article Language: en Sources: [Tania Rascia]() Topics: [coding](), [CSS](), [React](), [Web Development](), [Web platform]() Tags: [bluesky](), [burnout](), [career](), [coding](), [css](), [hooks](), [keyboard](), [meta](), [pagination](), [projects](), [react](), [redesign](), [review](), [side-projects](), [sorting](), [table](), [variables](), [year-in-review]() ### AI overview A 2024 year-in-review from a principal engineer who continues to work primarily with React and CSS. The author reflects on balancing a full-time engineering role with coding, writing, side projects, and maintaining a personal website, while highlighting several articles and a blog redesign completed during the year. ### Source excerpt I'm trying to win the award for "Latest Year in Review". 🏆 I don't know if anyone can challenge me at this point, as it's almost thirdway... ## Using the Temporal CLI DevFeed: [Using the Temporal CLI]() Original publisher: [Read original article]() Author: Loren Sands-Ramshaw Published: 2023-04-27T04:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Command-line interface](), [Development](), [Server]() Tags: [aliases](), [auto-completion](), [bash](), [cli](), [command-line](), [commands](), [development](), [docs](), [download](), [environment](), [how-to](), [json](), [pagination](), [server](), [temporal-concepts]() ### AI overview A tutorial on using the Temporal CLI to install the tool, run and interact with a Temporal Server, configure environments and aliases, enable shell completion, and understand changes when upgrading from the previous CLI. ### Source excerpt How to use the Temporal CLI to run a development version of the Temporal Server and interact with it. ## Challenge Accepted: Transposit DevFeed: [Challenge Accepted: Transposit]() Original publisher: [Read original article]() Published: 2019-04-23T07:09:26Z Content type: tutorial Language: en Sources: [Jessie Frazelle]() Topics: [API](), [Code](), [GitHub](), [SQL](), [Bot]() Tags: [api](), [bots](), [code](), [github](), [graphql](), [join](), [pagination](), [query](), [sql]() ### AI overview The author describes testing Transposit's SQL interface for combining multiple APIs, using a GitHub bot that syncs issues and pull requests to Airtable as a complex example. ### Source excerpt Last week, I had the pleasure of meeting with the Transposit team in San Francisco. Tech is a super small world and it turns out the two founders and I are separated by one-degree through several different people we know. In meeting them I closed many loops without even realizing it, but I digress... Their product is really cool, it exposes a SQL interface for interacting with numerous APIs at once. For someone like myself who deploys a lot of bots, this is great. Usually when I have a complex bot I end up writing a lot of "glue code" to combine a few different APIs and get the information I want. Most of my bots have some sort of pagination logic and all have the N+1 problem where I don't really optimize my queries or use anything fancy like graphQL. Many APIs don't even have graphQL interfaces but also I am old school and I don't really want to learn something new. This is why I was super intrigued by Transposit's SQL interface, because hey, I know SQL! Adam, the CEO, challenged me to try it out, give them feedback, and see if I could break it with something complex. I am not one to back down from a challenge and I have some super weird ass bots, so I decided to start with the weirdest. Gitable Gitable is a bot I made for sending all my open issues and PRs on GitHub to a table in Airtable. I fucking love Airtable. It's design just feels right and works the way my brain works. I set out to make this bot work in Transposit because I know it has some super weird loops and has the N+1 problem where I loop over all my repos, then make another API call after. To reiterate, the goal of the bot is to iterate through all my repos on GitHub and sync the list of issue and PRs with a table in Airtable. Query all the user's repos First, I need to get all my repos that are not forks. So I need a SQL query for this, in Transposit it looks like this: SELECT name, full_name FROM github.list_repos_for_user WHERE username=@owner AND type='owner' AND fork=false The github.list_repos_fo ## Custom Jekyll pagination DevFeed: [Custom Jekyll pagination]() Original publisher: [Read original article]() Author: Stanko Published: 2016-02-22T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Jekyll](), [Code]() Tags: [code](), [custom](), [gist](), [jekyll](), [pagination]() ### AI overview This tutorial describes customizing Jekyll pagination to show at least five page links with the current page centered, plus first and last page links on larger screens while retaining Newer and Older links. It points readers to the implementation code and a screenshot. ### Source excerpt Please note that I'm not using Jekyll anymore, so this post might be outdated. Jekyll comes with simple pagination which has only Newer and Older links. I wanted a little bit more, now pagination shows at least five pages, with current in the middle. On the larger screens there are also first and last page links. Newer and Older links are, of course, still there. Check the gist with the code. You can see it at the bottom of this website, or just check the screenshot below: