What is our primary use case?
We have around 20 scheduled jobs we run every few hours. These include our price fetching jobs, market tracking jobs, subscription checking jobs, profit calculation jobs, etc. These are pretty long scripts with complex instructions to handle multiple data from a different database, microservice APIs, and many public market exchange APIs. All this data crunching was difficult to perform and maintain before ActiveBatch, however, once we started using ActiveBatch workload automation software, scheduling these jobs and tracking data crunching became easy.
How has it helped my organization?
ActiveBatch has improved our organization by making job scheduling and API integrations very easy to use and to get started with. Earlier, we needed to assign these tasks to a high-paying highly-skilled resource. Now, we can train anyone to do the same job with very little effort. Our operation costs are significantly reduced because of ActiveBatch. Now, anyone can complete automation tasks without much knowledge of how computer API works and with no knowledge of coding. This has made our automation easier.
What is most valuable?
Some of the features we found useful for our use case are:
- Job scheduling. It has helped with scheduling complex jobs with simple scripts.
- API integration. It is very easy to set up regular Rest API calls and data gathering.
- Time Savings. Tracking multiple servers for downtime and multiple jobs logs is very time-consuming. We have to switch between multiple tabs and applications for all this. However, ActiveBatch made it very easy to track the downtime of our own services and logs of our cron jobs very easily.
Overall, we found these valuable
What needs improvement?
Some improvements can be made to the user interface. I personally love to see ActiveBatch keep up with current trends in UI development.
Also, some improvements can definitely can be made to make ActiveBatch more beginner friendly.
The custom theme could be a new feature suggestion for ActiveBatch.
Apart from these, I don't have any suggestions for ActiveBatch. They did a pretty good job of giving the best state-of-the-art features. All of these features are very well thought out and very useful
For how long have I used the solution?
I've used the solution for two years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
The scalability is great. We are onboarding new users, and our number of jobs is growing. We have not faced any problems.
How are customer service and support?
Technical support offers great support with a fast response time.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
ActiveBatch is the first software of this nature that I have used.
How was the initial setup?
The initial setup is straightforward.
What about the implementation team?
We handled the implementation with an in-house team.
What was our ROI?
ActiveBatch gave us a good ROI in our organization.
What's my experience with pricing, setup cost, and licensing?
The features provided in ActiveBatch are worth buying, and the cost makes sense for the number of features provided.
Which other solutions did I evaluate?
We did some research on VMware and IBM Workload Automation.
Which deployment model are you using for this solution?
Public Cloud