Clearly the author still hasn't learned his lesson: his "no more vendor lock" solution is another vendor(s) - which is always able to vendor-lock him, again. It is truly mind blowing on how many people keep falling for one of the oldest trick in IT : vendor lock-in. === No more vendor lock In 2018 Heroku was pretty much the only option for a newbie like me to get started with web-development. The landscape is very di…
So what should he be doing, building his own data center?
Heroku has been running a second copy of my scheduler instance
11–20 of 132 posts
Re: Heroku has been running a second copy of my scheduler instance
#12Clearly the author still hasn't learned his lesson: his "no more vendor lock" solution is another vendor(s) - which is always able to vendor-lock him, again. It is truly mind blowing on how many people keep falling for one of the oldest trick in IT : vendor lock-in. === No more vendor lock In 2018 Heroku was pretty much the only option for a newbie like me to get started with web-development. The landscape is very di…
So what should he be doing, building his own data center?
Re: Heroku has been running a second copy of my scheduler instance
#13My god I wish I could short Heroku stock.
Re: Heroku has been running a second copy of my scheduler instance
#14If Heroku is running some zombie instance of your app, what if you were to just kill the instance you control and let Heroku run the zombie instance? When your service goes fully down, you'll know they've killed the zombie instance, so you can then run a clean copy.
Re: Heroku has been running a second copy of my scheduler instance
#15Clearly the author still hasn't learned his lesson: his "no more vendor lock" solution is another vendor(s) - which is always able to vendor-lock him, again. It is truly mind blowing on how many people keep falling for one of the oldest trick in IT : vendor lock-in. === No more vendor lock In 2018 Heroku was pretty much the only option for a newbie like me to get started with web-development. The landscape is very di…
Moving to another vendor while making it easy to move between vendors doesn't get you locked in.
Re: Heroku has been running a second copy of my scheduler instance
#16Re: Heroku has been running a second copy of my scheduler instance
#17If Heroku is running some zombie instance of your app, what if you were to just kill the instance you control and let Heroku run the zombie instance? When your service goes fully down, you'll know they've killed the zombie instance, so you can then run a clean copy.
Not being able to update your code plus your app will completely crash randomly at some point between now and eternity - sounds great!
Re: Heroku has been running a second copy of my scheduler instance
#18Re: Heroku has been running a second copy of my scheduler instance
#19I vote for moving to Render! My god I wish I could short Heroku stock.
Then add Postgres for another $95. Or if you're cheap like me, you self-host that in your $24 droplet and pay nothing extra.
And then they want you to pay for Crons....instead of just running a cronjob on your dedicated compute?
What is this world coming to?
Re: Heroku has been running a second copy of my scheduler instance
#20Earlier quoted context omitted.
Rent a $5/month VPS, install a few packages? Or just run a linux vm locally.
So, rely on yet another vendor, or do as I suggested except without any semblance of reliabiliy.