|
|
|
|
|
|
by 8n4vidtmkvmk
1153 days 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. |
|
|
As I said, there’s more of a issue of wanting to maintain your infra than knowing how to.