Live data from Hacker News

Render: a Zero DevOps Cloud Platform

render.com

101–110 of 127 posts

Re: Render: a Zero DevOps Cloud Platform

#101

Earlier quoted context omitted.

Well Heroku is overpriced garbage so that's not surprising. They rely on lock in to keep you stuck paying egregious fees for services that are relatively unreliable. After migrating an entire startup infrastructure from Heroku to AWS I'm even more against Heroku given how easy it is to use something like Elastic Beanstalk to do the same thing without many of the same downsides. I've been burned by Heroku, though, so…

Right now I'm on my third job in my career where we've migrated off from Heroku. There have got to be agencies out there that specialize in this, right? If not, it seems like a hell of an opportunity for someone.

Where do you typically migrate to? Or does it depend on the project?

Re: Render: a Zero DevOps Cloud Platform

#102

May I ask what the benefit of this is vs spinning up your own Redis server? An equivalent solution would be to spin up a $5 droplet on DO, do basic due diligence wrt security (lock down ssh, firewall, etc.) and you end up with more memory, more connections, for less money. I realize I'm a Luddite, in the field of DevOps. Is it just the benefit of not needing to maintain the server?

DigitalOcean also offers managed Redis

Re: Render: a Zero DevOps Cloud Platform

#104
Congrats on the launch, Render team! Like so many others here, I was a former Heroku user turned AWS-customer that is longing for an option with the positioning, UX/DX that Heroku offered ten years ago.

There's this bit of copywriting I see on many startup landing pages that annoys me a bit:

"You can now set up a Redis instance in just a few clicks and let Render handle the heavy lifting to operate it reliably and securely."

To me, it always feels somewhat patronizing to refer to yourself as doing 'heavy lifting' and the customer's work as (obviously) not-quite-as-heavy-lifting. Maybe in particular because I've set up Redis in the past, and as many others have mentioned it is really the epitome of hassle-free, easy-to-setup server software. So referring to hosting Redis as heavy lifting just kind of feels wrong or over the top.

Re: Render: a Zero DevOps Cloud Platform

#105
post #18

(Render founder) Hi HN, we built our managed Redis service for people who already use Render to host their apps. You can of course use it from outside Render, but ideally you'd use the Redis internal URL (e.g. redis://red-longuniqueidhere:6379) in your code that's also running on Render.

I've been hearing fantastic things about Render. One concern I have is about the trajectory of the company-- for example there was a time when Heroku was a great bet, then it got sold and stalled. What are the most convincing points you can give for why Render won't follow a similar path?

Interestingly, Heroku improved and grew quite a bit after the acquisition (2010), but ultimately, getting acquired was a personal/financial decision for the founders: https://twitter.com/_adamwiggins_/status/1334595789201563649

I'm very happy to share my own acquisition calculus over email (in profile).

Re: Render: a Zero DevOps Cloud Platform

#106
post #104

Congrats on the launch, Render team! Like so many others here, I was a former Heroku user turned AWS-customer that is longing for an option with the positioning, UX/DX that Heroku offered ten years ago. There's this bit of copywriting I see on many startup landing pages that annoys me a bit: "You can now set up a Redis instance in just a few clicks and let Render handle the heavy lifting to operate it reliably and se…

Noted. Our intent is more 'you don't have to worry about it' vs. 'you're too dumb to do it yourself'.

Re: Render: a Zero DevOps Cloud Platform

#107
post #4

This is the first time I’ve read “Zero DevOps” as a product feature, but it seems like a pretty good selling point.

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

It is a part of my job, however so far I have found that if your pipelines are getting too complicated, it is time to break them out into build docker images, bash scripts etc.

Re: Render: a Zero DevOps Cloud Platform

#108
post #94
post #80

Earlier quoted context omitted.

Mind pointing me to the podcast? Cloudflare is quite easy to set up in front of Render now.

Hi, is it possible to proxy, for instance, /media/ from example.com/media/ to a S3 bucket? I run a setup using `nginx-ingress-controller` and it's possible to use it as reverse proxy to an external http server and I'm wondering if Render supports it as well. Thanks!

It should be for most setups. https://render.com/docs/redirects-rewrites has details.

Re: Render: a Zero DevOps Cloud Platform

#109
post #19

Earlier quoted context omitted.

Well Heroku is overpriced garbage so that's not surprising. They rely on lock in to keep you stuck paying egregious fees for services that are relatively unreliable. After migrating an entire startup infrastructure from Heroku to AWS I'm even more against Heroku given how easy it is to use something like Elastic Beanstalk to do the same thing without many of the same downsides. I've been burned by Heroku, though, so…

It is sad to see how Heroku has been totally abandoned by Salesforce. I mention as it's probably Render's closest competitor.

[deleted]

Re: Render: a Zero DevOps Cloud Platform

#110
post #92

* 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?

Render supports building / deploying docker containers so it supports everything, including Java. render.com and fly.io are in a similar niche of "deploy your app easily". To me fly.io prioritized the wrong thing: deploying apps close to users. I care more about low price, ease of use and features than optimizing latency. render.com is the best (that I know) "run a server for your app" service. I used Digital Ocean v…

If you don't care about optimizing latency, we definitely didn't build Fly.io for you. That's not because you want the wrong thing, though. It's because we have a narrow and, we think, very valuable focus.

We're actually not in the same niche as Render! At least, I'm pretty sure we're building towards different things. But we are each (a) small (b) scrapping with large public cloud providers and (c) attempting to generate a self sustaining startup reaction.

Attracting people with new apps is a way both of us prove the value of what we're doing. Attracting people who want to run their apps close to their users is the way we make a lot of money.

Post reply on HN