If you are doing or thinking about moving towards DevOps, there may be a conundrum you have to deal with. Some, perhaps many, of the enterprise tools that currently are prevalent in Ops, don’t fit well (I’ve been told I have a talent for understatement) into the Dev “as code” model. That world revolves  around code management systems like Git, automated build tools like Jenkins and configuration management tools like Chef or Puppet. Among those enterprise tools may be workload automation tools that manage your critical business applications.


On the other hand, the tools from the DevOps ecosystem that do fit well into the “as code” model, may be immature and basic (after all, building Rome was not the only project that took longer than a day) and may require developers to spend an inordinate amount of time scripting and integrating and instrumenting. That might be OK if they didn’t already have a day job or if they could miraculously develop sophisticated instrumentation that has taken the industry decades to evolve.


We believe the best approach is to take the leading solution for automating business applications, one that has already proven itself to be highly flexible and adaptable through decades of evolution from mainframe to distributed systems to big data to business-aware monitoring to self-service, and evolve it further to embrace and support the DevOps ecosystem.


That is the concept of Jobs-As-Code as implemented by Control-M. Take the best operational instrumentation for batch workflows, expose its functions via RESTful APIs, enable object definition using a familiar notation for construction (JSON), provide support for programmatic provisioning to support automated testing and generally make it simple to embed into whatever CI/CD tool chain you are already using. Make sure that all of the existing capabilities that have made this solution the leader over decades (the ONLY solution in the Leader Quadrant in Gartner’s Magic Quadrant since 2001) are fully accessible and dovetail seamlessly with the newly added automation capabilities and voilà. Done and dusted.


We’ll be showing Jobs-as-Code at the DevOps Enterprise Summit in San Francisco Nov. 7 – 9. Come by and take a look.