Try our new research platform with insights from 80,000+ expert users
Ruby programmer at a computer software company with 201-500 employees
Vendor
Very good for implementing new apps and pushing changes
Pros and Cons
  • "It's easy to push a change and to deploy new things."
  • "Heroku doesn't support Docker images on the CI infrastructure."

What is our primary use case?

My primary use case of this product is for hosting Ruby applications. Probably more than half of the people at our company use Heroku for applications. I am a customer of Heroku and a Ruby programmer. 

What is most valuable?

I like the operations of the product because it makes it easy to push a change and to deploy new things. We trust the store for add-ons, they are pretty good with some solutions like storage or login add-ons. 

What needs improvement?

They used to have MongoDB add-ons, but currently I think they've stopped and I'm not sure why. There is an issue because Heroku supports Docker container images, but not if you're using the continuous integration infrastructure. I really think Heroku should support Docker images on the CI infrastructure. For now, you cannot use those images and have to use the certified ones they provide for continuous integration and continuous delivery.

They have a free plan but it only provides three hours of service, after which you have to switch to a pay plan. It's when you start to scale the application it becomes costly. There should be more scalability options for storage. It would be nice to have more official stacks, to try and support more languages to stack officially.

For how long have I used the solution?

I've been using this solution for eight years. 

Buyer's Guide
Heroku
January 2025
Learn what your peers think about Heroku. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
831,997 professionals have used our research since 2012.

What do I think about the stability of the solution?

There are some stability issues from time to time. 

How are customer service and support?

The technical support isn't bad. The response time could be improved but I last contacted them some time ago when they were still using email and didn't have a direct chat option. It was either email or on a forum. It's probably improved since then. 

How was the initial setup?

Deployment time depends on the type of applications you plan to use. Deployment usually takes less than three minutes. 

What other advice do I have?

I would recommend this solution. It's very good for small organizations with low traffic that don't need a lot of storage. If you need more storage, you should use an extra add-on or connection like Amazon.

I would rate this solution a nine out of 10. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Developer at a tech services company with 1,001-5,000 employees
Consultant
Good host for nodejs, but not the cheapest solution

What is most valuable?

Deploying with git, npm install git hook ... basically, they got it right for nodejs servers hosting. Free trials is limited (1 app running at a time) but good enough for a proof of concept. Using an Heroku backend and a GithHub pages front end serving static content, I can scale my app for free to a reasonable level.

What needs improvement?

Plugins aren't cheap (Mailchimp is $1.5/1000 emails).

For how long have I used the solution?

6 months

How are customer service and technical support?

The doc is good, for nodejs at least. It is newbies friendly.

Which solution did I use previously and why did I switch?

I rejected Google app engine for there lack of nodejs support, and AWS for the complexity of setting up a simple app.

How was the initial setup?

The CLI tools are good and deployment is quick. The web control panel ain't that great, I got into trouble trying to launch my app.

What's my experience with pricing, setup cost, and licensing?

0 for now :)

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user154575 - PeerSpot reviewer
it_user154575IT Manager at a wellness & fitness company
Vendor

Heroku's support is very poor.

Buyer's Guide
Heroku
January 2025
Learn what your peers think about Heroku. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
831,997 professionals have used our research since 2012.
PeerSpot user
Engineer at a tech services company with 51-200 employees
Consultant
Some insights into PaaS market

Platform as a Service is a one of the GROWING sector of cloud computing. PaaS basically help developer to speed the development of app, saving money and most important innovating their applications and business instead of setting up configurations and managing things like servers and databases.

Other features buying to use PaaS is the application deployment process such as agility, High Availability, Monitoring, Scale / Descale, limited need for expertise, easy deployment, and reduced cost and development time.

Major forces driving the PaaS

- Pay as you Go
- Low start up cost
- Leave the plumbing to expert
- PaaS handles auto scaling/descaling, Load blancing, disaster recovery
- PaaS manages all security requirements
- PaaS manages reliability, High Availability
- Paas manages manay third party addon’s for you

Barrier to PaaS adoption?

- Less Control over Server and databases
- Have to be expert to mange security controls and audits
- Costs will be very high if not governed properly
- Premature and dobious in current day and age

