https://blog.yusukeikoma.com/tags/realtime/Recent content in realtime on Ikoma's BlogHugoen-usSat, 19 Sep 2026 21:10:16 +0900https://blog.yusukeikoma.com/posts/push-notifications-are-hints-apns-stores-one/Sat, 19 Sep 2026 21:10:16 +0900https://blog.yusukeikoma.com/posts/push-notifications-are-hints-apns-stores-one/Apple and Google both document what happens to a push when the device is offline, the app is killed or the sender is too chatty: messages are replaced, dropped, reordered or delayed. A table of those documented failure modes, and a small simulation showing that a client which pulls from a cursor converges where a client which applies push payloads does not.https://blog.yusukeikoma.com/posts/websocket-bufferedamount-backpressure/Sun, 06 Sep 2026 20:54:24 +0900https://blog.yusukeikoma.com/posts/websocket-bufferedamount-backpressure/WebSocket send() never waits, and bufferedAmount only sees the part of the path that is in your own process. In a small lab, a sender that politely waited for bufferedAmount to drain still let a slow consumer queue nearly all 400 messages in its own memory, while a credit window of 8 kept the backlog at 8. This post goes through four common beliefs about send(), bufferedAmount, message size and backpressure, tests each one, and ends with a table for choosing between them.https://blog.yusukeikoma.com/posts/resumable-streams-cursors-last-event-id-snapshots/Fri, 04 Sep 2026 19:26:37 +0900https://blog.yusukeikoma.com/posts/resumable-streams-cursors-last-event-id-snapshots/How a client catches up after a reconnect without losing state, without duplicates, and without re-reading history. Built in steps (versions 0 to 4), from “read everything again” to a bounded log with a snapshot fallback, with what a real browser’s EventSource does on reconnect and on a non-200 response, a snapshot-ordering bug, and a decision tree.https://blog.yusukeikoma.com/posts/level-triggered-invalidation/Tue, 25 Aug 2026 17:33:01 +0900https://blog.yusukeikoma.com/posts/level-triggered-invalidation/epoll’s edge-triggered mode stalls after a partial read; level-triggered mode cannot. The same distinction decides whether a realtime client survives lost, duplicated and reordered events. A reproducible epoll experiment, a five-way simulation on a lossy channel, and a 40-line invalidator that handles the race everyone misses: an event that arrives while the refetch is running.https://blog.yusukeikoma.com/posts/replace-polling-with-subscriptions-keep-poll-as-fallback/Thu, 20 Aug 2026 18:03:49 +0900https://blog.yusukeikoma.com/posts/replace-polling-with-subscriptions-keep-poll-as-fallback/How a mobile client moved from timer-driven polling to shared change subscriptions over a per-message-billed relay. The subtle part is not the stream. It is deciding honestly when the fallback poll may stand down.https://blog.yusukeikoma.com/posts/live-document-and-saved-copy/Thu, 13 Aug 2026 10:14:09 +0900https://blog.yusukeikoma.com/posts/live-document-and-saved-copy/Designing collaborative document editing with conflict-free synchronization, saved snapshots, and safeguards against overwriting content before initial sync.