eBooks

OreillyMultiCloudFinalEBOOK

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

Navigation

Page 19 of 57

ing cycles are, and how to get support if something goes wrong. You also need to share that information with your team so that everyone knows the limitations of each provider and is empowered to open support tickets. Designing for a Multicloud Infrastructure Moving to a multicloud architecture often means redesigning your application to accommodate a more complex networking and infra‐ structure environment. As with other documentation, this requires careful planning and assistance from the cloud providers themselves when possible. Many cloud providers have architects on staff who can help answer any questions from your team. They can also offer tips to make the migration process smoother. Remember that CSBs often have architects on staff who can advise organizations on dif‐ ferent aspects of various cloud platforms. Cloud architects are a valuable resource, and for many organiza‐ tions, it pays to have one on staff. The architect could be an outside hire or a person who is already on staff who has been trained on the cloud platforms that the organizations intend to use. The advantage to having a cloud architect on staff is that you will have someone who knows and understands your application in a way that an out‐ side consultant will not. On-staff cloud architects are empowered to give a more accurate assessment of what needs to be changed in order to maximize the success of the multicloud migration. Conclusion Migrating applications to a multicloud architecture will increase resiliency while saving your organization money in the long run. But multicloud migrations come with challenges and short-term costs. Before jumping into a multicloud infrastructure, it is impor‐ tant to take a step back and understand the maturity of your appli‐ cation and your team, and to make sure the organization is ready for the complexity of a multicloud deployment. After completing an internal assessment, the next step is to under‐ stand which providers will meet your needs and what their offerings are. Then, it's time to design the architecture, working with a cloud architect whenever possible. This is also the time to document the new design for your application and make any changes needed to support the new architecture. 14 | Chapter 1: Why Multicloud Architecture?

Articles in this issue

view archives of eBooks - OreillyMultiCloudFinalEBOOK