I believe this is happening because Coolify has chosen to cater to those who "require" redundancy. It's a respectable choice, but in my opinion single (maybe beefy) node is what most indie hackers need (and should stick to)
100% agree. Most people do not need this extra crap, just deploy one VPS and put your apps on it. That was the point I was trying to make in my blog post as well.
Have not tried k0s - there are a few of these "kubernetes but simpler" tools that all attempt to prepackage k8s into an installer and make it more efficient. k0s appears to be a bit more customizable, but by default probably has the same issues I pointed out with k3s.
I think k3s/k0s are good tools if you need horizontal scaling - but seeing as:
1) Most people do not need horizontal scaling, at least not in the beginning
2) Dokku supports k3s as a scheduler: dokku.com/docs/deployment/sch…
=> You can just start off with Dokku + local docker scheduler and later change the scheduler to k3s globally or per app as needed.
In my opinion multi-node and elastic scaling has been way overblown over the last years of AWS/GCP/Azure marketing campaigns. They did a good job though 🤣
Haha yep. I think we also have to keep in mind that server hardware has continued to get better and better, which has made horizontal scaling less and less necessary.
So probably 50% marketing hype and 50% moore's law :)
I believe this is happening because Coolify has chosen to cater to those who "require" redundancy. It's a respectable choice, but in my opinion single (maybe beefy) node is what most indie hackers need (and should stick to)
100% agree. Most people do not need this extra crap, just deploy one VPS and put your apps on it. That was the point I was trying to make in my blog post as well.
It totally resonates with me. I especially appreciated the sane defaults subsection.
And wow, I didn't expect k3s to take nearly 15% of ram! I haven't used it in a while, maybe it got bloated?
Btw, have you tried k0s?
Thanks for the kind words! Glad you liked it.
Have not tried k0s - there are a few of these "kubernetes but simpler" tools that all attempt to prepackage k8s into an installer and make it more efficient. k0s appears to be a bit more customizable, but by default probably has the same issues I pointed out with k3s.
I think k3s/k0s are good tools if you need horizontal scaling - but seeing as:
1) Most people do not need horizontal scaling, at least not in the beginning
2) Dokku supports k3s as a scheduler: dokku.com/docs/deployment/sch…
=> You can just start off with Dokku + local docker scheduler and later change the scheduler to k3s globally or per app as needed.
Totally on the same page, I was just curious.
In my opinion multi-node and elastic scaling has been way overblown over the last years of AWS/GCP/Azure marketing campaigns. They did a good job though 🤣
Haha yep. I think we also have to keep in mind that server hardware has continued to get better and better, which has made horizontal scaling less and less necessary.
So probably 50% marketing hype and 50% moore's law :)