Introduction
One of the lesser-known ways savvy engineers are innovating automation may surprise you. In a world where most activities are handled by scripts and orchestration of myriad specialized tools, low-code DevOps has emerged to promise ways to deploy, monitor, and self-heal applications. By providing an efficient means of rapid prototyping with reduced complexity, it significantly reduces operational toil.
What is Low-code DevOps?
Simply put, low-code DevOps is a combination of software development and IT operations that shorten the development life cycle and provide continuous delivery of high-quality software mostly through configuration, with a minimal amount of code. Low-code DevOps isn’t something that we see a lot of in today’s tech world. One reason is many of the operations that DevOps engineers need to complete still involve a lot of scripting to utilize various CLIs and API endpoints. Implementing tools for low-code DevOps is beneficial for a number of reasons.
One benefit that may actually be mistaken as a deficiency is the overall methodology of low-code itself. Using visual tools and IDEs that “hide” the more esoteric coding language can be seen as non-standard practice. That notion is being challenged for low-code’s use case in DevOps and general engineering. Rather than start with a non-visual and complex step-focused operation, low-code DevOps tooling starts with an initially complete workflow and then expands the details from there.
This is a critical aspect of using low-code DevOps methods. After the initial layout is completed with the help of intuitive low-code tools, more intricate details of the process can be added to create a complete solution. As with other tools, operations and workflows for automation can be templated and implemented for use when a standardized solution is needed.
Tools and methods for Low-code DevOps.
When evaluating any additional tooling to be introduced into your DevOps ecosystem, it should be complementary to your existing automation and development stack. For instance, are your environments contained in a cloud, multi-cloud, or even a hybrid configuration? Does the tool support the stack your development teams focus on? And one big question is can the same tool be used to fulfill the needs of multiple projects?
Similar to having a kitchen tool that does multiple jobs, selecting a tool to help in more than one automation project is a good way to get the most out of a low-code DevOps solution. The goal is to use methods that allow a visual representation of the overall flow, working through as much of the process as possible with configuration alone, and then enhancing with code or script only if absolutely necessary. This is the main goal of using low-code methods to help with DevOps automation.
While the tools we discuss today may not be specific to DevOps, this is the state of low-code development tooling at this time. Expect change as more and more portions of these platforms are further automated. The way the tools are used to create an end-to-end solution is often a mixture of standard usage, customization, and extensibility added by plug-ins and integrated applications.
Mendix
Mendix is at the forefront of Low Code development. They claim that 65% of application development activity will use some type of low-code system by 2024. Their platform boasts a number of features like cloud-native development and deployment, mobile development, and various methods to create workflows.
What makes Mendix’s service offering attractive for Low Code DevOps is the process automation part of the platform. Automating common tasks to remove the human element is not just time-saving, but avoids the potential for human error. Onboarding is a good example of using Mendix workflow and process automation for completing operational tasks. Once a request is created, the data in that request can be used to automate account creation, the configuration of security and building access, and even hardware procurement.
OutSystems
One of the ways OutSystems stands apart is how they have been focusing on DevOps practices from the start. Expanding upon a team’s already established automation is one way they help introduce their Low Code platform as a solution that is viable for DevOps activities.
Recognizing that there are a large number of industry-standard tools like Jenkins, ElasticSearch, and test solutions like Selenium, OutSystems strives to be an end-to-end complete solution, including deployment to various on-premise and cloud environments.
Microsoft Power Apps
If you remember the days of Microsoft’s WYSIWYG IDE for web and desktop apps, you’ll be reminded of it when you look into Power Apps. The difference is that many of the components used in Power Apps are the same familiar Microsoft tools already in use today. Power Apps Portal Studio is the design tool that allows for this level of integration and design for web pages, components, and other data elements.
Integrating aspects of Microsoft Power Apps into a Low Code DevOps procedure, one can anticipate a lot of support and guidance. This is thanks to the documentation that is available from Microsoft and their large user base. Other applications of Power Apps allow for direct integration with data already in systems such as Dynamics 365. Those already doing a lot of development in this platform and Sharepoint would find Microsoft Power Apps a readily adoptable pathway to more automation.
Examples of Low Code automation.
Let’s see the benefits of Low Code DevOps by using some examples. Based on the tools we discussed, the following examples show ways to potentially address shortcomings of existing systems. One might say there’s a potential solution for nearly anything there, it is a simple matter of available time. Using a Low Code method could potentially shorten that time with a stable, value-adding system as the end result. The less time any one solution requires, the more solutions can be reached in the available time.
Mendix Onboarding Request
Mendix provides a good example on their website of an onboarding process. To onboard any new member, many different applications and systems are touched. This also means there are multiple hands involved in handling that request. This type of complexity makes the process slow and prone to blockage and errors.
Rather than depending on the manual portions of this, integration into a workflow allows for many parts to be handled by automation. In this example, once HR creates a record, a decision flow is created to automatically configure phone and laptop details. From there, additional items can be automated to ensure the provisioned laptop and account have access to all required systems. What was once done manually through manual processes in many different systems is replaced by automation that reaches out to actively create, modify, and spark additional actions.
OutSystems helps with CI/CD.
While we would love to say our entire pipeline is automated, seldom do we see the complete end-to-end solution in motion – meaning build, test, deploy and continuous monitoring across that entire process. This is how AI-powered Low Code DevOps platforms help provide additional benefits to an existing deployment scenario.
The built-in logging and instrumentation allows for measurement and improvement in performance across the process. If one portion of the build is slow due to dependencies, part of the platform’s job is to ensure those dependencies are highly available. After the deployment monitoring continues, to show the health of the running application. Actions based on that data is where the extension to Low Code methods can provide considerable value.
Kaholo helps with Low Code orchestration.
As powerful as these tools are, even they benefit from orchestration in order to be at the right level of user-friendliness. Kaholo provides a visual and intuitive way to use workflows to allow everyone involved to have a part in the process. This “democratization” of automation is the key to remove barriers that otherwise threaten to slow or block internal processes.
Orchestration of the many tools that handle source code verisoning, builds, dependency resolution and management, and deployment into that single comprehensive view is what we all strive for. Looking at the large number of integrations available for Kaholo shows that they are prepared for the Low Code DevOps world. Tight integration through visual workflows ensures the maximum usability and maximum utility of all of the tools at your disposal, including aspects of continuous improvement.
Closing
The use of low-code DevOps is quickly gaining momentum. Looking at products and providers like we discussed today, it is clear there is a future where low-code solutions will be commonplace. To prepare for that, it is vital to stay on top of all the new integrations and changes to existing ones.
Rather than task you and your team with that aspect, consider Kaholo as a drop-in solution that handles the menial tasks. Many tools are available that could do something similar, but starting from a vantage of what is important to Low Code DevOps and development helps Kaholo stand above the rest!
