2 ms·
My experience as a one man operation is that you always have to make trade offs between building something yourself (especially if you actually need to learn a
by wuliwong 11y ago
My experience as a one man operation is that you always have to make trade offs between building something yourself (especially if you actually need to learn a new skill-set to do it) and using someone else's solution. Honestly, in general this is essentially always the debate even at my regular job.
For me, Heroku has always been the choice over AWS or Digital Ocean. I haven't had it block me from doing anything I've wanted to do and my monthly bill is around $10 (for multiple sites). For my projects, I could never make a solid argument that moving away from Heroku would actually change the product for the end user in any meaningful way. And with the greater amount of time and energy I would need to focus on a non-Heroku server-side, it would likely slow progress.
- overcast 11y agoHonestly, I don't really care what you use if it fits your needs. The main point here is that the author shut down his project, because they were spending $250 a month, to operate a very basic setup. Pick your favorite host, but a car payment to do so, is ludicrous.
- mod 11y agoI use both. I have a side project deployed to Heroku and it's fine there, but it costs me about $45/month. The same project would often have a better response time (when heroku sleeps the dyno) if it were hosted on DO, and both would require no maintenance (I haven't edited a line of code in ~2 years). It's a django/postgres setup, nothing special, and would run on the smallest DO instance. I'm just too lazy to switch it over, honestly. I don't think it's a difference between "building it myself" and "using someone else's solution." It's about an hour of setup, maybe 2 if I encounter headaches. I probably ought to do it, given it'll earn me $35-40 per month forever.