Deployment as a service directs the journey of code to the cloud
Infrastructure is on the rise. Software application development is driven by many year-over-year trends, but one of the biggest drivers today is the drive to create and enable more powerful, manageable, and flexible controls that work. at the infrastructure level.
Given that the infrastructure is now, in many cases, cloud native and heavily influenced by open source technologies, we can see where many application deployment efforts are now focused.
Deployments as a service
This is a cloud era where we’re not just talking about deploying software and pushing it to live production and later user use cases, this is a time where we can start talking about so-called deployments as a service. technologies.
Not yet abbreviated to an acronym or acronym like DaaS (probably because it’s so close to DataBase-as-a-Service or DBaaS), the industry generally refers to as-a-service deployments as an integral part of ‘Infrastructure-as-Code (IaC), i.e. automated controls to manage the provisioning that applications and data services need for deployment, more closely aligned with the end requirements at the point of departure , creation and publication.
But making this technology work is a problem.
As previously explained here on Forbes, the first generation of DevOps tools designed for Infrastructure-as-Code (IaC) were created before the days of containers and Kubernetes (a very popular cloud container orchestration service) and new kernel-level controls like Cilium.
We need a new era of cloud infrastructure technologies aligned to enable developers and operations teams to use infrastructure as a competitive advantage, not just a lower substrate utility layer which is somehow kind of “right there” – like electricity, water or maybe even slices of white bread.
Seattle-based Pulumi is striving to be part of this new era of infrastructure players. The company’s recently launched Pulumi Deployments service allows software engineers to use infrastructure controls to “spin” (a term used to refer to the creation of a cloud instance due to hard drive spin-up). a cloud server when updated) or update existing cloud applications and components instantly with a Git commit (a small piece of software code designed to perform functions), a click of a button in the user interface ( UI) Pulumi or a “call” to the new Pulumi Deployments REST Application Programming Interface (API).
Built using Pulumi’s multi-language, multi-cloud infrastructure-as-code (IaC) universal platform, Pulumi Deployments provides extensible building blocks that allow users to create any cloud infrastructure. It is a deployment-as-a-service technology to manage IaC tasks and here it is powered by Pulumi Automation API – a programmable IaC technology.
IaC needs library-level wealth
The company explains the Automation API as a technology that answers the question, “What if IaC was a [whole] library [of software code functions and services]not just a CLI CLI [single software command]which enables the development of custom platforms as a service and multi-step workflows, including drift detection.
“[Our] the new services announced take Infrastructure-as-Code (Iac) automation to the next level,” said Joe Duffy, Founder and CEO of Pulumi. “We followed Pulumi’s standard approach of delivering beautiful out-of-the-box experiences, layered on a foundation of highly programmable API building blocks, to unlock innovation for our builder community. »
Duffy points to Pulumi usage data, which he says shows his company’s automation API (which also powers the Pulumi Kubernetes operator and Pulumi GitHub Actions) enables organizations to manage more than ten times the cloud infrastructure resources per engineer versus other infrastructure as code tools.
Developers can now choose from a library of Pulumi architecture patterns that serve as baselines for the industry’s most common cloud architectures on AWS, Microsoft Azure, Google Cloud, and Kubernetes. These templates set up infrastructure-as-code projects that include out-of-the-box best practices, for architectures including containerized microservices, serverless applications, static websites, virtual machines, and Kubernetes clusters. .
Automatic cloud delivery
Developers can select these templates directly in the Pulumi CLI or the Pulumi Service Console. These templates work with Pulumi deployments at launch, enabling automatic delivery to the cloud.
“Old legacy Infrastructure-as-Code (IaC0) tools weren’t enough for us because they lacked the programmability to orchestrate complex multi-cloud deployments and workflows,” said Curtis Bray, director of engineering at Fauna, a distributed relational database company. which provides its services as a cloud API.
Bray says other pain points for his company include the fact that, “Additionally, domain-specific languages (DSLs) like Terraform were bulky, difficult to use, and incompatible with modern software engineering. Thanks to Pulumi’s universal infrastructure-as-code approach, we were able to deliver critical new functionality faster than before, because Pulumi’s programmable model is designed to handle complex, multi-cloud scenarios like ours. .
The takeaway here is clearly underscored by the fact that the tech industry is already talking about cloud computing having older infrastructure-as-code (IaC) tools, i.e. while many organizations may not have deployed the cloud at a deeply penetrating level of their business. , or have taken a cloud-first approach to cloud-native technologies, we are already talking about internal component mechanisms becoming obsolete.
Cloud computing is evolving rapidly, cloud infrastructure is currently evolving even faster than the upper level user layer. MIND THE STEP.