4 ms·
I've seen millions of dollars spent on infrastructure to support what Heroku could do for a few thousand a month. Not to mention the egregious dev heartache ca
by ftlio 5y ago
I've seen millions of dollars spent on infrastructure to support what Heroku could do for a few thousand a month. Not to mention the egregious dev heartache caused by having to work against it. Anyone who argued it was a waste of time and money just "didn't get it" apparently.
I'm a huge fan of all the cool container stuff, queues, stream processing, all the weird topologies for apps built with node, Golang. I'm with it, kids. But for an MVP, just use Heroku, GAE, a Droplet with SCP for god sakes.
If you need to do something more complicated, growth will tell you.
- VWWHFSfQ 5y agoI worked for a very profitable small internet biz whose entire deployment was git-archive + rsync. I never had to troubleshoot that thing even once. Now it seems like everybody is playing golf trying to see how many AWS services they can use to unpack a gzip on a server.
- pphysch 5y ago> If you need to do something more complicated, growth will tell you. +1. Needing to refactor & scale your infrastructure to enable more growth is almost always a "good problem to have". You've steadily grown to $100mm revenue and your backend is starting to show it because you prioritized productivity over premature optimizations? Oh no, the world is ending! (said no one ever)
- tomcam 5y agoSorry to nitpick, and I agree with almost the entire statement you made, but I don’t quite understand how Go fits in there. I chose it in large part because it sharply reduces dependencies. Just curious about your inclusion of it in that list. Totally not trying to get into language wars or anything. Just want to understand your thinking.
- ftlio 5y agoI guess it doesn't fit in besides I've seen it be used for microservices where microservices don't apply