When a list endpoint starts returning too many rows, the first question is usually "offset or keyset?" That question comes second. The first is: can the pagination strategy change later without breaking a single client? If the answer is no, the SQL is the smaller decision, because the response shape has already locked you in. This guide is a decision analysis for C#, SQL Server and REST APIs, built on documentation from Microsoft. No benchmarks are claimed. Paging is a contract change before it is a query change Microsoft's API guidance recommends supporting paging whenever a collection could grow large, and Azure's own API tooling notes that designing pagination up front avoids a later breaking change when continuation links have to be added. That matches how clients behave. A client handed a bare array has no way to know a second page exists, so it silently processes a truncated list. Three criteria, in order: Can the client discover that more data exists? ...
Can a bucket be your system of record? The answer depends on which failure you are worried about. Eleven nines of durability answers "will the bytes survive hardware loss?" It says nothing about two writers racing on one key, or a job that overwrites last night's good file with tonight's bad one. This guide separates those failures and maps each to an S3 control, based on AWS documentation. Four questions decide it, and durability answers only one Before choosing S3 over a database, ask: Will stored bytes survive infrastructure failure? The durability question. Will a reader see the latest write? The consistency question. When two writers collide, who wins, and does the loser find out? The concurrency question. Can a person or a buggy job destroy good data, and can it be recovered? The retention question. S3 answers the first two by default. The last two are answered only if you configure or code for them. That gap is why "S3 is a database" i...