OFOffline First · Open source
Community homeHot discussions Latest posts Best of Knowledge base Resources About

Offline First · Open source · Discussion: is the offline-first-opensource ecosystem being replaced by another stack?

14
OFr/offline-first-opensource·posted by kite·32 minutes agoTooling

Discussion: is the offline-first-opensource ecosystem being replaced by another stack?

Most offline-first-opensource articles stop at "how to use it" and never cover "when not to use it". This is an attempt at the second half.

On trade-offs, my view is this: if nobody on the team owns this area long-term, do not introduce a second mechanism. With two coexistence you first have to work out which one is even in play when things break, and that costs far more than the performance you saved.

Image placeholder · object storage in production
POST /api/uploads → CDN origin pull
5 comments

5 comments

M
Wwinter·2 hours ago

Sharing our numbers, 8 cores 16GB, same scenario:

| Concurrency | P50 | P99 |
|---|---|---|
| 200 | 12ms | 88ms |
| 500 | 31ms | 340ms |

P99 clearly collapses at 500 concurrency, which lines up with your knee point.

378
Nnikic·28 minutes ago

Worth learning from this debugging approach. We went straight at the logs and took a much longer route.

142
Hhuang_ke·3 minutes ago

There is actually a simpler fix that needs no architecture change: move this check up to the gateway and the problem disappears. The cost is one extra lookup at the gateway.

76
Hhuang_ke·just now

I see point 3 differently. The trade-off depends on your read/write ratio: read-heavy with little writing means caching actually widens the inconsistency window.

43
Nnikic·12 minutes ago

This matches what we see in production. We only hit it past 3k QPS; the earlier load tests showed nothing — the test traffic was too clean, with no long-tail requests.

11

This is the post detail page /en/c/offline-first-opensource/post/p10. Posts and comments are generated deterministically from a seeded PRNG, so the same post always renders the same content and the link can be shared, reloaded and indexed. In production this page reads MySQL for the post, Redis for hot-post caching, and fetches the whole comment tree in a single query on the path column.

See the database schema →