Amazon S3 vs Heroku Platform

• Highly available and redundant; we do not worry about the service having downtime
• Simple usage from multiple different frameworks using Amazon's SDKs, or roll your own
• A large number of bucket policies and security adjustments to tailor usage to customer needs
• Regional support for storing assets in particular locations around the world

Read full review

• Heroku has a very simple deployment model, making it easy to get your application up-and-running with minimal effort. We can focus on our efforts the unique aspects of our application.
• The robust add-on marketplace makes it easy to try out new approaches with minimal effort and investment -- and when we settle on a solution, we can easily scale it.
• Heroku's support is quite good -- their staff is quite technical and willing to get into the weeds to diagnose even complicated problems.

Read full review

• No support for object versions retention: There can be a retention policy(days or number) for object versions that are stored in S3 so that we don't have to worry about paying extra for all the old versions of an object in the bucket.
• No feature for replication within a region: Currently AWS does not support replication within a region. Also, having to enable versioning for buckets in which you need replication makes it even more costly.
• Confusing pricing: The pricing model of S3 can be a little confusing for a new customer with questions regarding data transfer from other AWS services, between buckets or data transfer to the outside world.

Read full review

• Large price jumps between certain resource tiers (2x Dyno for $50 per month versus Performance Dyno for $250). Free Postgres next jumps to $50 per month.
• Marketing/Branding to non-technical stakeholders. As the years pass, I've had to fight more to convince stakeholders on the value of Heroku over AWS.
• Improve Buildpack documentation. This is one area where Heroku's documentation is fairly confusing.

Read full review

• It practically eliminated some real heavy storage servers from our premises and reduced maintenance cost.
• The excellent durability and reliability make sure the return of money you invested in.
• If the objects which are not active or stale, one needs to remove them. Those objects keep adding cost to each billing cycle. If you are handling a really big infrastructure, sometimes this creates quite a huge bill for preserving un-necessary objects/documents.

Read full review

• Heroku allowed us to get up and running fast. Deployment was really easy and connecting to our codebase was, too. The deployment integration with GitHub is pretty slick.
• The add-ons provisioning is so simple and the documentation is so thorough that, at least at first, it means you don't have to hire a dedicated devops person to manage this stuff.
• Heroku has tools that allow the collaborators (those with access to the Heroku dashboard) to be able to quickly and easily do triage from just about anywhere, including your smartphone.

Read full review