Learn all you need to know about email best practices, deliverability, and tools with email whitepapers and ebooks.

Issue link: https://hub.dyn.com/i/1119883

Contents of this Issue


Page 23 of 57

organizations to easily redeploy an application from one cloud pro‐ vider to another. Containers have additional security benefits, as well. By stripping out unnecessary tools from the container and leaving just the appli‐ cation and its dependencies, you create a smaller footprint for bad actors to attack. Even if an attacker does manage to exploit an unpatched vulnerability on a container, they will have a difficult time. That's because the native tools an attacker normally uses to move around the system will not be there. After the attacker is detected, it is simply a matter of destroying the container and replacing it with a newly patched version. Even though containers bring added benefits, they also come wit challenges, including management, security, and complexity con‐ cerns, which we discuss in this chapter. Powerful Orchestration Interfaces Are Crucial The cloud marketplace is constantly changing, with providers adding new features and enhancing their services regularly. The market is dynamic, and this means that your architecture must be able to quickly adapt to new capabilities. The web applications your organization deployed five years ago look nothing like the web applications you deploy today, and two years from now they will be completely remade again. Infrastructure migration has always been painful, as evidenced by the large number of legacy systems that still exist today. But migra‐ tion is the new norm. Containers help organizations adapt to rapidly changing infrastructure requirements, but they are only the first step. In addition to using containers, organizations need to use management and orchestration tools to effectively manage contain‐ ers across all cloud providers. Using these tools, your organization will be able to quickly take advantage of new features and services. One of the benefits of container deployment, discussed in the previ‐ ous chapter, is that it is not dependent on the underlying hardware. Because the container has the application and all required libraries built into the platform, you can deploy it in almost any environment and function in the same way across all deployed platforms. How‐ ever, in a multicloud environment, there will be dependencies between containers. Therefore, your management system needs to 18 | Chapter 2: Multicloud Infrastructure Orchestration and Management

Articles in this issue

view archives of eBooks - OreillyMultiCloudFinalEBOOK