Salesforce Heroku, is an ideal tool for all types of developers who want to upload their applications to the cloud, you can work as a test error, running the applications, which are in the database of the application, in an environment simulated, for later, when you are sure, they work perfectly, they are uploaded to the network, and they can be online and accessible to all.

I must be honest, this software is somewhat complicated to use even for advanced developers, many commands and codes may be difficult for many to understand, since they are development environments a little different from those we are already familiar with, apart from this, the documentation of help, which is found on the web, about this program is very limited, a very large help documentation is needed, to avoid wasting time, in the trial and error of the use of the different features, that the application uses.

We have a sector of developers, experimenting with new creations of applications of all kinds based on Heroku, we see a high potential, in this application and we want to move, many outdated applications that we still have, elaborated in different applications that use obsolete codes, and change them by the new ones that are made, in Heroku.

The ease of deployment and configuration is a big plus. Heroku lets you build and scale your website (and related components such as Postgres database or a Redis cache) with minimal fuss. There's more add-ons such as scheduled tasks and monitoring. Compared to other cloud providers, it's much easier to learn how to use and deploy your first app.

I think that for a highly complex application, heroku may not offer enough low-level control of the infrastructure.

Heroku may just suit your needs. Do a bit of research before committing to a cloud provider, there's no need to have complex features if you're not using them, and Heroku is located at a sweet spot with respect to price, ease of use and features that can support most web applications.

I built an application that let's users upload their data and share with others. It was very easy to provision the machines and the databases I needed - I didn't have to manage any networking configuration for example.

Heroku Toolbelt makes deployment and maintenance tasks so easy - everything is just a command line away. Almost never a gem compatibility problem, it's a complete plug-and-play. Hobby tier provides sufficient availability for my purposes.

Documentation works great for my needs, and it's supplemented by a healthy user community - I can find answers to most of my questions by just googling them,

It'd be nice to have some kind of a persistent file storage add-on. As things are now, I have to use Amazon S3 for files.

I wish Heroku Toolbelt used one port for everything. I roam a lot, working off of public wireless access points. Depending on their restrictions on TCP, ports you can use, this or that Heroku command won't work.

Also I'm not a big fan of their ElasticSearch add-on, Bonsai, I understand run by a separate company. I had availability issues specific to them, more than with Heroku proper. And when it happened, they would tell me that it's my fault for not subscribing to their more expensive plan.

It'd be nice to have more logs than just the last 1500 lines.

If your needs, like mine, are hosting Rails and Node.js web apps, Heroku seem like a good choice.

Watch out for the lack of persistent file storage - it came as a bit of a surprise to me.

We're building an IT Consulting Marketplace.

The main benefit is easy setup for easy deployment - DevOps without a big investment of time and money

Heroku enables any company of any scale or seamlessly manage any web properties they have. For rapid prototyping and testing new features, Heroku more than meets one's needs, and is a perfect solution to rapidly deploying and testing new mobile API back-ends. Whether one has always used personally managed servers or are coming from tools such as AWS Elastic Beanstalk, Heroku is very quick to migrate to and flexible to whatever deployment configuration you have. Its use of Git has been incredibly transformative for our team, as we had all been previously using it Git for all projects, and Heroku closed the loop allowing us to work and deploy from the same system.

Is more expensive than more traditional DIY hosting options. In the name of ease of use, some functionality is harder to find/employ, but this is more than compensated by the realized benefits of the system.

For rapid prototyping you will not be disappointed, but do bear in mind the cost as things scale.

Easy team collaboration and resource management and scaling. Heroku is the best way to achieve this. When application issues have occurred, Heroku has made patch deployment very easy and has been able to drastically improve our issue response time.

That it is so easy to manage and go back and force between data I am looking up.

That some of the updates are not at the level they should be for the product to be running to the best of its ability.

Salesforce is a very effective product however they need to make more updates that make it easier for the user.

