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 16 of 57

options take time, and it's still possible to miss out on a new service that might be a good fit for your organization. Another option is to rely on updates from your own team. Cloud providers often offer certification programs for your engineering team. This gives your staff added insight into the services available through the cloud provider and helps them stay abreast of the latest offerings. Many organizations turn to Cloud Service Brokers (CSBs) such as Bluewolf, Jamcracker, or Cloud Foundry to help identify cloud pro‐ viders that deliver the right services at the right price. CSBs have experience with a wide range of cloud providers and have worked with other customers, often with needs similar to yours. This exten‐ sive experience empowers them to help organizations find cloud services that you might not have previously considered. CSBs can make the process significantly less painful, and they can help organi‐ zations get up and running in a multicloud environment quickly. Development Agility The last trade-off in considering the move to a multicloud architec‐ ture is development agility. A multicloud architecture requires the ability to create code that can run on multiple cloud providers' plat‐ forms, ideally with no changes to the code from one provider to the next. Development standards within your organization help take care of this, so even if the code base is a mess, each provider can run that mess without different code bases. Moving an application to a multicloud architecture might require your team to revisit application code. The code will need to be cleaned up and tested across your cloud providers to ensure that pushing out updates won't create problems that will make one of the cloud instances unavailable. But it is more than just editing your code; there are other tasks that you need to complete, such as mak‐ ing sure your provider has the libraries, language compilers/ runtime, and server versions available in their repositories for what‐ ever containers you are running. A good example of that is the Java Development Kit (JDK)—you might be at the point at which you can install only an open-JDK version. Another example is that you could have a version of Apache Tomcat that runs a significantly newer servlet specification. Trade-Offs | 11

Articles in this issue

view archives of eBooks - OreillyMultiCloudFinalEBOOK