Optimizing Cloud Migration: Performance Lessons for the Enterprise

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/671893

Contents of this Issue


Page 25 of 35

formance issues but also to outages seen at specific data centers. Alternatively, rather than switching location—as this is not always possible due to practical issues (e.g., data)—the system could also be configured to move into a lower-bandwidth/minimized-service interaction state to minimize the impact. Understand the Cost of Performance and Monitoring as a Core Part of Capacity Planning The cloud allows you to provide all the systems needed to deliver a scalable system, but those systems do not come for free. Anyone who has used cloud-based services will tell you that it is very easy to run up much higher bills than expected. However, this can be miti‐ gated by intelligent system design. Key Concept—Capacity Planning Has Changed Capacity planning used to be about understanding the capacity of your systems and ensuring that there was always sufficient head‐ room to allow for anticipated short/medium-term growth. In this model, a server hitting capacity was a negative position that indica‐ ted that capacity planning was failing and that the system may soon fail. In the cloud world, this is reversed, and the objective should be to have a system that is always operating close to capacity. Resources are so easy to scale that scaling them ahead of time is generally a waste of money. Adding complexity will add cost—not only in terms of cloud costs, but also in terms of development and maintenance overhead. It is essential that you consider the following: Level of usage Scale systems only to the level of usage that you anticipate. There is no need to future-proof systems. You build systems that can scale, not that are at a capacity to meet any anticipated future demand. Good system architecture is essential here and, like other things, cloud-based system architecture is different from on-premise system architecture. As a general rule, the aim should be to use cloud-based services where possible, as they 20 | Phase 3: Enhancing Your Cloud Solution

Articles in this issue

view archives of eBooks - Optimizing Cloud Migration: Performance Lessons for the Enterprise