You should try out all the options you listed and the other recommendations and find what works best for you.
I personally use Kubernetes. It can be overwhelming but if you’re willing to learn some new jargon then try a managed kubernetes cluster. Like AKS or digital ocean kubernetes. I would avoid managing a kubernetes cluster yourself.
Kubernetes gets a lot of flack for being overly complicated but what is being overlooked with that statement is all the things that kubernetes does for you.
If you can spin up kubernetes with cert-manager, external-dns, and an ingress controller like istio then you got a whole automated data center for your docker containers.
There are a few reasons I can think of that Lemmy is a better platform than ticktock.
ticktock uses an algorithm to drive engagement and keep users on the platform for as long as possible, recommending posts that it thinks the user will like or hate. Lemmy doesn’t do this.
I’ve never actually used ticktock so I’m not sure if it’s possible to block content in the same way but the ability to block users, communities, and entire instances is I think one of Lemmy’s best features.
there are no ads on lemmy.
Now for the content in question, my understanding is that it’s entirely user generated. Just like Lemmy, reddit, YouTube, Etc. It’s not like the Chinese government is making American women film themselves dancing and then forcing them to post it on ticktock. That’s just what that person wanted to make and post and ticktocks algorithm is recommending it.
With that being said, there are potentially useful, funny, or important content that might be uploaded to ticktock by a user, the same way that girl dancing video was. If that happened, wouldn’t make sense to move that content to a platform without many of the down sides of the ticktock platform?
I would say that if you are going to host it at home then kubenetes is more complex. Bare metal kubernetes control plane management has some pitfalls. But if you were to use a cloud provider like linode or digital ocean and use their kubernetes service, then only real extra complexity is learning how to manage Kubernetes which is minimal.
There is a decent hardware investment needed to run kubernetes if you want it to be fully HA (which I would argue means it needs to be a minimum of 2 clusters of 3 nodes each on different continents) but you could run a single node cluster with autoscaling at a cloud provider if you don’t need HA. I will say it’s nice not to have to worry about a service failing periodically as it will just transfer to another node in a few seconds automatically.
With a basic understanding of how k8s works and an already running cluster, all one needs to know is how to run a service as a docker file to have it also run in k8s
Well the kubernetes API has all the necessary parts built in mostly, although sometimes you may want to install a custom resource which often comes with complex service installs.
But I think the biggest strength of kubernetes is all the foss projects that are available for it. Specifically external-dns, cert-manager, and istio. These are separate projects and will have to be installed after the cluster is up.
Caution, not all cloud providers support istio. I know that Google’s GKS doesn’t, they make you use their own fork of it
I would also recommend you avoid helm if possible as it obfuscates what the cluster is doing and might make learning harder. Try to just stick to using kubectl if possible.
I have heard good things about nomad too but I have yet to try it.