将应用程序作为服务运行或将其部署在容器上有什么区别? [英] What is the difference between running an application as a service or deploying it on a container?

问题描述

我需要安装以下应用程序以实现我们的持续交付策略:

I need to install the following applications for our continuous delivery strategy:

Jenkins 和 Apache Archiva

但是他们提供:

要作为Windows服务安装或 要部署在容器中(即Tomcat)

to be install as a windows service or to be deploy in a container (i.e. Tomcat)

我想知道将这些应用程序作为服务安装是否会为我们提供更好的性能，可靠性，安全性或其他方式，或者根本不提供任何功能

I was wondering if installing those applications as a service will give us better performance, reliability, security or whatsoever or the other way around or nothing at all

谢谢！

推荐答案

来自在Windows上安装Jenkins的官方文档:

如果您在Windows上运行，最好将Jenkins作为服务运行，这样它就可以自动启动而无需用户登录.最简单的方法是运行Windows安装程序(从Jenkins主页链接).这也具有易于自动化的优点.

If you're running on Windows it is good to run Jenkins as a service so it starts up automatically without requiring a user to log in. The easiest way is to run the Windows installer, linked from Jenkins' homepage. This also has the advantage of being easier to automate.

如果将Jenkins部署到Tomcat，则每次启动计算机时，可能都必须手动启动Tomcat.另外，如果要停止或暂停在容器中运行的Jenkins，则可能必须手动关闭容器.如果操作不当，可能会导致问题.

If you deploy Jenkins to Tomcat, then every time you start up your computer you might have to manually start Tomcat. In addition, if you want to stop or pause Jenkins running in a container you may have to manually shut down the container. This can lead to problems if not done properly.

另一方面，如果Jenkins作为服务运行，则Windows将为您处理大多数此类事情.除非您需要对Jenkins进行非常精细的谷物控制，否则我将其保留为服务.您可能可能将其部署到Tomcat中的一个示例是，如果您编写了一个自定义插件并想要对其进行测试.

On other hand, if Jenkins be running as a service, then Windows will handle most of these things for you. Unless you need to have very fine grain control over Jenkins I would leave it as a service. One example where you might want to deploy it in Tomcat would be if you wrote a custom plugin and wanted to test it.

这篇关于将应用程序作为服务运行或将其部署在容器上有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！