# Understanding supervisor

**URL:** <https://forum.elixirforum.com/t/understanding-supervisor/6174>\
**Category:** Questions\
**Tags:** otp, design-problem, deployment\
**Created:** [June 18, 2017, 10:17pm UTC](https://forum.elixirforum.com/t/understanding-supervisor/6174 "2017-06-18T22:17:00Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![peerreynders](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/peerreynders/32/5826_2.png) [@peerreynders](https://forum.elixirforum.com/u/peerreynders)\
**Post date:** [June 18, 2017, 10:52pm UTC](https://forum.elixirforum.com/t/understanding-supervisor/6174/7 "2017-06-18T22:52:26Z")

</div>

Supervisor _is_ an OTP concept. The load balancing between nodes is the responsibility of the BEAM. [RabbitMQ is an OTP application](http://www.rabbitmq.com/resources/erlang-exchange-talk-final/ex.html) (unless you are talking about the BEAM process mailboxes - the mailbox is an integral part of any BEAM process while the BEAM handles the details of message routing between BEAM processes).

---

_[View the full topic](https://forum.elixirforum.com/t/understanding-supervisor/6174)._