flyctl VS libcluster

To begin with, you could go with a Platform-as-a-Service (PaaS) provider like Heroku, or Fly for a more seamless experience. You can also do a bit of DevOps: set up a Docker installation on a VPS and deploy your app there.

To begin visit fly.io to create an account. Next install flyctl a command line tool for creating and deploying fly apps. macOS

For frontend deployment, I used Netlify (for the generous free package) and the recommended fly.io for server + database (also cheap package).

Create an account on Fly.io.

You can learn more about fly.io and tigris, we will need to create an account on both platforms for this project regardless. Anyway with the theory out of the way let's get started in the next section as we create our accounts and start building the app.

Fly.io is a platform that helps you run your apps and databases closer to your users all around the world. It takes your app code, packages it up neatly, and puts it on virtual machines that can be quickly started or stopped. This makes your app faster for users and more reliable. Fly.io is easy to use, works well for small projects or personal apps. It's a great way to make sure your app runs smoothly for people no matter where they are.

In this post, we'll start from scratch, running FerretDB locally via Docker, trying out the connection with mongosh and the MongoDB Node.js client, and finally deploy FerretDB to Fly.io for a production ready set up.

2- fly.io

Fly is a cloud platform that focuses on global edge computing. Fly specializes in high-performance hosting and provides a global network of edge locations. Fly is known for its scalability and performance optimizations.

But videototextai.com is built using NextJS + Firebase auth + Firestore and a backend deployed at fly.io . Fly makes it really easy to deploy docker containers and that is IMO the fastest way to develop, you can setup a local setup

libcluster is the go-to package for connecting multiple BEAM instances and setting up healing strategies. libcluster provides out-of-the-box strategies and it allows users to define their own strategies by implementing a simple behavior that defines cluster formation and healing according to the supporting service you want to use.

I am using libcluster to connect my nodesI get the following error:

Distributed Elixir can be done with Docker containers too, see https://github.com/bitwalker/libcluster which by default has some Kubernetes support but you can also have third party (or custom) clustering strategies. I've not done this myself but I've seen articles about this a lot during the past years.

Hot code updates for most applications aren't really worth it in my opinion, assuming you do something like blue/green rollover deployments. It's cool that it's possible though. But it requires appup files and afaik Distillery is one of the release tools that has support for it built-in.

On the deployment level, you can use synchronous communication using API-based solutions or asynchronous communication using external solutions (RabbitMQ, Kafka,...) or Erlang/Elixir tools (message passing, pg2, PubSub, Libcluster,...)

Looking throught libcluster code (https://github.com/bitwalker/libcluster/blob/master/lib/strategy/kubernetes_dns.ex#L150) it does seem to require that both nodes share the same basename.

libcluster – Automatic cluster formation/healing for Elixir applications.