<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Container on Mi&amp;Bee Blog</title><link>/en/tags/container/</link><description>Recent content in Container on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Mon, 17 Apr 2017 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/container/rss.xml" rel="self" type="application/rss+xml"/><item><title>Practices and Pitfalls of Dockerizing Enterprise Applications — From Traditional Virtualization to Containerization</title><link>/en/archives/05-docker-enterprise-application/</link><pubDate>Mon, 17 Apr 2017 00:00:00 +0000</pubDate><guid>/en/archives/05-docker-enterprise-application/</guid><description>&lt;h2 id="introduction-why-containerize-enterprise-applications"&gt;Introduction (Why Containerize Enterprise Applications)&lt;/h2&gt;
&lt;p&gt;In the era of cloud computing, the way enterprise applications are deployed and managed is undergoing a profound transformation. While traditional virtualization technology solved the resource isolation problem, it still has many pain points in terms of operational efficiency, resource utilization, and deployment speed. The rise of Docker container technology has provided a brand-new solution for the modernization of enterprise applications.&lt;/p&gt;
&lt;p&gt;This article shares our practical experience in the containerization migration of an enterprise email system, including technology selection, infrastructure construction, the full process of migrating from OpenVZ virtualization to Docker, and various issues encountered in production along with their solutions. Through these practical cases, we hope to provide valuable reference for teams that are currently or planning to undertake containerization migration.&lt;/p&gt;</description></item></channel></rss>