# Distributed application - network split

**URL:** <https://forum.elixirforum.com/t/distributed-application-network-split/10007>\
**Category:** Questions\
**Tags:** erlang, distributed-systems\
**Created:** [November 10, 2017, 3:50pm UTC](https://forum.elixirforum.com/t/distributed-application-network-split/10007 "2017-11-10T15:50:38Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![hubertlepicki](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/hubertlepicki/32/6822_2.png) [@hubertlepicki](https://forum.elixirforum.com/u/hubertlepicki)\
**Post date:** [November 12, 2017, 8:25pm UTC](https://forum.elixirforum.com/t/distributed-application-network-split/10007/12 "2017-11-12T20:25:46Z")

</div>

> [@cs-victor-nascimento](#):
>
> That’s because the BEAM is one of the single preemptive scheduling systems I’ve ever seen

That’s correct but often the heavy workers I have “pleasure” to work with are not confined within BEAM. Every time they do video or image processing, or spawning headless crawling web browsers for example - either external binaries or external C libraries are called and this actually has an impact on the rest of the system.

This is in fact the reason why the worker nodes would ideally be isolated.

---

_[View the full topic](https://forum.elixirforum.com/t/distributed-application-network-split/10007)._