Live data from Hacker News

Render: a Zero DevOps Cloud Platform

render.com

81–90 of 127 posts

Re: Render: a Zero DevOps Cloud Platform

#81

Earlier quoted context omitted.

Why people choose to write CI pipelines in Yaml as a living (aka DevOps Engineer) I will never understand. Its horrible.

It's the easiest part of my job. It's just YAML indicating steps. Each step is a "thing to do". There's really no magic to it or terror or discomfort.

It’s loosely typed, you don’t know what parts are compatible or incompatible with one another, you can’t test without deploying to CI and seeing the results, the syntax sucks, the white space sucks, etc etc.

Re: Render: a Zero DevOps Cloud Platform

#82

Does anyone on HN have first person experience with Render? Their offering certainly looks great on paper. I'd specifically be interested in your experience with regards to: - Stability / Uptime - How well the management UI / API / tools work - Any services you found you needed but aren't yet offered - Compliance with data protection regulations

I just listened to an the Syntax podcast where it’s a pain to setup cloudflare for Render

I have ~10 websites / web apps with Render + Cloudflare and setting up cloudflare proxying for render is super easy.

You can even proxy * domains (i.e. requests for *.foo.com going to a single render server / ip address).

Re: Render: a Zero DevOps Cloud Platform

#83

The only killer feature missing from Render is a distributing the same app across regions for minimal latency. Heroku only pitifully support 2 regions. I want the choice for my app to be global on day one with no devops required. Just two clicks and it's available on multiple regions.

Check out fly.io as that is their raison d’être.

Re: Render: a Zero DevOps Cloud Platform

#84

Please rename to: "Hosted Redis" Right now it sounds as if it's a redis competitor, aka clickbait

I agree, and unclear why you're being downvoted. From the title I thought that Render must be a database company that built a database protocol-compliant with Redis. It took a while of searching around their blog, github, and careers page to understand that isn't what they do. They are a hosting provider.

Generally “me too” HN comments are frowned upon, but I also clicked because I thought this was a rewrite of a redis-compatible offering that perhaps offered something like zero-click sharding or something.

Re: Render: a Zero DevOps Cloud Platform

#85

* Does Render work for Java (e.g. Spring Boot, Quarkus)? "All Your Apps" but I don't even see Java logo. * How does it different than new "lightweight" cloud offering like Fly.io?

If you can write a Dockerfile for your Java app, it can run on Render without issues.

Re: Render: a Zero DevOps Cloud Platform

#86

Earlier quoted context omitted.

Why people choose to write CI pipelines in Yaml as a living (aka DevOps Engineer) I will never understand. Its horrible.

1000 euro/day, tiny workload, endless stream of work available? Horrible indeed. ;)

>1000 euro/day

Where and how does one get 1000 euro/day as a DevOps Engineer?

Re: Render: a Zero DevOps Cloud Platform

#87
post #22

I'm excited to see a solid competitor to Heroku. While I trust Heroku due to using it for so long, they have become complacent with pricing and features. For example, affordable autoscaling looks awesome.

https://render.com/render-vs-heroku-comparison is a good page on this. It totally sold me on the idea recently.

That's great. They make good points on securing databases as well. Everything has to be open with Heroku's basic dynos. It would be nice to secure PostgreSQL or Elasticsearch so the IP is not publicly available.

Re: Render: a Zero DevOps Cloud Platform

#88

Does anyone on HN have first person experience with Render? Their offering certainly looks great on paper. I'd specifically be interested in your experience with regards to: - Stability / Uptime - How well the management UI / API / tools work - Any services you found you needed but aren't yet offered - Compliance with data protection regulations

Yes I deployed a django application to render w/ a couple of additional services: database, 2x background workers and redis. Overall the experience was positive but I feel that it tries too hard to have a "simple" UX which ended up annoying me in the end. I would use it again but I didn't "love" it. I have a feeling it will be pretty good long term. Here are some annoyances I had:

- Environment previews don't always work, hard to easily switch between services running in environment previews

- Slow deploys because it rebuilds the docker image every time, no way to connect it to a registry

- Documentation is shallow, especially when things get technical or complex related to their "blueprints"

- Ran into a bug with their environment groups

- They proxy through cloudflare and had some intermittent issues

- Zero downtime deploy wasn't actually zero downtime

Post reply on HN