Re:Learning Go as a Node.js Developer
by mzzter on Friday February 09, 2018 @12:16AM
(#16338060)
Scaling parts of the application independently from each other. If traffic spikes in one part of the application (e.x.: your image categorization web app was posted in a cat forum) more nodes can be added to that one resource to handle the load. Another reason could be worker processes that ran intermittently at midnight every day (e.x.: to email users top pics they missed that day).
[ Parent
| on HN ]
Re:Learning Go as a Node.js Developer
by briankelly on Friday February 09, 2018 @02:22AM
(#16338526)
Isn't that the whole point of the Erlang/Elixir/OTP actor model and BEAM VM? It seems like many systems with microservice architecture are reinventing that wheel only worse - except in the cases where the system needs to use legacy or polyglot services.