# How discourse stays online (Message Bus, Faye, Long Polling)

**URL:** <https://meta.discourse.org/t/how-discourse-stays-online-message-bus-faye-long-polling/3238>\
**Category:** Development\
**Created:** [16 februari 2013 om 20:20 UTC](https://meta.discourse.org/t/how-discourse-stays-online-message-bus-faye-long-polling/3238 "2013-02-16T20:20:50Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![swilgosz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/swilgosz/32/244904_2.png) [@swilgosz](https://meta.discourse.org/u/swilgosz)\
**Post date:** [31 december 2021 om 08:09 UTC](https://meta.discourse.org/t/how-discourse-stays-online-message-bus-faye-long-polling/3238/26 "2021-12-31T08:09:41Z")

</div>

@sam From what I got by reading the README and this thread, `message_bus` seems to be a pure notification system (sth like a Pusher alternative)

Am I correct by saying, it’s not designed for implementing event sourcing in a distributed systems?

All examples here are rather related to short-term messaging catch-up, but it’s not possible to restore old app state from the events stream, due to the truncation mechanism. Is there anything I missed?

---

_[View the full topic](https://meta.discourse.org/t/how-discourse-stays-online-message-bus-faye-long-polling/3238)._