Salesforce allows me to schedule the people in my company to go to the schools they need to be. It allows me to give them the time and the directions of where and what time the person needs to be.

The best thing that I Like about Heroku is once you do the changes and adds on the project to connect to the Data Base, You can work locally as server with the same Data Base. It is a very practical way to work, and you do the push to heroku master when you think it is necessary that all features are build in a correct way to check on web.

Something that really dislike is the missing points of documentation to get a correct way to develop a project, specially on Django/Python.

Give more details about how implement a project with Heroku, because it is confusing trying to connect and if you don't have that information on sorting point it is frustrating

I've been working on a project with Django/Python and let me work easily, like I'm not using Heroku, that is one of the greatest benefits about it, because once you got anything under control Heroku + Project, it lets you work quickly, allowing you to take care another things to getting a better development.

Heroku makes it super simple to get your app running in the cloud with as little fuss as possible. You don't have to worry about the details - with just a few commands you app can be deployed.

Navigating the command line can be frustrating at time and little support for debugging the production environment is supported - expect to rely

May be pricey, but can well make up for it in its ease of use and great documentation

Saved a lot of time and allowed us to focus on product rather than infrastructure.

Heroku is an incredible, elegant platform for deployment, hosting, and scalability. It's very well documented, has a great user experience both in website and command line form, is well supported by Heroku as well as third-party tools, and has a very set of features. Most of all: No need to be concerned with securing a server itself.

They also provide a fear, single dyno service one can use for testing and micro projects.

Heroku does have some limitations in the form of a no-write filesystem, forcing developers to use solutions like Amazon S3. It has had some performance issues in the past due to how routing was performed, but Heroku was honest and transparent about the issue and their resolution.

Use it. You can run far more than Ruby applications on it these days. Get rid of any servers you truly don't need and go PaaS.

We've used this for our own products, to host software for running blood drives, greatly supporting a hospital and its children, for a custom video streaming solution, and far more.

We could not be happier with a PaaS. It has saved us immense time in provisioning, configuration, deployment, and security, allowing us to focus on the application itself. It's so easily scalable, there have even been iPhone apps for doing so on the fly.

Heroku toolbelt: It makes every thing easy as pie, from profiling a deployed system to switching from local to remote console in order to perform any desired task. It feels just as if one were working on his/her local computer, while performing some very non-trivial remote tasks. Also, the Procfile feature is a must, as I can easily configure additional tests, continuous integration, and run some extra scripts that I might need in order to fulfill a certain task my product my be in need of. Switching from local to my remote deployed system, as well as having many different instances installed at the distance of a simple command text. It's a must to me!

Steep learning curve. In order to being fully capable of using heroku's platform, one needs to take quite a bit of time to learn its commands and entrails. It did take me a while to really take the time to study it. I wish it was a little simpler so I could have enjoyed its great plugins a lot earlier.

If you are looking for a cloud saas virtual environment, full of plugins and APIs, hands on and easily deployable, you might want to consider taking a look at Heroku.

Backend Restful API with Real Time features. It's pretty much the same thing like working on my own environment. So I had for far no hassles at all with the classical: "in my machine it works" excuse.

It makes going from idea to deployed app ridiculously easy. I *always* recommend starting with Heroku to folks starting out with tech like Rails and the Python frameworks. It removes the deployment barrier for these folks to start sharing their code. The lack of require maintenance is also great. If a piece of hardware fails, they take care of it.

The price, which isn't to say it doesn't match the value. It's just that it does add up once you reach a certain level of traffic and complexity. After a while, you reach a juncture where your app is complex enough, you know enough, and the concept is "worth it" (from a personal or financial perspective) to move it to something that is far higher maintenance for (in raw dollars) cheaper.

If you plan to go all in on Heroku, it will make your life much easier if you choose tech (e.g., databases, email, etc.) that has tight integration with it through a third party provider or a direct Heroku service.

Again, it removes devops from the equation almost completely when it comes to getting an app in front of people.

