The Cloud Computing Optimization Argument Simplified

From “An Insider’s Guide to Cloud Computing”

Optimization of this CNCF architecture, or other architectural approaches, will provide the best perfor- mance and functionality with the smallest price tag. Thus, we need proof that this architecture is the best approach with the understanding that it’s the closest we can get to being fully optimized.

There is less historical evidence around optimization related to cloud native architecture. However, we know enough about optimization itself that cloud native costs in time and or money should factor into the decision-making process to determine whether a cloud-native architecture and cloud native applications are truly the best choice for the enterprise. Business value is always the top objective.

Figure 5-8 shows our optimization curve again, this time with the added dimension of cost in the curve moving up and to the right. Note that we typically have a sweet spot of investment being made. Too little investment shows less optimization, and thus less value is returned to the business. On the optimization side of the curve, we can see that too much investment reduces the value returned to the business because we spent (and often continue to spend) too much on the technology and that dilutes the value. Thus, you want to target a point in the middle where the investment made at a specific level optimizes its business value.

FIGURE 5-8 When considering the value of any architecture, including a cloud-native architecture, you need to look at optimization as you increase the investment. You’ll find a point along the curve that’s close to being fully optimized. That’s where you want to be.

Although this value curve relates specifically to cloud-native architecture and application development, it can be applied to any number of technology solution patterns. It’s not about finding where technology is fully optimized when compared to the investment, but how does the curve compare against other development and architectural options, even proprietary cloud provider development that leverages proprietary tools and deployment platforms? Also consider architectures that are more in the center, with a mix of proprietary and open technologies that you can mix and match as needed. Most cloud-based solutions fall in the center. They allow you to mix and match technologies to find the right solution, but you must do so on a particular vendor’s platform.

We can’t really talk about optimization without talking about the cost of the overall investment (covered next). But the architectural choices really come down to your application requirements, as related to your business requirements, and how they should fit together to form a whole. There are a lot of technology and architectural choices out there, cloud native and many others. Don’t fall into the trap of just moving along with the crowd, no matter how compelling the arguments are to use some hyped approach or technology. Doing so will quickly lead you to underoptimized solutions, and your decisions could easily end up damaging the business. Don’t be that person.