The Heroku Platform, now from Salesforce, is a platform-as-a-service based on
a managed container system, with integrated data services and ecosystem for deploying modern apps. It takes an app-centric
approach for software delivery, integrated with developer tools and
workflows. It’s three main tool are: Heroku Developer Experience (DX), Heroku
Operational Experience (OpEx), and Heroku Runtime.
Heroku Developer Experience (DX)
Developers deploy directly from tools like…
$85
per month
Netlify Platform
Score 10.0 out of 10
N/A
Netlify is a platform for developers from the company of the same name in San Francisco, used to build performant and dynamic web sites, e-commerce stores and applications. By uniting an ecosystem of technologies, services and APIs into one workflow.
Heroku provides backend server capabilities, meaning its configuration is slightly more complex and involved than Netlify Platform. Netlify Platform trades off ease off deployment for limited hosting capabilities
To me, Netlify is the gold standard for static web hosting, but each alternative has specific situations where it might fit better. If building a Next.js site, then Vercel is the easiest solution for hosting. For Jekyll, GitHub Pages might make more sense. Other than that, I …
Netlify is best for static websites (JAM stack websites) hosting. It supports continuous integration and continuous deployment out of the box which is not there in Firebase or Heroku. It uses CDN, which optimizes images, videos, and documents on the fly. In short, Netlify is …
Heroku is very well suited for startups looking to get a server stack up and running quickly. There is little to no overhead when managing your instances. However, you'll need a background in basic DevOps or system management to make sure everything is set up correctly. In addition, it's easy to accidentally go crazy on pricing. Make sure you're only creating the server instances you need to run the base application and set up an auto-scaler plugin to handle peaks.
Netlify is a static website host, so it obviously wouldn't work for hosting dynamic websites built in PHP, such as WordPress or Drupal. It works very well with static sites with a git codebase on something like GitHub. It has automatic deployments, which include preview websites. It works very well with this workflow. There are solutions for allowing content authoring on static websites on Netlify, but I would probably reach for something like WordPress or Drupal for that.
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.
I can connect Github/Gitlab repos or drag and drop code folders directly to host them onto the platform, and can customize build and publish details. It handles all granular details itself, so I don't have to worry about configuring everything like I would have to do on an IaaS like AWS
Netlify Platform has inbuilt scalability support - meaning automatic upgrading of servers to handle traffic, without us needing to do anything at all, again, unlike IaaS, where we'd have to manually configure scaling
It has a built in CDN, meaning static applications can be served blazing fast over the web without worrying about traffic or latency
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.
Heroku is easy to use, services a ton of functions for you out of the box, and provides a means to get a software product off the ground and managed quickly and easily. The tools provide allows a small to medium size org to move very quickly. The CLI tools provided make managing an entire technical infrastructure simple.
Easy to use web based console and easy to use command line tools; deployment is done directly from a GIT repository. What more could you ask for? The one thing that keeps me from giving it a 10 is that custom build packs are almost incomprehensible. We used one for a while because we needed cairo graphics processing. Fortunately, I was able to figure out a different way to do what we needed so that we could get off the custom build pack.
We interact with the CLI via our CI/CD pipeline. It was very straightforward to get set up, and their documentation is thorough. There are a ton of examples online of various setups. We needed to deploy a React SPA, so we required redirects, which was straightforward with Netlify.
Heroku availability correlates pretty strongly to AWS US EAST availability. We had a couple of times where there was a Heroku-specific issue but not for the last 7-8 months.
I've used it for many years without facing any major problem. It's not hard at all to get used to it, it's documentation is outstanding and simple. We are close to 2020 and I don't think most of the existing companies or startups should still face old problems such as wasting time deploying code and calculate computing resources.
Be ready to pay a bit more than expected in the beginning if you're migrating from a big server. The application is probably not ready for the change and you have to keep improving it with time.
It's also important to consider that you can't save anything to the disc as it will be lost when your application restarts, so you have to think about using something like S3.
Heroku is the more expensive option for hosting compared to some of the cloud platforms we investigated, but it's worth it for us because of the plug-and-play nature of Heroku deployment. We can be up and running in a few minutes and know with precision how much it will cost us each month to run the application, unlike Amazon Web Services where you have to go to great pains to configure it correctly or else you might end up with a shocking monthly bill. Overall, spending the time to configure Amazon Web Services or one of its competitors is likely the more affordable and powerful choice, because you have control over so many specifics of the configuration. But it also requires the burden of continuing to maintain and update your AWS instance, whereas with Heroku they take care of security fixes and platform upgrades. It's a great service and we are happy to pay the extra cost for the value-adds Heroku provides.
Netlify Platform is the first choice that we are using in this organization continuously and it's been a very promising platform to use. It also maintains the things very well. it also giving a very good updates. It is very easy to use and very easy to learn. overall it is good.