Heroku is finely customizable to a number of modern programming language such as Ruby, Node.js, PHP and Go. Users get quite a bit of functionality of the free tier which easily meets the needs of smaller personal applications. A single dyno is generally sufficient for these purposes.

Heroku also offers a fairly large catalogue of add-ons to integrate with applications, and database integration is a snap with Postgres.

The pricing model at Heroku should probably be revisited. Users with the hobby or free tier can generally extract quite a few features out of the service to fit the needs of personal applications, but the professional level infrastructure scheme is a bit nebulous.

Premium support options also make lower-tier subscribers feel neglected when trying to contact support.

Simple and easy to use, even for users with minimal knowledge of application architecture. May not fit the needs of larger applications, and the pricing model may need revision.

Heroku's Platform-as-a-service has functioned well as a standup environment in the smaller innovation development team that I have been a part of, but I suspect that larger enterprise development teams will likely side with vendors with more corporate recognition such as Microsoft Azure or Openshift.

It's quite simple.to create and configure an entire pipeline.

The UI is pretty simple and useful. You can perform almost any action: start/stop an application, group some apps in a pipeline, perform a rollback to a previous version with jist one click, etc...

It's a bit expensive.

An x1 instance (512MB and 1 core) costs 25 euros per month.

If your applocation needs 1GB of primary memory you'll need to pay 50 euros per month.

In my opinion it's not as cheap as other platform, like digital ocean. However it's true that Heroku is a PaaS so it offers more features.

You can set up an entire environment very fast

Build an entire pipeline (dev, test and pro) and autoscale our platform.

Lets you have a performant production server with a couple clicks, no devops knowledge needed.

Has tons of plugins for all your needs: Database (Heroku Postgres), Cache (Redis), Monitorization (NewRelic), emails (Mailgun), SSL…

Provides lots of documentation to set up apps in a variety of languages, and covers things like using several environments, tuning your memory usage, deploying from Dropbox, and more.

Together with a auto-scaling plugin like HireFire, it can manage your app as usage goes up and down, and you'll never be overwhelmed by a traffic spike, or spend more than you need on valley hours.

The pricing is a little high, especially if you want to use the dedicated dynos, which increase performance and decrease response time dramatically. We've also been bit by downtimes a couple times in the past year, being fully managed by them there's not much to do once it goes down. Also, since it runs on AWS ,if that goes down Heroku does too.

Great for starting a web app. As traffic rises, consider switching to a performance dyno, which gives you more bang for your buck, and also has much slower response time. Beware of delays in your requests when you deploy, consider using rolling restarts to fix it.

I can save lots of tiie configuring, testing and deploying servers on AWS or providers like Digital Ocean, while focusing on developing the app itself, which is what brings value after all.

The leader in the emerging platform-as-a-service industry is Heroku, an extensible and well-connected cloud hosting platform that makes deploying and managing applications in several popular languages almost effortless.

It has made great strides since its inception as a Ruby-only application hosting platform to include support for Python, Node.js, Java and PHP multiple languages.

Heroku has a freemium model, and invariably, Ruby enthusiasts who try out Heroku, invariably get hooked on to it and start using more and more resources and move to the premium offering.

No other services can be run on dynos. Dynos are strictly for application processes. Databases, background workers, and other services usually cost extra through Heroku’s add-ons or third party services.

No way to install system software. Heroku does provide some commonly-used packages such as Imagemagick, but if you need anything else, you’ll have to resort to hacks.

You can’t beat free, and this is actually quite a good offering. One dyno is plenty to run many kinds of apps. Brochure sites, simple APIs, and blogs are a few of the many possible uses for this free dyno.

Modern Platform-as-a-Service for Enterprise Application Development.

Corporate app dev teams can enjoy all of the core Heroku benefits — including smart containers, instant scalability, powerful developer tools and workflow, pre-integrated add-ons, and data services — with added collaboration functionality, additional control features, and enterprise grade support. Now enterprises can build highly engaging, disruptive apps as easily as startups.

