Apache Airflow vs. Control-M

For a quick job scanning of status and deep-diving into job issues, details, and flows, AirFlow does a good job. No fuss, no muss. The low learning curve as the UI is very straightforward, and navigating it will be familiar after spending some time using it. Our requirements are pretty simple. Job scheduler, workflows, and monitoring. The jobs we run are >100, but still is a lot to review and troubleshoot when jobs don't run. So when managing large jobs, AirFlow dated UI can be a bit of a drawback.

Incentivized

Control-M processes about 10,000 jobs starting every day in our production environment, and adding new jobs is very simple. We don't feel any pressure on Control-M because it is processing multiple jobs in parallel. As a developer, I created an account in the BMC community to get help and support. We post there rarely because sometimes we need solutions very quickly and don't have time to connect with the guys on the Control-M help desk. If BMC adds more videos or notes on scenario-based content, then it will be more helpful.

Incentivized

• Apache Airflow is one of the best Orchestration platforms and a go-to scheduler for teams building a data platform or pipelines.
• Apache Airflow supports multiple operators, such as the Databricks, Spark, and Python operators. All of these provide us with functionality to implement any business logic.
• Apache Airflow is highly scalable, and we can run a large number of DAGs with ease. It provided HA and replication for workers. Maintaining airflow deployments is very easy, even for smaller teams, and we also get lots of metrics for observability.

Incentivized

• Workload change manager is one of our favorite features of this product. It enforces standards, which is a huge benefit. Users don't just make crazy changes that cause issues with other jobs. It does great promotions from one environment to another, transforming all the data to match the next environment.

Incentivized

• A local "dry run" or IDE plugin that can validate and simulate DAG execution without needing a full environment.
• Better feedback on DAG parse errors in the UI or CLI.
• Navigating large DAGs with hundreds of tasks can be slow and hard to understand visually.

Incentivized

• I haven't come across too many spots where I'm not happy with the product. Most of the shortfalls were in my knowledge of the product as opposed to the actual product. Currently we're having a little bit of an issue with the deployment of the software to the servers, but it's more of an "us" problem than a product problem. I can't really give any good examples of shortfalls of the product that I've found so far.

Incentivized

It is one of the best solutions on the market, in terms of innovation, reliability and stability. Control-M provides security when used by the largest companies in Mexico such as banks, department stores and logistics. It has proven to be able to integrate with new technologies on the market and provide almost 100% availability, thanks to its automatic FailOver scheme.

Incentivized

For its capability to connect with multicloud environments. Access Control management is something that we don't get in all the schedulers and orchestrators. But although it provides so many flexibility and options to due to python , some level of knowledge of python is needed to be able to build workflows.

Incentivized

It has an excellent graphical user interface and robust functionalities, which any scheduling tool currently has in the current market. Strengthening security measures, such as role-based access control and encryption, is essential to protect sensitive data. Providing tools to optimize resource utilization and reduce costs would be valuable. Limited options for customizing the user interface can hinder productivity. Allowing users to tailor the interface to their needs would enhance the experience.

Incentivized

Secondary Instances: Control-M supports the installation of a secondary instance of the entire Control-M environment, Control-M/EM, or Control-M/Server.Automatic & Manual Failover: In case of a failure on the primary host, Control-M can automatically failover to the secondary host if using Oracle or MSSQL databases. Manual failover is also an option, enabling a controlled switch during planned maintenance.Fallback: After resolving the issue on the primary host, you can easily fall back to it, or even designate the secondary host as the new primary. Database Replication: For high availability, Control-M leverages database replication from the primary site to a disaster recovery site. While replication is essential, its implementation and maintenance are the user's responsibility.

good page load times, efficient report completion, and minimal impact on integrated systems. Specifically, the well-designed GUI contributes to a positive user experience, and the platform's ability to automate various stages of the workflow, including Big Data processes, is highlighted as a key strength. Fast Page Loads: Control-M is reported to have a responsive user interface with fast page load times, allowing users to quickly navigate and manage their workflows

He contactado varias veces con el soporte de BMC y ha sido bastante bueno, siempre han sabido darme una solución a lo que he pedido. Esta vez quiero hacer alguna nueva pregunta, pero no se si se me podrá contestar, ya que es algo que tal vez fuera de otro rango y no pertenezca a ellos.

Incentivized

Very knowledgeable instructors provide a hands-on, collaborative learning experience and can interact directly with instructors to develop our Control-M skills. This format allows for immediate feedback, in-depth discussions, and tailored guidance, leading to a deeper understanding of Control-M concepts and practical application. Face-to-face interaction fosters higher engagement and a more dynamic learning environment.

Incentivized

Simple and easy to use web based, well paced. Available any time. All online courses are simple and easy to access and use. Very practical everyday use scenarios and solutions. Incorporates software simulations, learning games, and built-in assessments to enhance comprehension and engagement. Online subscriptions are regularly updated with the latest product information, ensuring users have access to the most current knowledge.

Incentivized

As HA we have depend on the external DB, why don't we have HA feasibility with embedded DB. As with external DB, there are performance issues and fine tuning the DB. As if its embedded DB, Control-M it self take care of the functionality.

Incentivized

Apache Airflow is suited for a much wider set of use cases compared to Databricks. You can run it anywhere, and there is also no vendor lock-in. With Airflow, we can utilize almost any compute engine. Same thing we want to do with Databricks. There might be some level of difficulty based on the support.

Incentivized

Jenkins is a user-friendly tool, but it doesn't offer the same blend of features that Control-M has. Often, Jenkins jobs become stuck, but Control-M typically doesn't; instead, it generates an alert to the designated email recipient. In the case of production, this act is so quick

Incentivized

awesome product.Control-M delivers advanced operational capabilities easily consumed by Dev, Ops, data teams, and lines of business.Control-M Workflow InsightsApplication and data workflow observability: Increased confidence that SLAs are being met for Control-M users and IT leadersComprehensive control and management capabilities: Enhanced dashboards and reporting with constant telemetry and intelligent analysis on executing workflowsSelf-service visibility: In-depth reporting to help teams work autonomously

• Most of the ETL processes were automated, cutting down on human labor.
• Apache Airflow's user interface (UI) was very informative and straightforward.
• Since ETL processes were providing data via airflow, we were able to gain a deeper comprehension of the data at hand.

Incentivized

• Since centralizing all our workflows in Control-M, we've cut end to end processing time by nearly 30%
• Before Control-M we were babysitting scripts, manually rerunning failed jobs, and chasing ghost errors. With automated recovery, smart notifications, and fewer failures slipping through the cracks, we have saved 3 hours a day across teams
• Our workflows success rate sits at 99.95% and when things do fail, they are pinpointed immediately

Incentivized