Design Host-Guest Messaging

Host-guest messaging is one of the recurring Airbnb design prompts, usually posed as a real-time chat between a guest and a host, sometimes with a few more people on the thread. It is a chat system, so the familiar pieces show up: a persistent connection, real-time delivery, durable history, read receipts. What makes it an Airbnb question rather than a WhatsApp question is that every thread hangs off a reservation or an inquiry. The message is part of the booking itself, and that single fact reshapes the requirements.

Anchor the scale before anything else, because it points the design somewhere surprising. Airbnb messaging volume is bounded by the booking funnel. Roughly a million-plus reservations a day, plus several times that in inquiries that message but never book, gives a few million active threads a day. Each trades maybe ten messages over its life. Call it ~100 million messages a day. Spread across the day that is only about 1,200 messages a second, peaking maybe four times that in the busy evening planning hours. That is a modest write rate. Raw throughput is the easy part. The hard part is keeping every message safe, delivering it in order, and reading every word for safety.

The Airbnb angle

Messaging is the trust surface of the whole booking funnel, so it scores as a product problem first and a throughput puzzle second. A guest asks "is the neighborhood safe at night, can I check in late" before they spend two thousand dollars, and the booking often lives or dies on that exchange. Keep the guest and the host in frame the whole way through. Walk in with a WhatsApp answer that fans out millions of messages a second but treats the thread as anonymous text, and you've solved the wrong problem cleanly.