DevOps is something almost everyone is thinking about—but not everyone has an action plan. Part of the problem may be that DevOps might sound like yet another complex, specialized initiative to be squeezed onto an already full plate.
However, DevOps is something you can and should begin to integrate into what you are doing right now. It boils down to this imperative: moduNo matter the style of development, tools and techniques should be integrated into workflow strategically to make people more productive.
Business application developers, for example, should find deployment to be smooth and simple, with a lot of the complexity managed in the background. Code-style developers, on the other hand, look for configuration-based automation—and they want complete control and visibility.
DevOps is all about eliminating the issues that sometimes arise between development and IT operations. Although you may not have an official DevOps initiative, you still have to manage that development-to-production process and all that it entails. You need to make sure that where IT Operations is not included in the initial application planning process, a developer doesn’t just “throw the app over the fence” to have someone else deploy, manage and monitor it.
Similarly, with agile-style development, which is focused on paring back development cycles, simply getting an application finished means little if you can’t test, deploy and manage the different environments. You can select a DevOps approach that is appropriate for the type of developers involved in the application process.
GUI style developers and business analyst-type developers probably need a DevOps process that is obfuscated. The same thing holds true for enabling a citizen, or line of business, developer.
This category of developer simply won’t care, or at least won’t want to be bothered, by all that is involved in deploying the application to different environments, managing different environments, managing version control, or anything else too “techy.” For this audience, making use of a low code approach requires that the app dev platform take care of all of the deployment work automatically while providing the IT organization oversight and choice of the appropriate cloud infrastructure.
Low-code development platforms are gaining momentum. Developers and IT organizations can boost their ability to deliver by getting on board. A high-productivity PaaS solution such as Progress® Pacific™ can fit the bill, improving productivity and providing IT with visibility and control over the direction and output of work.
The other side of the coin is the code-style developer assembling applications from components and writing code to glue them together. While these developers are more familiar with the deployment process, you should still try to use automation that allows them to focus on developing the app—automation designed to facilitate DevOps.
To accomplish that, you can rely on a platform that is focused on deployment, such as Modulus™. Such a high control platform allows you to automate deployment, scaling and more, while providing you the ability to monitor and adjust. While Modulus provides more control appropriate to code-style developers and IT Ops professionals, it is still automated and allows the developer to focus on development, not deployment tasks.
DevOps is worth leveraging as a means to achieve a range of development goals–and something you can do right away.
Mark Troester is the Vice President of Strategy at Progress. He guides the strategic go-to-market efforts for the Progress cognitive-first strategy. Mark has extensive experience in bringing application development and big data products to market. Previously, he led product marketing efforts at Sonatype, SAS and Progress DataDirect. Before these positions, Mark worked as a developer and developer manager for start-ups and enterprises alike. You can find him on LinkedIn or @mtroester on Twitter.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.