AutoSys Workload Automation vs. Azure Batch

In Informatica or Spark ETL jobs loading data into a Data Warehouse using AutoSys Workload Automation triggers ETL pipelines, monitors completion of jobs and also triggers the power bi report refresh. AutoSys Workload Automation can schedule jobs based on file arrival, and provide alerts if any data loads get failed. A small data team managing greater than 100 jobs. Buying and maintaining AutoSys Workload Automation is overkill in terms of cost, complexity and maintenance does not justify the value

Incentivized

To better serve their consumers, businesses that often interact with those clients who rely on Microsoft's software products may consider migrating to Azure. This program would be useful in any installation of a Microsoft product or suite that necessitates a test of the target environment. It is simple to maintain and implement, making it an ideal IT backbone. If a client doesn't have any use for this particular instrument, it's not going to be of any benefit to them.

Incentivized

• AutoSys Workload Automation is our scheduler that automates and monitors workflows across all our system reducing manual runs
• Applications which run over multiples systems(cloud, on premise) are coordinated using AutoSys Workload Automation
• AutoSys Workload Automation clustering or failover ensures that workloads continue without any issue.
• AutoSys Workload Automation maintains execution logs and job history, which helps in compliance, audit trails, and root-cause analysis.

Incentivized

• Managing the users
• Having multiple environments
• Creating multiple groups

Incentivized

• In AutoSys Workload Automation, Workflow and job dependencies are shown in a static way, which makes user difficult to visualize more complex job chains or debug failures in a graphical view.
• Latest schedulers (like Control-M, Airflow) allow more easy workflow design makes user to understand it better, but AutoSys Workload Automation relies heavily on JIL scripts and text-based job definitions.
• AutoSys Workload Automation interface is very slow when searching or filtering over thousand of jobs

Incentivized

• The user interface, in my opinion, might need further clarification.
• Any situation where a user's password has to be reset would benefit from this feature.
• Any accounts that were accidentally established more than once may be transferred over quickly and easily.

Incentivized

AutoSys Workload Automation is a place to schedule, monitor, and manage thousands of jobs. Time, file arrival, dependencies are much very flexible. Once jobs are set up they run consistently with minimal intervention. AutoSys Workload Automation is powerful but very complex o understand. Mainly for beginners the interface is not user friendly. AutoSys Workload Automation is very useful in terms of job scheduling and automation. AutoSys Workload Automation is also useful for strong logging and reporting purpose. AutoSys Workload Automation has reduced a lot of human efforts and manual processing.

Incentivized

In AutoSys Workload Automation, strong legacy presence, proven reliability, slightly simpler for basic scheduling if user already have in-house AutoSys Workload Automation expertise. so we already had investments in AutoSys Workload Automation, trained team, and large numbers of jobs running thus making AutoSys Workload Automation more cost-effective to continue rather than migrate to use AutoSys Workload Automation over Control-M. All our workloads are heavily batch-driven (SAP, ETL) real-time pipelines. AutoSys Workload Automation provides the robustness and enterprise support that Airflow lacks without heavy internal engineering overhead.

Incentivized

They both are great tools and provide the services they have implemented. They are two competing companies that have different cultures and forward mission agendas. I would say Azure is a little easier to support through their user interface for the IT support side of things. Both tools are useful and have their own strength and weakness. If you're a dynamic company with a multitude of customers then both are a required tool to have.

Incentivized

• Critical job process consistently complete on time without delays
• Significant reduction in team effort due to this resources for available for higher-value tasks. Human intervention is reduced due to this incident costs are also reduced.
• Faster incident resolution, improved productivity, and lower downtime.

Incentivized

• After initial setup, we now have significantly less time spent processing data.
• The automation of data formatting and display after processing is exciting because it frees us to focus on the data itself.
• Since using Batch, we have significantly decreased the number of items we previously utilized.

Incentivized