anuragg
We finally have a Mix clustering guide to go with Phoenix deployment with Mix Releases.
Deploy an Elixir Cluster with Mix Releases and libcluster
The finished code for the guide is available at GitHub - render-examples/elixir_cluster: Distributed Elixir Cluster on Render with libcluster and Mix Releases · GitHub.
Meta: the Mix team has done a wonderful job learning from Distillery and making it even easier to cluster nodes, especially on platforms like Render (where I work) because we can auto-populate clustering variables for you.
Where Next?
Trending in Guides/Tuts
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
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
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
tristan
How are you keeping separate customer’s Erlang clusters. K8s network policies? It would be good to add TLS usage to the tutorial.
anuragg
Yes, firewalling through network policies. Regarding SSL, we terminate TLS at our L4 load balancer. Do you need e2e TLS?
tristan
I mean TLS for distributed erlang so that all communication is encrypted. Erlang Distribution over TLS — OTP 29.0.2 (ssl 11.7.2)
anuragg
Makes sense. We’ll add a guide for it.
jwarren92
This is really great, anuragg! Say I have a horizontally distributed application with microservices sitting in other pods. To connect the main application to the microservices, would I just add multiple topologies for them to connect to each other?
If so, as Render uses IP instead of FQDN for the DNS resolution, how would I send messages to and from the different topologies? Since the IP isn’t guaranteed to be the same each time a service goes up and down, I can’t quite call
:rpc.call(node_name, :"Module", :function, [:"args"])orNode.spawn(:"servicename@127.0.0.1", :"Module", fun, args).How would you recommend passing messages between topologies in this situation?
anuragg
Each Render service gets a unique internal-only URL of the type
service-slug:port. You will see it on the dashboard once the service is deployed. You can connect to this URL from other services in your account; think of it as a built-in automatic VPC with preconfigured DNS. It sounds like this will work for your use case.