PaaS and DevOps beat the same stage

When people talk about PaaS and cloud computing, they often create a lot of confusion and misunderstanding. This article is designed to address these misconceptions, especially with respect to PaaS, so the authors found Jboss 'former CTO, now Cloudbees' CEO Sacha Labourey, and Labourey acknowledged that PaaS only serves organizations that use the DevOps approach to software development. Here's how he said it:

Misunderstanding: I just follow the DevOps method on it, PaaS does not make any sense

In dealing with many things, everyone makes habitual comparisons and accordingly puts forward some objections. By the way, it creates a sense of tension that forces others to make choices based on their comparison. Now, there is an active thread clouderati echo room concept that the concept of Platform as a Service (PaaS) delivers NoOps ready to compete with DevOps. Who would you like? DevOps or NoOps? Controversial point is that this topic is that they must be allowed to see a particular market sector it is successful.

Returning to the real world, IT staff are more concerned with solving some of the challenges they face in deploying, expanding , and updating so as to ensure the operation of complex systems and scarce resources and to change business instructions. The scope of IT growth has moved from mainframes more than a decade ago to fully virtualized environments; a key IT operational activity is building bottom-up servers and virtual machines to run business systems and applications. Over time, these environments must also work smoothly. From an operational point of view, organizations are working on such solutions, and in their view organizations are more concerned with infrastructure orchestration and automation.

When these organizations started using the cloud, they quickly discovered that eliminating the overhead of using automation was necessary: ​​not only because it was the only way to benefit from cloud attributes such as on-demand billing and resiliency, but also because It is the only way to run a dependable environment on the top level, with resources coming and going. There's no need to do it on purpose, and organizations need to deliver on an ongoing basis if they want to succeed on the cloud and become DevOps experts.

PaaS contrast

On the other hand, one of the things that often happens is that the adoption of PaaS is line-driven, but in times of need or driven by developers and quality assurance who help upgrade their processes so that products Finish faster and have higher quality. These teams are not driven from the bottom up; instead, they are top-down and focus on all of their applications for business concerts. As its name implies, its ideal people will be NoOps, operations and DevOps personnel delivered by PaaS providers. As a result, it has become a common practice to keep getting involved in implementing, testing, phasing and deploying applications.

So what is your definition of your own organization? Uh, most likely both! Part of the cloud deployment will come from IT operators migrating or scaling existing systems and applications to the cloud, and DevOps will do that. The other part of the cloud deployment, most likely a new application, will come from the development team and have no specific or historical need for a custom bottom-up stack. In spite of this, most of these new applications have the need to have system connectivity or interaction with the present, and these systems are met by IT and maintained.

Summary: In both cases, bottom-up for DevOps, and top-down for NoOps, the goal is to deliver to end-users while continuous delivery is the intersection of the two.