Docker文章

<p>[TOC]</p> <h1>容器论文笔记</h1> <h2>1.Docker</h2> <h3>1.1开山之作或者白皮书</h3> <p><strong>基本信息：</strong> </p> <ul> <li>2014|Docker: lightweight linux containers for consistent development and deployment</li> <li>Merkel D. Docker: lightweight linux containers for consistent development and deployment[J]. Linux Journal, 2014, 2014(239): 2.</li> </ul> <p><strong>摘要：</strong> </p> <pre><code>Take on “dependency hell” with Docker containers, the lightweight and nimble cousin of VMs. Learn how Docker makes applications portable and isolated by packaging them in containers based on LXC technology. Imagine being able to package an application along with all of its dependencies easily and then run it smoothly in disparate development, test and production environments. That is the goal of the open-source Docker project. Although it is still not officially production-ready, the latest release (0.7.x at the time of this writing) brought Docker another step closer to realizing this ambitious goal. Docker tries to solve the problem of “dependency hell”. Modern applications often are assembled from existing components and rely on other services and applications. For example, your Python application might use PostgreSQL as a data store, Redis for caching and Apache as a Web server. Each of these components comes with its own set of dependencies that may conflict with those of other components. By packaging each component and its dependencies, Docker solves the following problems: Conflicting dependencies: need to run one Web site on PHP 4.3 and another on PHP 5.5? No problem if you run each version of PHP in a separate Docker container. Missing dependencies: installing applications in a new environment is a snap with Docker, because all dependencies are packaged along with the application in a container. Platform differences: moving from one distro to another is no longer a problem. If both systems run Docker, the same container will execute without issues.</code></pre> <p><strong>结论：</strong></p> <pre><code>One reasonable argument we've heard is that you shouldn't start with a microservices architecture. Instead begin with a monolith, keep it modular, and split it into microservices once the monolith becomes a problem. (Although this advice isn't ideal, since a good in-process interface is usually not a good service interface.)</code></pre> <p><strong>可参考的文献：</strong> </p> <p><strong>笔记：</strong> </p> <p>是Docker的白皮书和介绍，讲了docker的一些基本使用，docker是为了解决依赖地狱的问题，解决了一个平台安装不同版本的应用；缺少依赖；平台差异的问题，是一项轻量化的容器技术。</p>