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

Another problem could be that you are stuck with an old system that is part of your stack that requires something old that you can‐ not get from a cloud provider, like an older, unsupported relational database. This can cause expenses related to the time it takes devel‐ opers to plan that upgrade and data migration, and unexpected license costs. None of this would be code cleanup, but it is necessary to factor in the time and cost when making the move. Development agility is about more than just clean code that can run across multiple cloud environments. It also means adapting to the reality of more frequent updates to the code base. It means updating your code multiple times a month or week instead of a couple of times a year. The development team also needs to be able to rapidly write and test new security patches and deploy them quickly without taking the application offline. Truthfully, this is already a develop‐ ment reality, and being in the cloud to do it is not a requirement for this type of development process. Agile development is how a lot of businesses operate, irrespective of where the application resides. Given that the Agile development process is the new norm, what changes for most organizations when migrating to a multicloud infrastructure is neither the code nor the development cycle. It is the DevOps process and the Continuous Integration (CI) tools that run DevOps. You now have to package, deploy, and run automated tests on multiple cloud providers. And maybe one app is on just one cloud provider, but another application that needs the redundancy is on multiple cloud providers. You are going to want your develop‐ ment cycle to automatically provision and deploy to the appropriate place. And your local development environment likely isn't a cloud provider (although it could be). Evaluation If you have read this far, you might be asking, how do I determine whether my project and organization are ready for multicloud? It is not hyperbole, or even controversial, at this point to state the future of most IT projects will be in the cloud. The benefits of cost savings, resiliency, and new feature enhancements that organizations realize by moving to the cloud are too great to ignore. Moving to the cloud allows an organization to focus on its core competencies instead of managing a datacenter. 12 | Chapter 1: Why Multicloud Architecture?

Articles in this issue

view archives of eBooks - OreillyMultiCloudFinalEBOOK