博客
关于我
强烈建议你试试无所不能的chatGPT,快点击我
noops fabric_每个开发公司需要了解的有关NoOps开发的知识
阅读量:2507 次
发布时间:2019-05-11

本文共 8428 字,大约阅读时间需要 28 分钟。

noops fabric

It seems like everything is getting automated these days.

这些天似乎一切都在自动化。

And I mean everything.

我是认真的

Who would’ve thought that we’d be automating development teams, though?

谁会想到我们会自动化开发团队呢?

69% of development companies agree that , so it makes sense we’re heading in this direction.

69%的开发公司同意 ,因此我们朝着这个方向前进是有道理的。

This rise of automation has formed a new development model known as NoOps, which stands for no operations.

自动化的兴起形成了一种称为NoOps的新开发模型,该模型代表无操作

The name means that this approach involves no operations input, cutting out the “operate” step of the continuous development model.

名称意味着这种方法不涉及任何操作输入,从而消除了持续开发模型的“操作”步骤。

Continuous development model

That’s right. The developers are capable of launching, testing, and fixing apps on the fly without any interruptions or downtime.

那就对了。 开发人员能够即时启动,测试和修复应用程序,而不会造成任何中断或停机。

Follow along as I further cover what NoOps is, the benefits of using it, and how to implement it.

接下来,我将进一步介绍NoOps是什么,使用NoOps的好处以及如何实现它。

什么是NoOps? (What is NoOps?)

NoOps is a new development approach that involves relieving developers of needing to constantly work with operations members, speeding up deployment time, testing, and workflow.

NoOps是一种新的开发方法,该方法涉及减轻开发人员需要与操作成员不断合作,加快部署时间,测试和工作流程的需要。

It stems from the previously popular model of developers and operations teams working closely called DevOps.

它源自紧密合作的称为DevOps的开发人员和运营团队的先前流行模型。

Instead of working together, service providers give development teams the proper cloud infrastructure, patching, backups, and resources to work on their own.

服务提供商无需一起工作,而是为开发团队提供适当的云基础架构,补丁程序,备份和资源,以自行工作。

Traditional DevOps vs NoOps

That means programmers no longer require feedback and approval during development, and can operate completely independently.

这意味着程序员在开发期间不再需要反馈和批准,并且可以完全独立地运行。

This also allows the operations department of a company to focus on what they do best: project management, talent acquisition, and so on.

这也使公司的运营部门可以专注于他们最擅长的领域:项目管理,人才招募等等。

However, NoOps is typically most beneficial for startups that begin with this continuous development model. It is much more difficult to switch to NoOps when you have existing environments, pipelines, .

但是,NoOps通常对于以这种持续开发模型开始的初创公司最有利。 当您拥有现有的环境,管道时,切换到NoOps要困难得多。

As an example, NoOps does not work well for enterprises that are still stuck with a monolithic legacy application. This would require a re-write of most of their codebase to make it fit with the NoOps ideology.

举例来说,NoOps对于仍然坚持使用单一遗留应用程序的企业而言效果不佳。 这将需要重写其大多数代码库,以使其符合NoOps意识形态。

Additionally, if a company adopts NoOps later in the business cycle, they may have to shrink the size of their operations team.

此外,如果公司在商业周期的晚些时候采用NoOps,则他们可能不得不缩减其运营团队的规模。

If a startup launches with a NoOps model from the beginning, they have the potential of staying lean for longer. The saved resources can be put towards other aspects of business growth, like marketing.

如果一家初创公司从一开始就采用NoOps模式启动,那么它们就有可能保持精益状态更长的时间。 可以将节省的资源用于业务增长的其他方面,例如营销。

NoOps有什么好处? (What Are the Benefits of NoOps?)

There are many benefits to be gained by adopting a NoOps model. The first of which is that it maximizes development time.

采用NoOps模型可以获得许多好处。 首先是最大化开发时间

By not having to go back and forth with operations members, developers can roll out changes, features, and entire apps faster than ever before.

通过不必与操作成员来回交流,开发人员可以比以往更快地推出更改,功能和整个应用程序。

This process is further sped up by providing many preconfigured templates for running a specific type of application, like a Node.js microservice. This means no time is wasted on configuring and securing your application deployment as everything is pre-configured by the template. This kind of easy-to-use experience is also referred to as Developer Experience (DX).

通过提供许多用于运行特定类型的应用程序(例如Node.js微服务)的预配置模板,可以进一步加快此过程。 这意味着无需花费任何时间在配置和保护应用程序部署上,因为所有内容均由模板预先配置。 这种易于使用的体验也称为开发者体验(DX)。

This also implies that hitting milestones will be easier and quicker. With this sped-up development time, companies create opportunity to generate revenue sooner, since the software can be completed ahead of schedule.

这也意味着达到里程碑将更加容易和快捷 。 有了这样的加速开发时间,由于可以提前完成软件的开发,公司就可以创造机会更快地创收。

Furthermore, NoOps allows developers and operations teams to do what they do best: develop and operate.

此外,NoOps允许开发人员和运营团队做他们最擅长的事情: 开发运营

Both departments of a business can double down and become more productive thanks to the extra focus and time gained by this continuous development model.

通过这种持续发展的模式,企业的两个部门都可以加倍投入提高生产力

如何实现NoOps (How to Implement NoOps)

The simplest way to integrate this methodology is by using a NoOps funnel tool, , that offers managed cloud storage, pipelines, zero-downtime deployments, and automated operations. It is the most convenient and simple solution to get started with NoOps.

