3 ms·

Why is upvoted so much. This just touches the surface. Although, I am not very related to PaaS, I know much more for the three of the methods listed. This even

Why is upvoted so much. This just touches the surface. Although, I am not very related to PaaS, I know much more for the three of the methods listed. This even oversimplifies so many things, to the point of getting it wrong. > WHEN TO CHOOSE DOKKU: for hobby and side projects that do not require high availability Surely, not correct. Don't make your decision on this line. It's not made for fault tolerance, but anyone who has doubts regarding which to use is very likely to use a single region of single cloud provider. I think most companies(even large one) do that. > Big caveat (for Kubernetes): it is very hard to setup I really don't think he did that. It's really easy for AWS at least. See https://kubernetes.io/docs/getting-started-guides/aws/ https://kubernetes.io/docs/getting-started-guides/aws/ > WHEN TO CHOOSE DOCKER SWARM: in my opinion, this has a very strong potential to be a contender against current solutions mentioned above but as of right now, it is still evolving. AFAIK, it has been extensively tested and is being used live. I am not sure, but the amount of presence it has, it's hard to believe that it is just evolving and not to be used.

deforciant 9y ago
Swarm is used but I have heard many companies migrating from swarm to k8s and openshift. Swarm is just unstable, network connectivity is flaky, not sure how can you run it in prod (maybe you can't?). As for k8s - would recommend it for anything from hobby projects to large prod deployment. Easy to set up anywhere. This article is indeed very shallow and clearly author hasn't bothered to do some research.
- likelynew 9y ago
  > This article is indeed very shallow and clearly author hasn't bothered to do some research. Well, yeah, but the thing concerning here is HN upvoted it to the top. I have nothing against the author. > As for k8s - would recommend it for anything from hobby projects to large prod deployment That's what I am saying. IMO, the reputation that it has to be used only if somewhat wanted to manage very large number of servers is a little misleading. I think Kubernetes can feel very intimidating at the start but it's not that hard.
  - bryanlarsen 9y ago
    Just today I spun up a single node Kubernetes production cluster. Obviously not its sweet spot, but the ecosystem, flexibility and tooling made it an appropriate choice, given that I already know Kubernetes and that I'll be deploying the same software elsewhere on "real" clusters.

deforciant 9y ago

Swarm is used but I have heard many companies migrating from swarm to k8s and openshift. Swarm is just unstable, network connectivity is flaky, not sure how can you run it in prod (maybe you can't?). As for k8s - would recommend it for anything from hobby projects to large prod deployment. Easy to set up anywhere. This article is indeed very shallow and clearly author hasn't bothered to do some research.

likelynew 9y ago
> This article is indeed very shallow and clearly author hasn't bothered to do some research. Well, yeah, but the thing concerning here is HN upvoted it to the top. I have nothing against the author. > As for k8s - would recommend it for anything from hobby projects to large prod deployment That's what I am saying. IMO, the reputation that it has to be used only if somewhat wanted to manage very large number of servers is a little misleading. I think Kubernetes can feel very intimidating at the start but it's not that hard.
- bryanlarsen 9y ago
  Just today I spun up a single node Kubernetes production cluster. Obviously not its sweet spot, but the ecosystem, flexibility and tooling made it an appropriate choice, given that I already know Kubernetes and that I'll be deploying the same software elsewhere on "real" clusters.