Shulou(Shulou.com)06/01 Report--

This article shows you how to analyze the current situation of DevOps and NoOps. The content is concise and easy to understand. It will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

In the current trend of IT, DevOps is a buzzword. It originated from the front-end application of SPA (single page application) a few years ago. I think the normal adaptation of IT technology is that when a new technology breaks out, it will immediately be adopted by sharp people and then spread quickly. This is the case with DevOps in recent years. But in a few years, you will hear another buzzword: NoOps.

Analysis of current situation of DevOps and NoOps Analysis of current situation of DevOps and NoOps

The difference between DevOps and NoOps

DevOps is the integration of development and operation and maintenance, and it is the practice of development and operation engineers working together to define the whole lifecycle process of application from design to delivery.

NoOp means no operation is required. The idea is to remove all platform management parts, thereby reducing friction between developers and infrastructure.

Why do I need DevOps?

As technical and business requirements become more challenging, IT services become more and more complex. This makes delivery more and more important and forces us to put energy into orchestrating the entire application delivery process.

With the cloud platform, the demand for system administrators begins to decline, but the demand for DevOps technology and business skills is still high. Implement DevOps and use it appropriately. This makes us need to consider situations other than technology delivery.

Why didn't there be DevOps before?

There are many answers, and you might say that previous business scenarios were simpler or did not have enough technical culture. I very much agree with the above views, but I do not think those are the root causes. In my experience, the bigger reason should be technology. The automation of delivery is actually very difficult to achieve.

Most systems a decade ago, by default, did not have a step-by-step build or well-defined workflow like git-flow. At that time, there was no cost-effective CI solution, so it was difficult to achieve automated delivery.

I remember that in 2009, I planned to deploy a. Net portal of my own. I spent a Saturday morning trying to create an automated deployment system using open source tools, but in the end I gave up. Because I know that it is much more expensive to maintain automated delivery than to deploy it manually. Now, if I use the Azure DevOps service, I can do it in ten minutes by using a web browser. Indeed, times have changed!

Why do I need more than DevOps can do?

This reason is easy to understand, when you go through twists and turns to introduce DevOps to your company, you may think that you are in good shape. But the truth is that in the IT world, things are changing faster than people, and now the market demand is becoming more and more hot, and the constant demand has brought constant change and adjustment, and you can't simply respond to the sentence: "I'm tired of dealing with change and need a break."

The advent of the cloud era has made things more complicated. It allows us to implement complex solutions and solve many challenges, but it also requires more skills.

All components in the cloud are scalable, but it involves some DevOps configuration, which always requires some manual intervention and still requires someone to be involved behind most processes. It can be understood that this is still the old mode of work.

The purpose of NoOps is to define a process that does not require a combination of development and operation and maintenance to make the process go smoothly. NoOps has a goal: to design that everything can be deployed without the involvement of anyone.

The general approach of NoOps is as follows: the developer has completed the deployment by submitting the code to the code base. It looks very similar to continuous delivery, but it covers a larger scope, including not only applications but also infrastructure deployment.

How does NoOps do it?

Compared with DevOps, NoOps needs technical support. There are many options for this support, but basically, we can summarize it as follows:

NoOps is a PaaS solution, such as Heroku or provided by cloud service providers such as Azure and AWS.

Serverless computing services purchased from service providers such as AWS,Azure.

A replicable infrastructure has been created (this is almost necessary for the first step).

Similar solutions mentioned above are well suited to solve the work of the infrastructure part, while traditional deployment tools can drive process processing and deliver applications.

All is not gold that glitters

I admit that the idea of abolishing infrastructure management is seductive and feels like pulling out a bad tooth. Because in general, infrastructure takes up a lot of management costs and brings friction between development and operation and maintenance.

But the other point is that the problem is not the infrastructure, but the process. If the process is well designed, there will be no friction, no delay, and everything can be done in an orderly way.

Are you worried about administrative costs? In fact, you should consider the overall cost, not just the administrative cost. It may be more expensive to manage your cloud infrastructure, but in the end the cost will be the same. But it's not absolute. Confused? The secret is that some applications can be deployed on PaaS and some can't. That's all. If your application is simple, PaaS is a good solution, and DevOps people will be happy to reduce the workload. But if you are going to launch the next Netflix, you will need more control, and the PaaS service will not be so appropriate. This is the root of it.

In the end, there is no DevOps or NoOps. The most fundamental driver is to create an intelligent infrastructure and automate everything with as little maintenance work as possible. Using services such as Google Cloud or other public cloud services, you can find the best solution for your application scenario.

So, from this perspective, what is NoOps? The essence is another buzzword in the cloud trend.

The above content is how to analyze the current situation of DevOps and NoOps. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.