This is the first time I’ve read “Zero DevOps” as a product feature, but it seems like a pretty good selling point.
Render: a Zero DevOps Cloud Platform
21–30 of 127 posts
Re: Render: a Zero DevOps Cloud Platform
#22Re: Render: a Zero DevOps Cloud Platform
#23I 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.
Re: Render: a Zero DevOps Cloud Platform
#24Re: Render: a Zero DevOps Cloud Platform
#25- "Access to the Redis CLI"
Does that mean we can access to Redis CLI in web interface? I need a product like this and I signed up to create an instance, and I created a Redis instance but I couldn't find the redis cli on web interface. I would like to access to the Redis-cli, and I don't want it to be accessed by outside of my cluster. So If I connect with my local redis-cli, I have to turn on External connections, which will make the instance accessible by everyone.
Re: Render: a Zero DevOps Cloud Platform
#26Redis 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?
Re: Render: a Zero DevOps Cloud Platform
#27This 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.
AWS and GCP are a nightmare.
Re: Render: a Zero DevOps Cloud Platform
#28The 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…
We recently got bit (not quite burned) with the load balancers in the Common Runtime being shared across all apps.
Some piece of malware was associated with one of the IPs of Heroku's load balancers. One of our customers ended up blocking one of our servers associated to that IP because of it. We did some research and we even think we know what app caused it (it's someone's app they host on Heroku), and we don't think it should be flagged as malware, but either way... some other app in Heroku could be truly doing bad things and we would then get our server blocked again.
Heroku's advice was to put up a CDN in front of their load balancers, which has worked for now. But that's extra cost and system complexity just to get around a limitation of Heroku.
We did confirm a Heroku Private Space would eliminate this, since we'd get our own set of IPs for the Private Space's load balancers. But that comes with extra cost, and perhaps even limiting which add-ons we can use in the Private Space.
So although we've generally been happy with Heroku, we are concerned with some technical limitations, like this important (to us) one.
Re: Render: a Zero DevOps Cloud Platform
#29Re: Render: a Zero DevOps Cloud Platform
#30This 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.
There's a nice poetry to seeing a system autorecover from outages or scale correctly when it gets a huge burst of traffic. From being able to help an engineer do something they think is impossible, and do it easily.