Google Cloud Run enables users to build and deploy scalable containerized apps written in any language (including Go, Python, Java, Node.js, .NET, and Ruby) on a fully managed platform. Cloud Run can be paired with other container ecosystem tools, including Google's Cloud Build, Cloud Code, Artifact Registry, and Docker. And it features out-of-the-box integration with Cloud Monitoring, Cloud Logging, Cloud Trace, and Error Reporting to ensure the health of an application.
N/A
Heroku Platform
Score 7.8 out of 10
N/A
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
SolarWinds Database Performance Analyzer
Score 5.6 out of 10
N/A
SolarWinds Database Performance Analyzer (DPA) enables deep visibility into database performance and expert advice for performance optimization and tuning. What can you monitor with DPA? Oracle Oracle Exadata Oracle EBS Microsoft SQL Server Azure SQL Database Azure SQL Database Managed Instance MySQL DB2 SAP ASE Aurora MariaDB DPA monitors physical, virtual,…
N/A
Pricing
Google Cloud Run
Heroku Platform
SolarWinds Database Performance Analyzer
Editions & Modules
No answers on this topic
Production
$25.00
per month
Advanced
$250.00
per month
No answers on this topic
Offerings
Pricing Offerings
Google Cloud Run
Heroku Platform
SolarWinds Database Performance Analyzer
Free Trial
Yes
No
Yes
Free/Freemium Version
Yes
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Optional
Additional Details
—
—
—
More Pricing Information
Community Pulse
Google Cloud Run
Heroku Platform
SolarWinds Database Performance Analyzer
Considered Multiple Products
Google Cloud Run
Verified User
Engineer
Chose Google Cloud Run
Google Cloud Run is integrated into GCP resources, admin, and billing. But it is not as easy to use as some other platforms like Heroku.
Microservices and RestFul API application as it is fast and reliant. Seamless integration with event triggers such as pubsub or event arc, so you can easily integrate that with usecases with file uploads, database changes, etc. Basically great with short-lived tasks, if however, you have long-running processses, Cloud Run might not be idle for this. For example if you have a long running data processing task, other solutions such as kubeflow pipelines or dataflow are more suited for this kind of tasks. Cloud Run is also stateless, so if you need memory, you will have to connect an external database.
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.
This is an easy 10 because I actually have recommended this product to multiple clients and colleagues! Any shop that writes its own SQL queries will benefit from the insight provided by SolarWinds Database Performance Analyzer, so they know which of their queries is causing a bottleneck. Small shops or databases with only a few tables likely will see far fewer opportunities for optimization.
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.
The UI can be made simpler. Currently the UI is bloated and it takes time to find out what you want
More integrations with container registry providers (ECR, dockerhub)
Better permissions UX. Currently GCP requires service accounts to be used with cloud products, the experience adding/removing permissions is difficult to navigate
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.
Alerts seem to be lacking in DPA compared to competitor's tools. They can be setup but are not quite as easy or as helpful as some other tools I have used.
Grooming/pruning the repository database isn't very easy. We don't manage a lot of instances but our repo DB has grown pretty significantly.
At times when I am drilled-down to a chart, it can be difficult to navigate around from that point to another time range/query/metric.
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.
We have relied on this product for a very long time and it continues to exceed expectations. The product is a vital part of our organization at this point, it would not be very ideal for us to abandon it. We use it almost every day and depend on its alerts for critical parts of our business
The UI/console is great... the documentation is top-notch for developers, but the CLI itself when you have to script around it is very complex and easy to forget some options... the downside of a generic command line client.
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.
I don't want to think about managing clusters of SQL servers in the future without this tool. We have demoed other tools and SolarWinds Database Performance Analyzer is the gold standard for usability and insight into what your servers are doing. The UI is a bit dated, but everything is laid out in a logical manner and drilling down into queries or timeslices is extremely intuitive.
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.
I have had to use their support on a few occasions, for reasons that I am not clear about until recently I have always had problems upgrading the software (although the last 2 updates have gone without issue which I am very pleased to say). On those unfortunate occasions, the support has been brilliant with either excellently documented guides on how to resolve the issue by myself or have been hands-on with calls and screen sharing to remotely fix the issue. Every time the problem was sorted and more importantly, nothing was lost (apart from a bit of time). And as I stated above whatever the problem was that was causing my upgrade issues appears to have been resolved in the last 2 updates.
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.
Follow the guidelines for the capacity of the servers. We found that the DPA databases were getting rather large and also that there are ways to reduce their size built into some of the options.
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.
At the time, we found SolarWinds Database Performance Analyzer to be easier to setup and to have a richer feature set than Redgate SQL Monitor, plus, from what I remember, the DPA pricing worked better for us over the course of a year. We're very happy with all the features DPA has to offer.