The flexibility of the Heroku platform and add-ons made it easy to build our initial product, and add and remove features as our product and customer needs have evolved.

Heroku is not the cheapest platform out there and it isn't always the most flexible service either.

I would recommend Heroku to teams looking to deploy quickly or expect to need to modify their product significantly. The flexibility and ease of deploying Heroku's add-ons have allowed us to test many product features while minimizing the total cost (in time and money) of development and deployment.

We use heroku to serve our web application to leading businesses, law firms, and non-profits. Heroku allows us to minimize our devops investment and deliver the scalable service our customers depend on.

Easy installtion of plugins and add-ons.

Powerful metrics to monitor the app.

Detailed sample apps and code for start a new application

The database support is powerful, but the free account only have few options to use the postgree sql.

Powerful management tools, easy to start, detailed documentations .

I used Heroku to host one of my previous ios app's server. It's useful for small-scale apps and it's free. It also provide powerful entries for app owners to monitor the app statistics.

Easy to setup and use. It works as a charm to add new features or plugins. Well documented and easy to understand. Makes development easy since it gives you all the needed resources to do so.

It is still difficult for me to understand what a dyno is. It is not well documented and I have not seen any good explanation on it.

Don't be afraid of changing from a traditional grid-service to a cloud computing service.

I'm using it to deploy all my business products, applications and websites. Since it is very easy to use and deploy it has reduce the amount of tools needed. All the programming languages are great and it is great for scalability.

Firstly, and this cannot be overlooked, it's free to get started with Heroku and you probably won't have to pay them for a long long time (and by then you're probably making enough money anyway).

Secondly, their documentation is awesome and it's really easy to get started. I wasn't a linux pro by any stretch of the imagination when I started with Heroku but if you can use Git then you can deploy to Heroku.

Thirdly, they have a bunch of plugins and third party services to add support for any weird or wonderful data storage mechanisms you want to use, message queue services etc. so you basically don't have to touch infrastructure at all (something you generally would have to fiddle with if you were using AWS or Digital Ocean or the like).

Herokus is essentially Linux only... not a huge problem for many people (and certainly not for Heroku users).

Definitely give it a whirl - it's free to try and probably does everything you need and more.

I needed a place to host my public websites. Heroku is a good pick for personal/hobby projects or prototypes as well though.

For those with the budget to pay for the cost of Heroku, Heroku provides a number of very convenient features for developers such as instant deployment. Heroku integrates seamlessly into Git, the state-of-the-art version control system that many teams are switching to. Integrating version control system into deployment is an enormous advantage. Then deployment becomes a one-step process and is less to learn for developers. Deployment itself, rather than the code, can sometimes present an issue.

I dislike that Salesforce App Cloud: Heroku Enterprise is more expensive than other kinds of deployment tools. As a result, some teams use AWS and we may switch to AWS or another cloud service when our usage becomes high enough to require a paid tier of Heroku's plans.

For small-scale software, I strongly recommend Heroku. When software usage is low enough not to put much of a strain on the servers, one can use Heroku at a free or low-cost tier without running over budget. Prototyping also puts a premium on quick deployment.

We would like to use a quick and easy deployment platform. Heroku presents a quick and easy deployment platform. We are also on a small enough Heroku plan that budget is a non-issue. My team is prototyping our software and usage is small enough for us to remain on the free tier of Heroku. We also like using Git and making deployment a seamless component of the Git pushing process.

The time it takes to move from an idea to MVP is very quick when building on a product like Heroku. With its support for side-projects through it's free tier - moving up to highly performant, concurrent, distributed systems - Heroku manages the app at all stages of it's life. If something isn't directly possible on Heroku, it mostly likely is through their addons.

- We've occasionally struggled in the past trying to send requests from Heroku to services which require a static IP - but this problem can be avoided by setting up a proxy with an ip (but it's a pain).