Major PaaS providers are Heroku, Jelastic, and Engine Yard. When we talk about revenue, The global PaaS market is estimated to grow from $1.28 billion in 2013 to $6.94 billion in 2018 at a compound annual growth rate (CAGR) of 32.54% in this period. In terms of geographies, North America continues to be the biggest market for PaaS solutions. In 2012, PaaS revenues ($1.2 billion) was the tenth of the size of SaaS ($14.4 billion), a fifth of IaaS ($6.2 billion), and just a tiny fraction of BPaaS ($84.1 billion).

PaaS has always taken a very small space in the cloud computing arena as compared to the other two segments: IaaS and SaaS. But the trend has recently shown a drift with PaaS market showing a very high growth rate in terms of revenue. Though it is still not as huge as the other two segments but now holds a significant proportion of the pie. PaaS has now been adopted by most of the big cloud computing and IT solution providers like Amazon, IBM, Google etc. as one of their main services.. Many small players have also emerged and made the market very dynamic and competitive. Application developers are benefiting from this fact resulting in more adoption and thus increasing the demand for PaaS all the more in various sectors.

We expect to see more and more application development companies choosing PaaS over IaaS or traditional Hosting, as they can then focus on driving innovation and building apps that change their interactions with customers, partners and community. It will make them free of the details of infrastructure, so they can push the possibilities of the latest technology to build great web and mobile applications.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user105252 - PeerSpot reviewer
it_user105252CTO at a healthcare company with 51-200 employees
Vendor

I don't see how the "barriers" are inherent to PaaS:
-->Managing servers is a cost TO BE AVOIDED - so that's actually a benefit of PaaS not a barrier
--> Security is no more difficult than implementing good security practices on a Web App. And much of it is simpler since you don't have to figure out how to optimally configure your Web Server, your Platform server (OS) and your middle ware server for optimal security. you only have to deal with App level and data level security.
-->Costs are inherently LOWER than with VMs since you do not have to have staff managing the VM stack and scaleout is easier to implement so you can start with a smaller instance
--> As for premature.... based on?

it_user7917 - PeerSpot reviewer
Engineer at a tech company with 51-200 employees
Vendor
How I hosted a local television contest for $2.37 on heroku

Big spender.

There’s my heroku bill after hosting the voting for a local television contest. $2.37. Over 40,000 people used the app over a period of 2 weeks.

I spent the same amount on coffee this morning.

What?! How?!

I’ve always been really interested in scaling and getting the best possible performance out of limited resources.

I had the opportunity recently to build out the voting back-end for a local television contest. Projects like this are fun because I had the flexibility to try out something new and a lot of people would be using it.

The Stack

I wanted to build an API to handle the voting and get the best performance out of it. Usually I’d use Sinatra for this, but this time I chose to try out Goliath, which is a non-blocking Ruby web server for building APIs. I also used Grape since it would make writing the API even easier.

I hosted it on Heroku. My initial goal was to see if I could keep it to only 1 dyno (more fun with a challenge).

If you’re not familiar with Heroku, a dyno is the equivalent of a small virtual server with 512mb of memory. They also give you your first dyno for free. So all I ended up paying for was the postgres basic database add-on.

Stress Test

Before releasing it, I did some stress testing with Siege. I couldn’t have this app failing when it went live.

212.45 transactions per second.

On only 1 heroku dyno.

WOW GOLIATH IS FAST.

Each transaction was a single GET request, that hit the database (postgres) and returned the count of contest votes. Postgres was probably the slowest part of each request. I could optimize even further by caching with memcached. Maybe next time.

The 200+ transactions per second was way more speed than I needed for this app. And much more than I expected to get out of a single dyno.

I knew that the traffic for this app would be pretty sporadic. Highly dependent on when it was mentioned on TV. Without Goliath, I would have needed to use more dynos to account for the spikes in traffic. But with the performance I was seeing out of Goliath, I knew it could handle the peaks with just 1 dyno.

See the details of the Seige test here.

If you’d like to try it out yourself, the app I used to run this contest was a modified version of Mathy Poll. Which is open source and you can grab it on github.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user4401 - PeerSpot reviewer
it_user4401Developer at a transportation company with 1,001-5,000 employees
Vendor

