ActiveBatch Workload Automation vs Heroku Platform

• ActiveBatch [Workload Automation] is great for simplifying complex tasks so that users of multiple technical skill levels can create and monitor automated tasks.
• The support team is amazing and will respond with solutions and answers to questions or issues very quickly.
• ActiveBatch [Workload Automation] does a great job of adding new features and enhancements to the product based on customer feedback.

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

• While I like being able to reuse scheduling objects and the like, more work needs to be done to help one not reinvent the same scheduling object without realizing it and to then find scheduling objects that have similar schedules even if they are worded slightly differently than what I'm expecting. It needs to be "smarter". It was easy to accumulate a pool of scheduling objects that while named differently, had exactly the same schedule. It was also hard to sift through to find the little differences between similarly named scheduling objects.
• The logger had a clean enough interface but it could be more legible and offer contextual help to describe the messages one is reading. I remember trying to read black text on a medium gray background with Courier size 10-11 font. Not so easy to read quickly and to parse through the relevant parts. I think some selective color coding would be good and links to message definitions or any form of further information would be nice. Maybe the ability to export the log file to various formats would also be helpful.
• I don't remember a dashboard that at a glance on the top level would highlight what jobs failed completely and which jobs might have warnings or non-critical errors. I got emails because I defined to get them. Maybe again if there was a way to color-code the type of error would be good nice-to-have.

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

• Saves employees time and sanity, from having to manually run tasks at certain times.
• Cost is not overly expensive, considering the amount of platforms it integrates with "out of the box."
• Takes control of sensitive processes, and runs them confidentially. Alerts management when completed.

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