Easy Peezy Heroku
Overall Satisfaction with Heroku
We use Heroku as our primary hosting service for our web application. It takes care of scaling when it comes to our database size, web traffic spikes, and background jobs. Deployment and maintenance come with ease without having to worry about managing our infrastructure. We have multiple web applications that serve as our staging and production environments, and we use a tagging system that rolls out our deploys quickly. The scheduler comes in very handy to mimic cronjobs necessary to run at specific times. Without having to worry about the systems side of development, we can concentrate more on features.
Pros
- On-demand scalability
- Ease of deployment
- Command Line Interface
Cons
- Fail safe when Amazon has problems. I understand that some of the ownership is on us, but we would prefer if we didn't have to resort to another service for backup.
- With the easy plug and play addons, it has been no-brainers to choose services that will easily integrate with our application. Choosing Redis, MemCache, and the Scheduler all were obvious choices.
I've had experience with using Amazon EC2 directly, Rackspace, and EngineYard. Heroku has provided the best ease of use without too much hands-on management. Outside of that, I believe it provides the most value for what you pay for. As your needs increase, the price increases, but only at the discretion of what is mandatory of the application.
Heroku Platform Feature Ratings
Using Heroku
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | Requires technical support |
- Scaling web dynos and workers
- Deployment
- Reporting
- Targeting R14 memory quota exceeded error and how to handle them
- What to do when your slug size exceeds the max allowed.
Comments
Please log in to join the conversation