- Setting up TLS certificates require an extra cost (as they require an addon) which in the day-and-age of letsencrypt, I think is a shame.

As a start-up in the property sector, Heroku has allowed us to focus on the business logic of building an online collaborative workspace, rather than worry about the infrastructure. In times of high demand we can scale the 'dyno' count to manage. Given out industry, we have low usage over weekends and evenings - which we can save in cost by scaling down.

Real time sync between salesforce and heroku enterprise. Linking up objects using indirect/external look up relationships so that we can access the data inside of salesforce. Options to limit sync transactions. Creating multiple applications within the same org etc.,

Implementation is not an easy task with heroku here as you need to be completely aware of heroku platform and its capabilities.

You need to change some settings on both the sides. But as we have a few trailhead chapters specially for training, it is of a lot of help

We are still exploring the platform and integration. As we are in the learning stage, we would be good to provide recommendations once our major go live happens with our next release.

We have made sure our developers are taking advantage all of the features it supports. We can write out a blog with likes, dislikes or recommendations pretty soon.

our service analyst used to have a real time reporting system which was complex but now our team has rolled out a partially new tool for the same purpose. They are finding it easy to observe the real time insights with heroku quick sync

It's a pretty decent cloud based scalable server where I personally like the number of conventions available (like using Postgres database, and no need of updating the file system every now and then) thus can easily scale as my application grows by bettering the database and increasing the number of dynos(Rails instances) and workers. And finally, heroku offers plenty of add-on resources.

Server cost is comparatively expensive(i.e. per instance when compared to renting on Slicehost). The abstraction comes on expense of control. With heroku I cannot get great control over configuration of my application, in terms of hardware, OS, firewall, versions etc. Sometimes I might end up paying little more than I would have paid for comparable capacity in EC2.

Provides great features such as

• Instant Deployment with Git push

• Plenty of Add-on resources

• Processes scaling

• Full Logging and Visibility

• Database integration is pretty simple and effective

• Scaling is straightforward

Finally, developers can focus on product development rather on managing infrastructure - this is especially relevant for small start-up's who need to roll their code quickly into production and focus on new features, not on operations.

Proper build for my applications are what I try to improve where Instant Deployment with Git push are real handy features in Heroku(like Full Logging and Visibility). Heroku offering number of Dyno for upgrade and downgrade app instance is what I love beyond any other services.

Heroku CLI. The Heroku CLI for deploying ruby on rails apps is very easy to use and git workflow is made painless with Heroku. It simplifies tasks like upgrading a Postgresql database which can be done easily from the command line.

The cost. For any development app with limited database tables and accessible to one or two users, deploying to Heroku is a no brainer. But, for production apps, the cost can quickly spiral as more integrations (e.g. New Relic) are added. For the price range of a typical Heroku production app, I feel there are much better solutions out there. While these may not have the ease of use that Heroku can provide, the additional work needed to setup deployment scripts and deploy to a server on Digital Ocean, for example, would be much more cost effective over a long period of time. Also, there are many open-source tools now that can mimic Heroku-like deployments without all of the costs.

Consider cost as well as usability/ease of use

Working with internal QA teams that need to see latest development changes instantly. Also, managing multiple development environments. With Heroku I can quickly get a new environment up for other team members to review.

Heroku is insanely easy to use, has a ton of buildpacks which you can fork and make your own. it supports python, ruby, java and all the languages you want to develop.

You write a normal local web app, add one file and use a CLI to push.

Everything is simple and fast and nothing weird.

It would be nice to have a GUI, more free options, free data services and open source container.

Try the free one, deploy one small application of the language and framework you are using, say Ruby on Rails with Postgresql. Test it and have your developers use the CLI, If it meets your needs jump in and buy some month to month. Try some data services.

Develop and deploy applications quickly without internal red tape or setup issues.

This was realized, very fast and easy to deploy applications in a production mode. Also Heroku works very well for Facebook applications.

