Salesforce Heroku Reviews: 4.3/5 — Solid Choice

Its extensibility, plugins and command-line integration. One can set up complete stack in minutes focus on the application rather than maintaining the stack.

Extra services that are required along with the primary platform come at a higher cost, if we choose to work entirely on the Heroku platform.

Creating large scale web platforms for social activities. It provides with all types of pricing to suit your needs and gives you the ability to test some free of cost.

Mostly free, pretty easy to use, CLI works well

Well the upgrading process is not exactly fun

To try out my test app and deliver them to the web

Its CICD integration with VCS like GitHub. Deployment is faster than its competitor like Render it has its own CLI tool, which is handy when you want to deploy projects which not on any VCS and check logs for applications without login your account in the web browser.

It becoming paid now means they have removed their free tier, so even if you want to try it, you must pay for it. And it's a bit more expensive than that. It's hosting also has some issues. You will face many problems working with different libraries like Puppeteerjs, which doesn't work on their hosting.

It Provides me with a one-click solution to set up my development server and integrate CICD automatically. With this, I can focus more on development rather than deployment.

Ease of deployment and scaling and no headache of devops

Very Expensive not suited for sme's or startups

Rest API deployments and mobile Backends

The ease of deployment, and speed to get started.

It is an opaque system: it can be a struggle to figure out what exactly is happening in any part of the system when things go wrong.

The speed at which we've been able to deploy to production has been a competitive advantage, and been a tremendous boon to new developers.

It's easy to get your app up and deployed complete with database, apps, etc., especially if you're using Ruby on Rails. Documentation is good and up to date. Pricing is fantastic. It's cheap.

OUTAGES! EC2 goes down, it takes Heroku with it. However the outages have gone much further than that. We use a shared Postgres database, and that keeps going down, knocking us over. Then, there are sometimes problems with restart, so we have a cascade problem -- we get a DB outage, we try to restart our site, and restart doesn't work. We've been down for as many as 9 hours at a shot, enough that I'm starting to think about moving to some other provider like EngineYard. It's very command-line centric. There aren't a lot of UI tools to help out new users, so there's a lot of doc-reading to do.

Not provided

Most Cloud offerings today are not that difficult to figure out. This one took a little while to get a handle of, but once you have it in place all systems are go.

Most Cloud offerings today are not that difficult to figure out. This one took a little while to get a handle of, but once you have it in place all systems are go.

Not provided

It makes deployments effortless with numerous available services such as Postgres, Redis, RabbitMQ, datadog, NewRelic etc. with one click. No need to configure docker and buildpacks are incredible and seamless. It also provides production, dev, staging etc. environments to deploy different branches of the project for rapid testing and previews.

Heroku used to provide free dynos with 730-hours/month limits which were enough to last a month. So basically, it was a free PaaS for deploying projects. Free dynos were automatically scaled to 0 and spun up seamlessly when the app received traffic. But now, the free dynos have been discontinued, so Heroku is no longer a suitable platform for deploying hobby projects and showcasing them.

Heroku takes out the pain of manually deploying projects or configuring CI/CD pipelines. Add-on services like Postgres, Redis, NewRelic etc. are effortless set-up. Heroku also saves the pain of configuring multiple dev, staging, and production environments. Heroku's rollback features are also helpful in instantly rolling back faulty deployments.

nothing at all, after salesforce has taken over heroku - it all went to the dump..

everything. several months ago my app was canceled without any reason given, I have lost access to my paid-subscription account, 2-step authentification I had to set recently - isn't even an option, when I log in it tells me no such user, and when I try to alter my password - it tells me the password is wrong, so the user must be there.. i contact support every week, it's my monday-morning tradition now, I ask them to stop charging me for the 1 x $7 dyno I've been subscribed to for my app, and nothing happens, they have NEVER replied my emails, it's really ridiculous, I simply have no way of canceling a subscription, short of replacing my credit card...

i am not sure what this means...

It's easy to set up and does what it says on the tin generally. Easy enough PaaS provider. The problems arise when you have contractual issues or need support...

Long story short, they will try to trap you with contracts - for example, rolling an annual contract even if you're talking to support ahead of time about amending or cancelling it. Do not trust them or rely on good faith. In true American style, common sense, compassion and clear business need cannot supercede their contracts and hunger for money. You can try and fight them afterwards, but when &^%$ hits the fan and you need to reason with a human being, it will not happen. Our case detailed below: We have been terribly hit by Covid (travel tech business) and so our traffic fell off a cliff a month or two before our contract renewal was due. We were actively in discussions with their team about how we could adjust our usage accordingly. As we were coming close to a resolution that would save us a load of cash, they suddenly said 'oh, too late, your contract has rolled over so we can't make any changes, you have to pay for x dynos even if you don't use them'. We pointed out that this was ridiculous, given that we were literally talking to their support team when it happened. Feeling fed up, we researched alternatives and had an option available that stood to save the business an amount that could be crucial to our survival. After explaining this to our rep and asking what reasonable provisions there were to simply pay for what we'd used and end the contract (which shouldn't have been rolled anyway) they immediately jumped to threatening us and saying that if we didn't pay for the full contract then they'll send debt collectors! We found this highly inappropriate and asked to speak to their manager. What followed was a circus of escalations and beaucracy, all amounting to different levels of people blaming processes as to why we couldn't simply pay for what we'd used and cancel the contract (which, again, shouldn't in good faith have rolled in the first place). Eventually they offered a very small concession (we'd still have to pay for more than we were using) but no reasonable exit provisions.

PaaS is relatively useful, avoids dev ops hires - though AWS has low-management options now-a-days.