It's relatively easy to scale out stateless web applications. You often only need a reverse proxy. But for those stateful web applications, especially those applications that embeds websocket services in them, it's always a pain to distribute them in a cluster. The traditional way is introducing some external services like Redis to handle pubsub, however, in such way, you often need to change your code. Can Erlang/Elixir, the "concurrency oriented programming languages", best other languages in this use case? Has Phoenix framework already integrated the solution of horizontally scaling websocket? I'll do an experiment to prove (or disprove) that.
Aetherus
/ scale-out-phoenix-with-websocket.md
Last active
February 23, 2024 14:31
How to scale out a Phoenix application with websocket
Steps to deploy a Node.js app to DigitalOcean using PM2, NGINX as a reverse proxy and an SSL from LetsEncrypt
If you use the referal link below, you get $10 free (1 or 2 months) https://m.do.co/c/5424d440c63a
I will be using the root user, but would suggest creating a new user
Update all outdated dependencies in this Elixir project, handling both safe updates and breaking changes.
Run mix hex.outdated to get a list of all outdated dependencies. Parse the output to identify:
- Safe updates: Dependencies where only the patch or minor version has changed (no major version bump)