Opsera announced that two new patents have been issued for its Unified DevOps Platform, now totaling nine patents issued for the cloud-native DevOps Platform.
When infrastructure-as-code (IaC) burst onto the scene in 2006, it was a game-changer. Not only did it redefine the way software engineers and operations thought about the provisioning and maintenance of infrastructure, but it also allowed teams to treat infrastructure like product code — meaning changes were now easy to track, repeatable, iterative, and recoverable. By combining the same tools as any other software project with IaC, developers were able to rapidly deploy applications. Today, IaC is regularly used by DevOps teams.
However, the increasing complexity of things like data center configurations, security requirements, and rapidly changing guidelines means IaC is poised for an overhaul. New technologies and techniques can help solve many of the challenges IaC presents.
IaC Workflow
Today, most enterprises are moving towards cloud-based infrastructure where deployments are 100% software-driven and underlying resources are standardized. The myriad of today's off-the-shelf components and services allow developers to create complex applications that can work at scale either on-prem or in the cloud. While this provides flexibility and agility in terms of application development, the proliferation of these components and services has created a drastic uptick in fragmentation throughout the infrastructure. In other words, they are deploying IaC.
Infrastructure-as-code is the process of managing and provisioning computer data centers through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. To create a successful IaC workflow, first, you must create the base infrastructure, then build out the platform/application services, conduct application provisioning or CI/CD, and run application monitoring.
Fundamentally, IaC requires DevOps engineers to have a lot of subject matter expertise, in-depth knowledge of security configurations and compliance standards, and the ability to code well. Simply put, IaC has created a unicorn skillset. Developers are not operators and operators are not developers.
While IaC shines at creating the base infrastructure and building out the platform/application services, it is strongly lacking in provisioning, application monitoring, and CI/CD. In other words, DevOps teams' needs have outgrown what IaC can provide.
IaC Needs to Operate at a Higher Level of Abstraction
To meet today's DevOps teams' needs, IaC needs to operate at a higher level of abstraction. To do that, you need the following:
1. Application-centric automation: Application-centric infrastructure configures and displays the entire application ecosystem — allowing administrators to manage a single system for application delivery instead of managing individual servers. It encompasses the virtualization of the data center and incorporates automated load-balancing, on-demand provisioning, and the ability to scale network resources as needed.
2. A rules-based engine: Application-centric automation by itself isn't enough. We need a rules-based engine that can take app-centric information and automatically run the rules to make sure that the software is compliant with the relevant security standards.
3. Self-service with guardrails for developers: Developers want to focus on building applications — not infrastructure. With code automation, developers can ask for secured resources without having to know tons of lower-level details to meet operations or accidentally violating the needed compliance and security requirements.
As you can see, IaC will need to evolve dramatically to meet the needs of today. Already, new technologies such as no-code/low code are addressing many of the shortcomings of IaC. It's only a matter of time before more companies adopt them.
Industry News
mabl announced the addition of mobile application testing to its platform.
Spectro Cloud announced the achievement of a new Amazon Web Services (AWS) Competency designation.
GitLab announced the general availability of GitLab Duo Chat.
SmartBear announced a new version of its API design and documentation tool, SwaggerHub, integrating Stoplight’s API open source tools.
Red Hat announced updates to Red Hat Trusted Software Supply Chain.
Tricentis announced the latest update to the company’s AI offerings with the launch of Tricentis Copilot, a suite of solutions leveraging generative AI to enhance productivity throughout the entire testing lifecycle.
CIQ launched fully supported, upstream stable kernels for Rocky Linux via the CIQ Enterprise Linux Platform, providing enhanced performance, hardware compatibility and security.
Redgate launched an enterprise version of its database monitoring tool, providing a range of new features to address the challenges of scale and complexity faced by larger organizations.
Snyk announced the expansion of its current partnership with Google Cloud to advance secure code generated by Google Cloud’s generative-AI-powered collaborator service, Gemini Code Assist.
Kong announced the commercial availability of Kong Konnect Dedicated Cloud Gateways on Amazon Web Services (AWS).
Pegasystems announced the general availability of Pega Infinity ’24.1™.
Sylabs announces the launch of a new certification focusing on the Singularity container platform.
OpenText™ announced Cloud Editions (CE) 24.2, including OpenText DevOps Cloud and OpenText™ DevOps Aviator.
Postman announced its acquisition of Orbit, the community growth platform for developer companies.