|
| 1 | +--- |
| 2 | +title: “基于容器的应用程序设计原理” |
| 3 | +date: 2018-03-15 |
| 4 | +slug: principles-of-container-app-design |
| 5 | +url: /zh/blog/2018/03/Principles-Of-Container-App-Design |
| 6 | +--- |
| 7 | +<!-- |
| 8 | +--- |
| 9 | +title: "Principles of Container-based Application Design" |
| 10 | +date: 2018-03-15 |
| 11 | +slug: principles-of-container-app-design |
| 12 | +url: /blog/2018/03/Principles-Of-Container-App-Design |
| 13 | +--- |
| 14 | +--> |
| 15 | + |
| 16 | +<!-- |
| 17 | +It's possible nowadays to put almost any application in a container and run it. Creating cloud-native applications, however—containerized applications that are automated and orchestrated effectively by a cloud-native platform such as Kubernetes—requires additional effort. Cloud-native applications anticipate failure; they run and scale reliably even when their infrastructure experiences outages. To offer such capabilities, cloud-native platforms like Kubernetes impose a set of contracts and constraints on applications. These contracts ensure that applications they run conform to certain constraints and allow the platform to automate application management. |
| 18 | +--> |
| 19 | +如今，可以将几乎所有应用程序放入容器中并运行它。 |
| 20 | +但是，创建云原生应用程序（由 Kubernetes 等云原生平台自动有效地编排的容器化应用程序）需要付出额外的努力。 |
| 21 | +云原生应用程序会预期失败； |
| 22 | +它们可以可靠的运行和扩展，即使基础架构出现故障。 |
| 23 | +为了提供这样的功能，像 Kubernetes 这样的云原生平台对应用程序施加了一系列约定和约束。 |
| 24 | +这些合同确保运行的应用程序符合某些约束条件，并允许平台自动执行应用程序管理。 |
| 25 | + |
| 26 | + |
| 27 | +<!-- |
| 28 | +I've outlined [seven principles][1]for containerized applications to follow in order to be fully cloud-native. |
| 29 | +--> |
| 30 | +我总结了容器化应用要成为彻底的云原生应用所要遵从的[七个原则][1]。 |
| 31 | + |
| 32 | +| ----- | |
| 33 | +| ![][2] | |
| 34 | +<!-- |
| 35 | +| Container Design Principles | |
| 36 | +--> |
| 37 | +| 容器设计原则 | |
| 38 | + |
| 39 | + |
| 40 | +<!-- |
| 41 | +These seven principles cover both build time and runtime concerns. |
| 42 | +--> |
| 43 | +这七个原则涵盖了构建时间和运行时问题。 |
| 44 | + |
| 45 | +<!-- |
| 46 | +#### Build time |
| 47 | +--> |
| 48 | +#### 建立时间 |
| 49 | + |
| 50 | +<!-- |
| 51 | +* **Single Concern:** Each container addresses a single concern and does it well. |
| 52 | +--> |
| 53 | +* **单独关注点：** 每个容器都解决了一个单独的关注点，并做到了。 |
| 54 | +<!-- |
| 55 | +* **Self-Containment:** A container relies only on the presence of the Linux kernel. Additional libraries are added when the container is built. |
| 56 | +--> |
| 57 | +* **自包含：** 容器仅依赖于Linux内核的存在。 构建容器时会添加其他库。 |
| 58 | +<!-- |
| 59 | +* **Image Immutability:** Containerized applications are meant to be immutable, and once built are not expected to change between different environments. |
| 60 | +--> |
| 61 | +* **镜像不可变性：** 容器化应用程序是不可变的，并且一旦构建，就不会在不同环境之间发生变化。 |
| 62 | + |
| 63 | +<!-- |
| 64 | +#### Runtime |
| 65 | +--> |
| 66 | +#### 运行时 |
| 67 | + |
| 68 | +<!-- |
| 69 | +* **High Observability:** Every container must implement all necessary APIs to help the platform observe and manage the application in the best way possible. |
| 70 | +--> |
| 71 | +* **高度可观察性：** 每个容器都必须实现所有必要的API，以帮助平台以最佳方式观察和管理应用程序。 |
| 72 | +<!-- |
| 73 | +* **Lifecycle Conformance:** A container must have a way to read events coming from the platform and conform by reacting to those events. |
| 74 | +--> |
| 75 | +* **生命周期一致性：** 容器必须具有读取来自平台的事件并通过对这些事件做出反应来进行一致性的方式。 |
| 76 | +<!-- |
| 77 | +* **Process Disposability:** Containerized applications must be as ephemeral as possible and ready to be replaced by another container instance at any point in time. |
| 78 | +--> |
| 79 | +* **进程可丢弃：** 容器化的应用程序必须尽可能短暂，并随时可以被另一个容器实例替换。 |
| 80 | +<!-- |
| 81 | +* **Runtime Confinement:** Every container must declare its resource requirements and restrict resource use to the requirements indicated. |
| 82 | +The build time principles ensure that containers have the right granularity, consistency, and structure in place. The runtime principles dictate what functionalities must be implemented in order for containerized applications to possess cloud-native function. Adhering to these principles helps ensure that your applications are suitable for automation in Kubernetes. |
| 83 | +--> |
| 84 | +* **运行时可约束** 每个容器必须声明其资源需求，并根据所标明的需求限制其资源使用。 |
| 85 | +构建时间原则可确保容器具有正确的颗粒度，一致性和适当的结构。 |
| 86 | +运行时原则规定了必须执行哪些功能才能使容器化的应用程序具有云原生功能。 |
| 87 | +遵循这些原则有助于确保您的应用程序适合Kubernetes中的自动化。 |
| 88 | + |
| 89 | +<!-- |
| 90 | +The white paper is freely available for download: |
| 91 | +--> |
| 92 | +白皮书可以免费下载： |
| 93 | + |
| 94 | +<!-- |
| 95 | +To read more about designing cloud-native applications for Kubernetes, check out my [Kubernetes Patterns][3] book. |
| 96 | +--> |
| 97 | +要了解有关为Kubernetes设计云原生应用程序的更多信息，请翻阅我的[Kubernetes 模式][3]这本书。 |
| 98 | + |
| 99 | +<!-- |
| 100 | +— [Bilgin Ibryam][4], Principal Architect, Red Hat |
| 101 | +--> |
| 102 | +— [Bilgin Ibryam][4]，首席架构师，Red Hat |
| 103 | + |
| 104 | +<!-- |
| 105 | +Twitter:
|
| 106 | +Blog: [http://www.ofbizian.com][5] |
| 107 | +Linkedin: |
| 108 | +--> |
| 109 | +推特：
|
| 110 | +博客： [http://www.ofbizian.com][5] |
| 111 | +领英： |
| 112 | + |
| 113 | +<!-- |
| 114 | +Bilgin Ibryam (@bibryam) is a principal architect at Red Hat, open source committer at ASF, blogger, author, and speaker. He is the author of Camel Design Patterns and Kubernetes Patterns books. In his day-to-day job, Bilgin enjoys mentoring, training and leading teams to be successful with distributed systems, microservices, containers, and cloud-native applications in general. |
| 115 | +--> |
| 116 | +Bilgin Ibryam（@bibryam）是 Red Hat 的首席架构师，ASF 的开源提交者，博客，作者和发言人。 |
| 117 | +他是骆驼设计模式和 Kubernetes 模式书籍的作者。 |
| 118 | +在日常工作中，Bilgin 乐于指导，培训和领导团队，以使他们在分布式系统，微服务，容器和云原生应用程序方面取得成功。 |
| 119 | + |
| 120 | + |
| 121 | +[1]: https://www.redhat.com/en/resources/cloud-native-container-design-whitepaper |
| 122 | +[2]: https://lh5.googleusercontent.com/1XqojkVC0CET1yKCJqZ3-0VWxJ3W8Q74zPLlqnn6eHSJsjHOiBTB7EGUX5o_BOKumgfkxVdgBeLyoyMfMIXwVm9p2QXkq_RRy2mDJG1qEExJDculYL5PciYcWfPAKxF2-DGIdiLw |
| 123 | +[3]: http://leanpub.com/k8spatterns/ |
| 124 | +[4]: http://twitter.com/bibryam |
| 125 | +[5]: http://www.ofbizian.com/ |
| 126 | + |
0 commit comments