anuragg
We just published a guide to automatic clustering in Elixir 1.9, with Mix releases and libcluster.
The cluster automatically discovers nodes as they join or leave, allowing you to scale by simply increasing the number of instances for your app. The source code is available at GitHub - render-examples/elixir_cluster: Distributed Elixir Cluster on Render with libcluster and Mix Releases · GitHub.
Trending in Guides/Tuts
# ~/src/livebook/.iex.exs
System.cmd("xdg-open", [ LivebookWeb.Endpoint.access_url() ] )
Because Livebook requires a unique passcode on ...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security











Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Most
Would it be a bad idea to deploy your app as a distributed cluster even though you won’t have much traffic to begin with? I understand “premature optimization is the root of all evil” but is having your app configured for distributed deployment an optimization decision or a design decision?
I wonder because I have a project that uses ETS tables and currently doesn’t get much traffic. But if I ever needed to scale it, I imagine I would have to use something like Mnesia instead.
mbuhot
No, it becomes valuable as soon as you have >1 instances for high availability. For example Phoenix channel broadcast and Phoenix presence will use clustering
for communicating between nodes.