集成此方法的最简单方法是使用NoOps漏斗工具( ,该工具提供托管的云存储,管道,零停机时间部署和自动化操作。 这是上手NoOps的最方便,最简单的解决方案。

Debugging code and some operational tasks will have to remain in-house, but a large chunk of infrastructure will be completely handled on behalf of developers.

调试代码和一些操作任务将必须保留在内部,但是大部分基础架构将完全由开发人员来处理。

Since these services typically allow many users to have individual accounts at once, it enhances collaboration as well.

由于这些服务通常允许许多用户一次拥有单个帐户,因此它也增强了协作。

When you successfully connect with a service provider, it’s recommended to also consider revamping procedures for:

与服务提供商成功建立连接后,建议还考虑以下方面的改进过程:

  • What the operations team needs to focus on with many tasks now outsourced.

    运营团队现在需要将许多任务集中在什么工作上。
  • Project deadlines and expectations since deployments and changes can be completed faster.

    项目截止日期和期望,因为可以更快地完成部署和更改。

NoOps的挑战 (Challenges of NoOps)

The ideas backing the NoOps movement are sound but NoOps itself is not without its challenges. The idea of NoOps is based on the assumption that automation can handle every use case, and therefore eliminates the need for any human intervention.

支持NoOps运动的想法是正确的,但是NoOps本身并非没有挑战。 NoOps的想法基于这样的假设:自动化可以处理每个用例,因此消除了任何人工干预的需要。

What many organizations forget is that containerized services can still fail and need maintenance. From my personal experience, I can tell you that my last microservices-based company had an emergency response team in place during the nights to bring up any container that had crashed (which happened once every 2-3 weeks).

许多组织忘记的是,容器化服务仍然可能失败并需要维护。 从我的亲身经历,我可以告诉你,我的上一家基于微服务的公司在夜间设有一个应急小组,以提起所有已坠毁的集装箱(每2-3周发生一次)。

Although you have to consider the element of failure which probably needs human intervention, NoOps is still able to remove the most need for human intervention — DevOps.

尽管您必须考虑可能需要人工干预的故障要素,但NoOps仍然能够消除最需要人工干预的因素-DevOps。

NoOps的未来 (Future of NoOps)

NoOps will play an important role for many startups and product-as-a-service (PaaS) companies. It helps them go to market quicker, and catch revenue faster.

对于许多初创公司和产品即服务(PaaS)公司而言,NoOps将扮演重要角色。 它可以帮助他们更快地进入市场,并更快地获取收入。

It also fits well into the agile methodology, in which you have fast releases. NoOps can provide this agility in quickly deploying your product in order to test it.

它也非常适合您快速发布的敏捷方法。 NoOps可以在快速部署产品以进行测试时提供这种敏捷性。

However, the future may take us even further into Intelligent-Ops, which includes the use of Artificial Intelligence (AI) to manage software deployments. For example, AI could learn patterns that detect common errors or inspect logs to detect failures and learn from this. The first step can be that the AI analyzes logs and detects patterns to report back to the team what possibly went wrong.

但是,未来可能会使我们进一步涉足Intelligent-Ops,其中包括使用人工智能(AI)来管理软件部署。 例如,人工智能可以学习检测常见错误的模式,或者检查日志以检测故障并从中学习。 第一步可以是AI分析日志并检测模式以向团队报告可能出了什么问题。

最后的想法 (Final Thoughts)

of any form in general. If you’re one of them, stop dreading deployment and start looking forward to it by taking advantage of NoOps.

通常, 任何形式 。 如果你是其中之一,停止害怕部署并开始采取NoOps的优势,期待它。

NoOps is an excellent choice for any software companies interested in scaling, optimizing development, and automating everyday procedures.

对于任何对伸缩,优化开发和日常流程自动化感兴趣的软件公司,NoOps都是绝佳选择。

This approach was created out of the DevOps model with the goal of further automation and faster rollouts.

此方法是在DevOps模型的基础上创建的,目的是进一步实现自动化和更快地推出。

It’s most suitable for startup companies that can form their business around it from the beginning, as it’s more difficult to reshape an entire business once a model like DevOps is already in place.

它最适合可以从一开始就围绕它开展业务的初创公司,因为一旦像DevOps这样的模型就位了,就很难重塑整个业务。

Contact a NoOps service provider if you believe this is the direction you’d like to take your development team, and start reaping the benefits today.

如果您认为这是您希望带动开发团队的方向,请与NoOps服务提供商联系,并从今天开始收获收益。

翻译自:

noops fabric

转载地址:http://hxegb.baihongyu.com/

你可能感兴趣的文章
Neutron在给虚拟机分配网络时,底层是如何实现的?
查看>>
netfilter/iptables全攻略
查看>>
Overlay之VXLAN架构
查看>>
Eclipse : An error occurred while filtering resources(Maven错误提示)
查看>>
在eclipse上用tomcat部署项目404解决方案
查看>>
web.xml 配置中classpath: 与classpath*:的区别
查看>>
suse如何修改ssh端口为2222?
查看>>
详细理解“>/dev/null 2>&1”
查看>>
suse如何创建定时任务?
查看>>
suse搭建ftp服务器方法
查看>>
centos虚拟机设置共享文件夹并通过我的电脑访问[增加smbd端口修改]
查看>>
文件拷贝(IFileOperation::CopyItem)
查看>>
MapReduce的 Speculative Execution机制
查看>>
大数据学习之路------借助HDP SANDBOX开始学习
查看>>
Hadoop基础学习:基于Hortonworks HDP
查看>>
为什么linux安装程序 都要放到/usr/local目录下
查看>>
Hive安装前扫盲之Derby和Metastore
查看>>
永久修改PATH环境变量的几种办法
查看>>
大数据学习之HDP SANDBOX开始学习
查看>>
Hive Beeline使用
查看>>