The HN title is confusing and "just works" isn't mentioned in the actual article.
I was going to ask if anyone ever had trouble running Redis. But that's not something the article itself asserts.
Render: a Zero DevOps Cloud Platform
61–70 of 127 posts
Re: Render: a Zero DevOps Cloud Platform
#62I 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.
Re: Render: a Zero DevOps Cloud Platform
#63How does clustering work? I hope this isn't just a single instance.
Clustering/HA is next on our list. We wanted to get the core release out quickly so customers can avoid mucking around with their own Redis container deploys.
Re: Render: a Zero DevOps Cloud Platform
#64Does 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
Re: Render: a Zero DevOps Cloud Platform
#65These days, can’t you simply install KeyDB in your own Kubernetes cluster?
Re: Render: a Zero DevOps Cloud Platform
#66* 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?
Re: Render: a Zero DevOps Cloud Platform
#67The pricing absolutely blows Heroku away here across the spectrum… Heroku: $15/mo = 50Mb memory + 40 connections Render: $10/mo = 250Mb memory + 500 connections --- Heroku $750/mo = 7Gb memory + 10k connections Render $250/mo = 10Gb memory + 10k connections
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…
Overpriced yes, but garbage? Heroku is definitely stagnating, but they were integral to a whole new genre of PaaS. Heroku got a ton of people's first apps online. Even today their 12 factor app methodology is incredibly useful/powerful.
Now that said I totally relate to having strong negative opinions after being burned. I've got a few orgs like that too. What did they do for you?
Edit: nevermind I should have refreshed. You already answered in a sibling comment
Re: Render: a Zero DevOps Cloud Platform
#68Earlier quoted context omitted.
> they started charging 10x more after reading our git commits I’ll bite. What does this mean?
Since a lot of their customers share passwords or only use git automation to deploy without logging in, as they charge by team members, they've started to count git committers as "team members" which blows my mind: even if you can justify some sort of "cost" associated with having a team member, I can't fathom why you would charge by the git committer, except for jacking up your revenue in preparation for a sales or…
wow, dang. So one time committers cost you the same as a daily committer? Sounds like they're discouraging open source models (even internal open source where people on different teams can contribute PRs). That would really suck for us.
Re: Render: a Zero DevOps Cloud Platform
#69Been very happy with Render after migrating everything off of Netlify (they started charging 10x more after reading our git commits). Great to see them offer a hosted Redis option!
Checkout Cloud 66 too
Re: Render: a Zero DevOps Cloud Platform
#70Redis in docker, Kubernetes is almost zero config as it is. For small stuff anyway. For big stuff, would it not be a massive drag not having it proximal to your app serve we a?
In what world is Kubernetes zero config?
GP is saying adding a Redis container to docker/k8s is (nearly) zero config, and they are correct, with the caveat that only if you don't need persistence features.