4 ms·

I think that the $5 tier is a little tight for a web app as opposed to a crud app, but 2x $40 tiers is enough for a decent amount of traffic, with one as a fail

I think that the $5 tier is a little tight for a web app as opposed to a crud app, but 2x $40 tiers is enough for a decent amount of traffic, with one as a failover. The problem is that containers are excellent, and IMO there's a gap in the market between "I want to run one container" and "I want a fully managed k8s cluster"

alibarber 3y ago
For my personal projects (that right now seem to revolve around April 1st jokes for people in my industry) - I've found a good middle ground to be K3s on a single Hetzner VM that I scale up and down if I think more/less people are going to be looking at it (i.e. between the 5 - 10 dollar/month price range) I set this up with Terraform and some bash scripts. Infra as code is just too convenient to pass up on for something that I might not come back to for months at a time (and then ask - how did I set that up?), and containers too mean that I can play with some shiny fun technology one time, leave it in a box, and then come back to a clean-slate for the next thing that I want to play with without having to pay for a new VM etc.
- maccard 3y ago
  The other great thing about containers is that you can have entire isolated stacks for your projects, and you can stand the entire thing up with `docker compose up -d` in a matter of seconds. Gone are the days of accidentally connecting to the wrong database with WAMP.
mnahkies 3y ago
For my personal stuff that doesn't get any traffic I cobbled together some scripts to manage containers / SSL here https://github.com/mnahkies/shoe-string-server https://github.com/mnahkies/shoe-string-server I don't think I ever got around to making it self healing if a container dies, but it does support gitops style deployments through a cronjob / conf repo similar to argocd It's been running happily on a <$10 / month aws lightsail instance for a few years now, though tbh I'd still reach for k8s for anything serious
auspex 3y ago
Why not use a single Fargate task?
- maccard 3y ago
  All my teams infra runs on fargate + ECS so I'm pretty familiar (and happy) with it. Running in fargate requires knowlege of AWS: VPC's, public and private subnets, security groups, ECR, ALB's, Target Groups, IAM policies + roles. Then, when you want to add a databse, you're back into all of the above, plus the database specific ones like database subnet groups. When it comes to health checks you have docker health checks, container health checks, load balancer health checks - all of which are configured separately.a Not to mention, doing it "properly" where your task doesn't have a public IP and is only accessible through your load balancer - [0] might be one of the most infuriating responses on stackoverflow. Meanwhile, with DO droplets, it's pretty much "here's a registry URL, and some configuration in YAML, go for it". [0] - https://stackoverflow.com/questions/61265108/aws-ecs-fargate-resourceinitializationerror-unable-to-pull-secrets-or-registry https://stackoverflow.com/questions/61265108/aws-ecs-fargate...
KronisLV 3y ago
> The problem is that containers are excellent, and IMO there's a gap in the market between "I want to run one container" and "I want a fully managed k8s cluster" A single container: Docker A few containers on the same node: Docker Compose Containers across multiple nodes with load balancing and networking: Docker Swarm (with Portainer to manage it) Alternatively, Podman is also pretty nice. If you need something that runs not just containers in clusters: Hashicorp Nomad If you want to go for Kubernetes but without it being too hard: K0s or K3s or MicroK8s or RKE (with Portainer or Rancher to manage it)
- justsomehnguy 3y ago
  I found the hard way Swarm is better than Compose even on one node. Bonus point is what you can scale it easily with just a minor forethought.
  - pdimitar 3y ago
    Are you willing to share your lessons learned? I'm very curious.
- duckmysick 3y ago
  Does Podman have something like Docker Swarm? Last time I checked (a few years ago) there wasn't and the suggestion was to use kubernetes.

alibarber 3y ago

For my personal projects (that right now seem to revolve around April 1st jokes for people in my industry) - I've found a good middle ground to be K3s on a single Hetzner VM that I scale up and down if I think more/less people are going to be looking at it (i.e. between the 5 - 10 dollar/month price range) I set this up with Terraform and some bash scripts. Infra as code is just too convenient to pass up on for something that I might not come back to for months at a time (and then ask - how did I set that up?), and containers too mean that I can play with some shiny fun technology one time, leave it in a box, and then come back to a clean-slate for the next thing that I want to play with without having to pay for a new VM etc.

maccard 3y ago
The other great thing about containers is that you can have entire isolated stacks for your projects, and you can stand the entire thing up with `docker compose up -d` in a matter of seconds. Gone are the days of accidentally connecting to the wrong database with WAMP.

mnahkies 3y ago

For my personal stuff that doesn't get any traffic I cobbled together some scripts to manage containers / SSL here https://github.com/mnahkies/shoe-string-server https://github.com/mnahkies/shoe-string-server I don't think I ever got around to making it self healing if a container dies, but it does support gitops style deployments through a cronjob / conf repo similar to argocd It's been running happily on a <$10 / month aws lightsail instance for a few years now, though tbh I'd still reach for k8s for anything serious

auspex 3y ago

Why not use a single Fargate task?

maccard 3y ago
All my teams infra runs on fargate + ECS so I'm pretty familiar (and happy) with it. Running in fargate requires knowlege of AWS: VPC's, public and private subnets, security groups, ECR, ALB's, Target Groups, IAM policies + roles. Then, when you want to add a databse, you're back into all of the above, plus the database specific ones like database subnet groups. When it comes to health checks you have docker health checks, container health checks, load balancer health checks - all of which are configured separately.a Not to mention, doing it "properly" where your task doesn't have a public IP and is only accessible through your load balancer - [0] might be one of the most infuriating responses on stackoverflow. Meanwhile, with DO droplets, it's pretty much "here's a registry URL, and some configuration in YAML, go for it". [0] - https://stackoverflow.com/questions/61265108/aws-ecs-fargate-resourceinitializationerror-unable-to-pull-secrets-or-registry https://stackoverflow.com/questions/61265108/aws-ecs-fargate...

KronisLV 3y ago

> The problem is that containers are excellent, and IMO there's a gap in the market between "I want to run one container" and "I want a fully managed k8s cluster" A single container: Docker A few containers on the same node: Docker Compose Containers across multiple nodes with load balancing and networking: Docker Swarm (with Portainer to manage it) Alternatively, Podman is also pretty nice. If you need something that runs not just containers in clusters: Hashicorp Nomad If you want to go for Kubernetes but without it being too hard: K0s or K3s or MicroK8s or RKE (with Portainer or Rancher to manage it)

justsomehnguy 3y ago
I found the hard way Swarm is better than Compose even on one node. Bonus point is what you can scale it easily with just a minor forethought.
- pdimitar 3y ago
  Are you willing to share your lessons learned? I'm very curious.
duckmysick 3y ago
Does Podman have something like Docker Swarm? Last time I checked (a few years ago) there wasn't and the suggestion was to use kubernetes.