Designs by Duhart All demos

Interactive demo · Designs by Duhart

One chat protocol, with a socket you can pull

Send a message, then drop the socket. The store keeps accepting writes, the transport queues them, and the runtime flushes the queue in order on reconnect. The UI never waits on the network.

interactive
# engineeringsocket open
  1. did the relay ever catch up after the restart?
  2. yeah, lag was the outbox, not Kafka. 40s to drain.✓ acked
  3. so the consumer groups were fine the whole time

The client half of project 2. The web tier splits transport, store and runtime so the socket can drop and reconnect without the UI knowing. The message above goes optimistic first, then reconciles against the server ack.