# \[Redis\] How are MessageBus and Redis working

**URL:** <https://meta.discourse.org/t/redis-how-are-messagebus-and-redis-working/90229>\
**Category:** Development\
**Created:** [6월 19, 2018, 4:37오후 UTC](https://meta.discourse.org/t/redis-how-are-messagebus-and-redis-working/90229 "2018-06-19T16:37:05Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\
**Post date:** [6월 19, 2018, 6:00오후 UTC](https://meta.discourse.org/t/redis-how-are-messagebus-and-redis-working/90229/2 "2018-06-19T18:00:16Z")

</div>

MessageBus and Redis serve very different purposes.

Redis is an in-memory database, used to store state on the server that is more or less volatile. Some examples are scheduled jobs, session data, rate limiting data, …

MessageBus is a system that is used to push messages to the client. For example, if you’re on Discourse while someone replies here, you’ll see a blue number appear an your avatar immediately – that piece of information was sent from the server to your browser through MessageBus.

---

_[View the full topic](https://meta.discourse.org/t/redis-how-are-messagebus-and-redis-working/90229)._