I am new to backend development, with no idea about how tough it is deploy manually.
And I don’t like Docker and other complexity that follows it.
I prefer the baremetal deployment and beam would take care of not crashing.
It took me a long time to deploy, and setup GitHub action for deployment to Linode.
Securing the Linode instance took effort, SSL certificate for the domain and subdomains was a breeze thanks to Caddy, but securing Cockroach DB and any other service I think about deploying would have taken even more of my time.
Plus it is geo restricted. Nodebalancer wont route traffic to nearest Server.
So I keeping complexity and Anycast in mind, I jumped to Fly.io.
I liked the idea of fly. I saw Chris Mccord deploy with just one command.
Which failed for me. I guess they are still migrating away from consul, that’s causing a bottleneck or maybe something else.
I was unable to make it work, and didn’t have the energy to reach out to their support.
Plus I don’t need GDPR compliance at the moment. I don’t have any data or plan to create something immediately that will need that.
So I moved to render, which was a breath of fresh air.
Deployment was as easy as using Netlify! Managed Postgres is confidence inspiring.
I did get blocked due to lacking documentation, that didn’t point out where to put Elixir and Erlang version.
But it is faster than manually SSHing into Linode or setting up GitHub action or securing and backing up Cockroach.
I haven’t given up on Linode and Fly.
Will try them soon, once I have projects that need them.
Like running Bumblebee serving, on Linode. Or low latency dashboards in Fly.