91–100 of 127 posts
What's not clear immediately is that this isn't a standalone offering. It seems to be meant for use with their hosting service. So you'd already be in the ecosystem, not trying to hook it up to like a netlify page or something on your own vm.
Using an off-site redis instance makes zero sense in the first place.
* 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.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 vps and then apps before.
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…
Earlier quoted context omitted.
I just listened to an the Syntax podcast where it’s a pain to setup cloudflare for Render
Mind pointing me to the podcast? Cloudflare is quite easy to set up in front of Render now.
I was under the impression that "Redis That Just Works" is usually referred to as "Redis". Redis is perhaps the easiest thing to deploy that I'm familiar with.
(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 moved a 1M monthly visitors project from Heroku to Render in December, and other than a few little hiccups, I have a better service (no hard-cap on memory for ex) for less than half the price. I thought I was happy with Heroku until realizing the absurd cost and lack of evolution it grew to be. I've been there for almost a decade.
I do sometimes worry that one day they’ll shut down and I’ll be stuck moving to a crappier service…
I moved a 1M monthly visitors project from Heroku to Render in December, and other than a few little hiccups, I have a better service (no hard-cap on memory for ex) for less than half the price. I thought I was happy with Heroku until realizing the absurd cost and lack of evolution it grew to be. I've been there for almost a decade.
Yeah, Render is great. I’ve run a company blog on a Django/Wagtail setup there for almost 2 years now with very few hiccups. I do sometimes worry that one day they’ll shut down and I’ll be stuck moving to a crappier service…
Earlier quoted context omitted.
I just listened to an the Syntax podcast where it’s a pain to setup cloudflare for Render
Mind pointing me to the podcast? Cloudflare is quite easy to set up in front of Render now.
Earlier quoted context omitted.
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.
There are better things to spend time complaining about and it's not this.