5 ms·
I wanted to give Heroku a try for a new website my brother and I are building and looking at the costs it's quite steep. $35 for a measly 2 dyno application, a
by sergiotapia 13y ago
I wanted to give Heroku a try for a new website my brother and I are building and looking at the costs it's quite steep.
$35 for a measly 2 dyno application, and another $50 for a production postgresql database.
Our use case is REALLY simple, we aren't building some freak sideshow redis golang nonblocking nodejs mongodb ravendb nqueue sync rabbit hyperthreaded monster. We're just building a Rails 4 site, with a PostgreSQL database backend. That's ENOUGH for our use cases. For what we need it's infinitely cheaper to just rent a Linode/DigitalOcean server, use something like Chef to spin up the services we need and voila. We probably won't have to touch the servers for a very long time. Again: We're doing simple things - CRUD basically.
I love Heroku for it's simple usage but it's just too darn expensive for us.
- mattmanser 13y agoHow is this relevant?
- sergiotapia 13y agoI meant to reply to nthj's comment.
- Aqueous 13y ago1X dev dynos are free. If you need to go up to 2 dynos or scale vertically to a 2X dyno then you start paying. You shouldn't really need to use 2 dynos until you actually have to launch. You're going to be spending a lot of time configuring/writing Chef cookbooks and refining your deployment process. This is time that you could be spending developing features and making your application more reliable. That's where the savings come in. It's not more expensive; it's less.
- zarriak 13y agoIt just depends upon what you value doing with your time, whether you value paying more for convenience, or paying less but having to deal with everything. It just boils down to a design choice.
- Aqueous 13y agoWell, no, I disagree. Having to create, maintain and monitor your own infrastructure is a very big time cost which has very real consequences when you are in a business. As a business you should be spending as much time as possible focusing on your product and not things that are extraneous to it. At this point the basic infrastructure for 99 % of small web applications is pretty much identical: a web service, a backend relational store, a load balancer, and probably a caching service. This basic set-up can accommodate a wide range of features. There is absolutely no need to spend time configuring these services and making sure they remain up and running. I see a lot of people who want to configure their own infrastructure because for some reason they believe their application is special. Invariably, if you look at their application more closely I've realized that, no, it tends not to be that special. Perhaps when/if they scale up the service requirements they will need to be become more specialized but even then, probably not. Even if it does end up that you have to change your application's structure during scaling, trying to make it ready for scaling too early is a premature optimization and will end up costing you.
- jrochkind1 13y agoI agree it's not cheap. What is your alternative that will give you as useful a deploy environment (for whatever kinds of 'useful' you need, everyone has different needs)? How much will it cost, in direct costs or your time? Do you or someone on your team have the expertise and time to provide and maintain such a deploy environment? If there's something that is good enough but cheaper, than by all means use it. The reason heroku is so succesful despite not being cheap is that for many people, there isn't. Which means while it may not be cheap, for many people it's a pretty darn good value.
- r-s 13y agoI have thought the same thing. I also have a few sites which get little traffic 99% of the time which the free plan works fine. I would pay a fee to get it so the app doesn't always have to spin up on the free plan.
- elithrar 13y ago> For what we need it's infinitely cheaper to just rent a Linode/DigitalOcean server, use something like Chef to spin up the services we need and voila. We probably won't have to touch the servers for a very long time. Again: We're doing simple things - CRUD basically. To be fair, all of that takes time (and therefore, $$). For side projects it's probably not a big deal--the learning process itself is valuable--but if you're actually talking hard sums, Heroku isn't always as expensive as it seems. You'll need to manage: - Chef cookbooks and testing (this is a big one) - Deployment (using Chef standalone? Fabric? Git server + post-receive hooks?) - Backups (are you pushing WAL logs to S3? Have you tested recovery?) - System resourcing (didn't write a logrotate config for that custom service? Out of disk space?) - Monitoring (Pingdom, New Relic, etc.) in case it does go down? - etc, etc. It all adds up. For my own side project I went down the DO + Salt + Packer path, but my day job isn't as a dev/programmer so I had to spend a little time learning the idiosyncrasies of Salt and Upstart. These skills are valuable (for the next project down the line), but if I was part of a small team with a deadline then taking "detours" isn't always an option.
- nthj 13y agoHey Sergio, my agency's website [1] has been happily hosted on Heroku for a year and I pay approximately $0 for it. You have to set up your site for performance—caching, CDN, use Unicorn, the like—but unless you have something like 30 concurrent users, I think you might be overthinking it. You definitely don't need a production-level PostgreSQL database. That said, I'm pushing my developers to use Middleman [2] for mostly-static sites these days. No moving parts means nothing can go wrong, and we host on GitHub pages for free. Not sure if this fits your use case. I'm a bit of a Rails performance nut, feel free to ping me at nj@thirdprestige.com if you'd like to ask me more specific questions. [1] http://www.thirdprestige.com/ http://www.thirdprestige.com/ [2] http://middlemanapp.com/ http://middlemanapp.com/
- sergiotapia 13y agoYeah that number is pretty abysmal. We average around 100+ users per second per Google Analytics. That means, we might need about 4 dynos for our simple website? Yikes!
- nthj 13y agoIf it's really "simple" (not dynamic, or doesn't change often), you should throw the whole site behind a CDN. Then you can support tens of thousands of users very in expensively.
- sleepyhead 13y ago> We probably won't have to touch the servers for a very long time. Until somethings fucks up. If you are on Heroku they will handle DB, routing and server problems. On Linode you have to deal with that yourself or hire a sysadmin.
- deleted 13y ago[deleted]