31–40 of 127 posts
Redis 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?
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.
I'm just complaining to complain lol.
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.
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…
I'm curious what the source of the burn is. 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…
For reference, we migrated to new t4g instances on AWS and received about a 100x performance improvement for a similar (sometimes cheaper) price than Heroku. We are also able to connect to our company VPC and use private resources partitioned elsewhere in AWS (e.g. a redis cluster that costs the same as Heroku with far fewer limitations).
The downside is obviously configuration and learning AWS. Thankfully, we are pretty well versed in AWS here.
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.
Horrible indeed. ;)
The 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…
You need double your number of typical connections to support rolling, combine that with the large price jumps and low connection counts on the plans and it becomes very expensive just to have something that should be standard in a modern PaaS platform. This is but one example.
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 didn't quite understand one of the things which is offered in the blog post. - "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…
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?
The 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…