I like that provisioning of any web application or service is very easy. You souldn't learn how to configure the servers or how to customize them to give you the best performance. On Heroku Enterprise you can, also, increase the scalability of any application and the support team is very very experienced and helps you with any thing regarding network issues, downtimes, servers configuration, so on.

I and my team didn't find any issues or things that we dislike until now.

If you search for a really customized PaaS, go for Heroku. It's the right choice.

My team doesn't need to configure the servers for our application. Continuous integration, testing servers, mail server, GIT server, Sonar server installation is very complicated for a huge application environment. With Heroku Enterprise, we just configure elelments and we are up to go if we want to extend features.

Super easy way to get an environment up and running for most startups using the web on a variety of hosts such as Node or Rails.

Maintenance and simple integration with GitHub are also pretty good.

Also has a rich supply of add-ons to make life easy, such as MQ, DB's etc.

It's so easy to use you need to be disciplined at making sure you clean up after yourself to avoid spiraling costs.

For example, if you create a follower DB to us as a backup, make sure you delete it after use!

Does not really give you any detailed metrics on server performance, some basic stuff is there, but you have to pay for something like New Relic to get more detail.

In a startup environment, agility rules, and Heroku offers just that.

How easy the application is for users to use and the flexibility and stability it provides a organization. You can host Heroku in the cloud and don't have to worry about having the overhead of any equipment on sight. This is a pretty cool application to have and use.

There isn't much that I dislike, if I had to say it would be pricing depending on what you need. Depending how much you need to scale or how fast your business grows it could get pretty expensive pretty fast. So depending on financial resources would determine if scaling is feasible.

N/A

Customer mobile application and tracking of user data. A mobile app that allows our customers to login and track their progress for the Immunotheraphy they are on. Allow the user to stay compliance.

Quite possibly the greatest aspect of using Heroku is the shear simplicity of working with the system. Whether you're building a Ruby, Node or PHP app, its as simple as running a command from your source directory. Heroku just gets out of your way and lets you work your own magic.

One of the only things I dislike about Heroku is the pricing model compared to some of the other PaaS solutions that are competitors. Based on the size of your app though, this may not be an issue as the cost comes with using, arguably, the leader in the space.

Definitely start with the free tier and see how the deployment mechanisms and processes fit within your existing setup. It shouldn't be an issue, but its definitely a change for some people. Additionally, Heroku Database is based on Postgres; its not the only platform available, but others require add-on functionality.

The largest problem I solve using Heroku is reducing the time-frame for putting out POC's. It's DEAD simple to get something live and in front of users with very minimal effort and management on your part. Being able to do this in pretty much every popular language is a really huge benefit as you don't have to jump from solution to solution.

Fast integration with NodeJS, mongoDB, and other new technologies and also with git.

Great documentation.

Any app in heroku runs smooth and fast.

Bad error log, I had some troubles building my app, and the errors those heroku give me to understand what is happening were REALLY bad, I spend a lot of time researching about issues, and many time there were package problem, or errors in the package.json.

Debugging in heroku is almost imposible.

Improve debugging, the integration system works really good, but if any problem appears it's almost imposible to find a solution quickly, that is the main problem with heroku server that I had.

I use heroku to build mobile app backends, as API services.

And also same pages or prototyping.

I love its flexibility and ease of use. My colleagues who did not have previous experience with the platform were able to pick it up very quickly. I also love how we can customie the layout easily and continually upgrade our capabilities.

Sometimes it's TOO flexible for people who are not excited by technology.

Everything is just faster and easier.

support for existing development languages, ease of deployment, plug & play assembly of apps using standard components. The Patterns they released were great. The new Elements are awesome. Excited to see where this grows!

What's not to like? Love it. I wish the Heroku Connect was cheaper - but that will come in time.

Try it for free - you won't regret it.