This is a really great idea. Thank you for sharing this information with us.

it_user701415 - PeerSpot reviewer
Tech Lead Javascript Full Stack at a tech services company
Consultant
It has improved our deployment speed without requiring time to configure some servers
Pros and Cons
  • "Valuable for us was the fast deployment. This means the time to market is improved without pain for developers."
  • "We don't find the pipelines intuitive. The user experience could be better. Having to set up multiple apps, then a pipeline, seems like an overkill on the amount of work to do."

What is most valuable?

Valuable for us was the fast deployment. This means the time to market is improved without pain for developers.

How has it helped my organization?

It has improved our deployment speed without requiring time to configure some servers.

What needs improvement?

We don't find the pipelines intuitive. The user experience could be better. Having to set up multiple apps, then a pipeline, seems like an overkill on the amount of work to do.

For how long have I used the solution?

We have been using the solution for six months.

What do I think about the stability of the solution?

We did not encounter any issues with stability.

What do I think about the scalability of the solution?

We did not encounter any issues with scalability.

How are customer service and technical support?

We didn't need to use the technical support.

Which solution did I use previously and why did I switch?

We did not use a previous solution.

How was the initial setup?

The initial setup was straightforward.

Which other solutions did I evaluate?

We evaluated Google Compute Engine, Google App Engine, and Kubernetes.

What other advice do I have?

It's an easy product to use.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Full Stack Web Developper, Freelance & Entrepreneur at a tech services company with 51-200 employees
Consultant
My story about going from being a fan of Heroku to leaving Heroku

I have been a great fan of Heroku as it simplified my work for many years.

But I recently got my account suspended because someone abused one of my apps. Since then, I decided to leave Heroku because I cannot afford to loose control on my work.

Here's the story: http://augustin-riedinger.fr/e...

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
CEO at a tech services company with 51-200 employees
Consultant
Amazing platform, poor customer service

Valuable Features

Lots of integrations

Use of Solution

1 year

Stability Issues

I had an issue recently where my site was down intermittently for unknown reasons. I posted a ticket and 5 days have gone by without any resolution. I'm surprised at this total lack of customer service.

Customer Service and Technical Support

Customer Service:

So far very very poor. I'm considering switching to another platform for only this reason. How can a startup scale a business with such poor support. 5+ days no response to a valid ticket!

Technical Support:

Horrible because they take forever to respond. Days with no response.

Initial Setup

The setup was pretty good.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user8373 - PeerSpot reviewer
Developer at a tech services company with 51-200 employees
Consultant
Great Deployment Options - Heroku, Engine Yard and Amazon

Depending on your needs heroku might get you very far, very fast. I like to use it for clients whose biggest hurdle is not the technology, but in rapidly building a product and iterating quickly. If you already know your customer base, your eventual architecture, and how big your app is going to get, you might prefer to jump ahead to engine yard or amazon, but if you are launching a new app and are still in the process of discovery and exploration, you may find heroku is a good place to start. I work with a lot of small startups and prototype apps, and I think heroku is great for that. Its easy to launch an app quickly, engage users, add new features, scale it up and down as needed, lots of plugins to help you along, while keeping your IT costs reasonable.
Now if the app really takes off, in a sustained way (not just a press-release spike), you will have to decide what changes you want to make to the architecture, and if you have outgrown heroku. I think its great to have Heroku, EngineYard, and Amazon as deployment options. They all have great free options, and each of them has their sweet spot.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user4401 - PeerSpot reviewer
it_user4401Developer at a transportation company with 1,001-5,000 employees
Vendor

On my opinion, Heroku has two main pros: speed and simplicity. Since I just want to focus on my applications, it's a convenience to have a managed platform that I can quickly push application to. I also like that it offers plugins which further simplify things like mailservers, backups, logging, etc. But, as a con, it is expensive.

Buyer's Guide
Download our free Heroku Report and get advice and tips from experienced pros sharing their opinions.
Updated: January 2025
Product Categories
PaaS Clouds
Buyer's Guide
Download our free Heroku Report and get advice and tips from experienced pros sharing their opinions.