2 ms·
> This unfortunately breaks down with (bad acting) NIFs. Where possible, I think the Erlangy thing to do would be to just have a separate executable and commun
by davidw 11y ago
> This unfortunately breaks down with (bad acting) NIFs.
Where possible, I think the Erlangy thing to do would be to just have a separate executable and communicate with that. Also ensures that things keep running if there's a segfault or something.
- devbug 11y agoExactly! Well, kinda. You can always throw the NIFs onto other nodes. You can also write ports that are glorified external processes. Other times, you just need low-latency and high throughput. In that case, you expect failure and design accordingly.