Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea...
by mati365 on Wednesday November 06, 2024 @04:58PM
(#42070132)
Why not? Install trafeik or any other load balancer, setup two services, and restart one after one.
[ Parent
| on HN ]
Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea...
by striking on Wednesday November 06, 2024 @06:14PM
(#42071042)
https://kamal-deploy.org/docs/configuration/proxy/
I think GP's point was that Kamal has all of these things already, so you don't have to set them up.
Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea...
by ngrilly on Thursday November 07, 2024 @12:31PM
(#42078821)
Precisely. I've been implementing some kind of blue-green deployment with both systemd and dockerd, but it was an imperfect and incomplete solution. Kamal put much more effort into it and it seems more convenient and reliable (but I haven't tried it yet in production).
Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea...
by FridgeSeal on Wednesday November 06, 2024 @06:06PM
(#42070971)
Ah yes my favourite thing to have to do, rolling my own deploys and rollbacks.
It’s stuff like this that’s just a thousand papercuts that dissuades me from using these “simpler” tools. By the time you’ve rebuilt by hand what you need, you’ve just created a worse version of the “more complex” solution.
I get it if your workload is so simple ir low requirement that zero-downtime deploys, rollbacks, health/liveness, automatic volumes, monitoring etc are features you don’t want or need, but “it’s just as good, just DIY all the things” doesn’t make it a viable alternative in my mind.
Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea...
by stackskipton on Wednesday November 06, 2024 @07:27PM
(#42071777)
Sure but Kumal getting all those features means it strays close to Kubernetes in complexity and it quickly because "Why not Kubernetes? At least that is massive popular with a ton of support."