| IT trend nowadays in, DevOps it is a hot word. It originated several years ago SPA (single-page application) front-end application. I think the norm is to adapt IT technology, new technology began at the moment of the outbreak, immediately people will be keen adopted, then quickly spread Come. DevOps recent years, it is one such. But a few years, you will hear another buzzword: NoOps. |
IT trend nowadays in, DevOps it is a hot word. It originated several years ago SPA (single-page application) front-end application. I think the norm is to adapt IT technology, new technology began at the moment of the outbreak, immediately people will be keen adopted, then quickly spread Come. DevOps recent years, it is one such. But a few years, you will hear another buzzword: NoOps.
DevOps and NoOps differences
DevOps is a fusion of the development and operation and maintenance, is the development and operation and maintenance engineers work together to define the practical application from design to delivery lifecycle process.
NoOp means without operator. The idea is to remove all the management part of the platform, thereby reducing the friction between the developer and infrastructure.
Why do I need DevOps?
As technology and business needs more and more challenging, IT services are becoming increasingly complex. This makes the delivery is becoming increasingly important, so we have to put in effort to orchestrate the entire application delivery process.
Once you have a cloud platform, the demand for system administrators began to decline, but demand for DevOps technical and business skills are still very high. To implement DevOps and just the right to use it. This allows us to consider circumstances beyond the technical delivery.
Why not previously DevOps?
There are a number of answers, you might say before the business scenario is simpler or do not have enough technical culture. I very much agree with this view, but I think those are not the root cause. In my experience, the reason should be more technical. Automated delivery is actually very difficult to achieve.
Most systems a decade ago, by default, do not step in building or as git-flow as well-defined workflow. There was no cost-effective solutions for CI, it is difficult to automate delivery.
I remember 2009, I myself intend to deploy a .net portal. I spent a Saturday morning to try to use open source tools to create an automatic deployment system, but in the end I gave up. Because I know that to maintain the delivery of automation than manually deploy its cost is much higher. Up to now, if you use Azure DevOps service, I just use a web browser can be completed in ten minutes. It really was the passage of time ah!
Why do I need than DevOps can do to be more?
The reason is well understood, the twists and turns when you will DevOps introduced into your company, you might think it in good condition. But the fact that IT world, things change faster than people now demand more and more popular, and constantly demand brings constant change and adjustment, but you can not simply deal with the sentence: "I have been struggling to cope with change, we need to rest a bit."
The arrival of the era of cloud make things more complicated. It allows us to implement complex solutions and solve many challenges, but we need to have more skills.
All components are scalable cloud, but it will involve some of the DevOps configuration, both always require some manual intervention, behind most of the processes running, still need someone to participate. It can be understood as this is the old mode of operation.
NoOps The purpose is to define the need to develop a combined operation and maintenance, it is possible to smooth the flow of the process. NoOps have a goal: by design so that all things can be deployed without the need for anyone to participate.
NoOps roughly as follows: developers to submit code to the code base has been completed all of the deployment. Continuous delivery looks very similar, but it contains a wider range, there is not only the application, but also includes the deployment of infrastructure.
How NoOps do it?
Relative to DevOps, NoOps is the need for technical support. This supports a lot of options, but basically, we can be summarized as follows:
NoOps is a PaaS solution, or the like Azure, AWS and other cloud service providers Heroku provided.
Purchased from AWS, Azure and other service providers at the server-computing services.
Creating the infrastructure can be copied (which is almost essential first step of the operation).
Similar to the above scenario is suitable for solving part of the infrastructure work, and let the tool to push the deployment of traditional treatment processes, deliver applications.
That glitters is not gold
I admitted to cancel infrastructure management idea is very tempting, it feels like a bad tooth pulled out. Because under normal circumstances, it is taking up a lot of infrastructure management costs, but also brought friction between the development and operation and maintenance.
But the other view is that the problem is not infrastructure, but in the process. If the process is well designed, there will be friction, there will be no delays, everything can be an orderly proceeding.
You worry about the cost of management? In fact, you should consider the overall costs, not just administrative costs. Maybe you cloud the higher administrative costs of infrastructure, but the final cost will be the same. But this is not absolute. Confused yet? This is one of the secret is that some applications can be deployed on PaaS, others can not. Nothing more. If your application is simple, it is a good PaaS solution, DevOps staff will be happy to reduce the workload. But if you want to launch is the next Netflix, then you will need more control rights, PaaS services will not be so apt friends. This is the root cause.
Speaking of the end, in fact, it does not matter DevOps or NoOps. The fundamental driver is: maintenance work as little as possible, to create an intelligent infrastructure, and all automated. Such as the use of other Google cloud or public cloud service, you can find the best solution for your application scenario.
So, from this point of view, what is NoOps? Essence is another popular trend in the word cloud.