Foundation for design – the thought process

The cloud was supposed to be simple. It was supposed to be fast. It was supposed to solve many, if not all, of the problems. As people started digging into cloud designs, they began to discover that things were not always as simple, things were not always less expensive, and things were not always performing as expected. In many cases, they experienced significant challenges with social adoption. The design did not match expectations for various reasons. Throughout this book, we talk about how perceived requirements are merely starting objectives that accelerate towards requirements with the gathering of additional insight and data. Ultimately, successful designs must simultaneously harmonize economics, strategy, technology, and risk. This balance leaves risk and economics offset at equilibrium.

Cloud computing is one of the rare things in our industry where nearly everyone is impacted or affected by the change. Adoption of the change is the big...