undefined | Better HN

0 pointsteaearlgraycold2y ago0 comments

It's a managed service. You pay a premium for it. Features like their blueprint file make it worth the price IMO - https://render.com/docs/blueprint-spec

If you are working on a team and you want everyone to be able to spin up a copy of the production infrastruction for each pull request then PaaS is the way to go. If you just have some random one-off production environment and you are happy to either manage the state of a HDD or a k8s cluster yourself (which comes down to will more so than skill) then DO is the way to go.

0 comments

8n4vidtmkvmk2y ago

> It's a managed service. You pay a premium for it. Features like their blueprint file make it worth the price IMO - https://render.com/docs/blueprint-spec

Looks like k8s yaml.

> If you are working on a team and you want everyone to be able to spin up a copy of the production infrastruction for each pull request then PaaS is the way to go.

But I get that with k8s + docker too. Everything's containerized. Just run the config, it even brings up the cron jobs.

> or a k8s cluster yourself (which comes down to will more so than skill) then DO is the way to go.

Yeah...that's the rub. Takes a few weeks to learn. Worth the time cost to save the $ cost and vendor lock in IMO.

teaearlgraycoldOP2y ago

> Takes a few weeks to learn.

As I said, there’s more of a issue of wanting to maintain your infra than knowing how to.

j / k navigate · click thread line to collapse