It's my swiss-army nice to solve lots of "edge of the system" use cases - without having to use a bunch of 3rd party tools that each have their own issues / licensing, etc. Able to rapidly prototype a mobile proof of concept for a prospective customer - then quickly iterate it into production and scale it up.

Installation with a Mac is flawless, and accessing the server is easy. The documentation available online is also phenomenal. You can always find something that will lead you in the right direction if you are unsure about something.

I wish Heroku was not only a read-only file system. This would allow users to deploy scripts. For example, I am building a mobile application that requires me to POST to a server with a list of variables and then run a script that calls an external API with these variables.

Heroku will definitely help your start-up if you want to get up and running quickly. In terms of scalability, you will not have to worry about much since the service can handle an immense amount of data.

Heroku eliminates the need to have house your own servers on your company's premises, and its cost is a mere fraction of what it would take to set this level of scalability up yourself.

In addition, if you want to use Heroku for testing your product with remote servers, you can very easily!

Integration with Amazon EC2 has solved the read-only problem, and it has allowed my mobile application to send and receive data to and from the database.

Heroku enforces the best practices listed in the 12 factor app. It makes it really easy to build a completely decoupled app. I like how it encourages using addons for different services. It might lead to a higher cost in the longer run but you can always replace an addon with your own service.

Sometimes debugging is hard because I can't ssh into the running dyno. Also, I noticed that sometimes the dyno would just become very sluggish for a few seconds. Turns out it's because another app is starving our app of CPU time. This went away after switching to performance dynos, but those are very expensive.

It's really good to prototype new software, to the point I'll never consider anything else for prototyping. Scaling heroku is hard and expensive though.

I work in the mobile payments space. As a startup, we had a very small tech team and heroku allowed us to focus on development and features rather than devops.

All rails developers know the virtues of Heroku and will tell you it's one of the great things about building in RoR.

I think Heroku's tiered pricing structure should be more favorable to smaller datasets. The bd im currently working with has about 200k rows and this puts me in the third pricing bracket. And this app has no funding so this will come out of pocket. I think people at my level should still be first or second tier and then up the rates on customers who are truely big data.

It takes a lot of the fragmentation out of hosting and is basically the one stop shop for launching RoR apps.

The Heroku command line tool chain makes it so easy as a developer to deploy nearly anything within a matter of seconds, it's second-nature to use Heroku by default when deploying any project, be it of corporate scale or side project.

The pricing, as soon as you're more than the default first dyno, gets pretty hefty pretty fast.

If you're a developer who writes open source software, do the world a favor and add the Heroku Button to your project.

Scale and development speed; the main benefit is that neither do I need to learn any sysadmin personally nor will I have to find a sysadmin in a startup context.

It's extremely simple to deploy apps; the auto-detection for app type (e.g. Django, MEAN...) works pretty well, and the setup for Procfiles is easy enough to follow with the official docs.

In some edge cases, Heroku can be tricky to set up. Most of the examples I've encountered are in esoteric Python packages (where installation can be tricky) or if you need to host a bunch of static content on AWS (since you can't really use Heroku as a vanilla filesystem -- not to imply that you should be able to, since that isn't the intended use).

I've mostly used Heroku as a quick way to host web apps, both for hobbies and for smaller web design contracting projects. The benefit is usually in the quick deployment, especially after initial setup. Git push to deploy is fantastic.

How easy it is to deploy and quick you can get a web app up and running.

It is very expensive and it can difficult to troubleshoot at times.

Consider how long it would you take you to setup an Amazon EC2 instance just so you could start deploying and it's clear you should use Heroku as at least a starting point.

The business problem is how do you quickly and easily deploy a web app.

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.

Heroku platform is fast upgrading, worth giving a try!

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.

setup time, ease of use, no maintenance, easy backup management

I can't really think of anything. I guess that if I started scaling this service will start being a bit expansive

Try it out with some POC app you'r building.

Rails website with postgres. using the pg backups.

the best benefits are simply deploying fast and simple no annoying setup time. start with a free package and go on from there.