3 ms·
I use this architecture myself where there's an Erlang thing sitting in the center, dispatching relatively heavyweight jobs to Perl daemons waiting for them, an
by jerf 16y ago
I use this architecture myself where there's an Erlang thing sitting in the center, dispatching relatively heavyweight jobs to Perl daemons waiting for them, and it does work. That isolates all the "eventish" stuff in Erlang, and turns the Perl daemons into, well, basically webservers, in the sense that they are just serving stateless RPC answers synchronously. This definitely avoids the complexity explosion.
You don't need a project like Beam.js to do that, but having someone else having already written the utility code can certainly be useful. Nothing like that existed for Perl but it hasn't been hard to do what I needed.