One of the dirty little secrets in the world of cloud computing is that there are some performance issues we’re dealing with. These issues are difficult to correct after deployment, and could be death for many initial cloud computing projects.
For the most part these are communication latency issues. Those leveraging public clouds are depending on the open Internet to send and receive data. Thus, if the volumes of data are too high, and the bandwidth too low, you have a performance issue to deal with.
The problem is not around the use of cloud computing, it’s around the architecture and the design of the systems leveraging public or private clouds. Like any traditional system there needs to be some thought around how information flows between “actors” within the solution.
I even go as far as creating performance models to insure that performance issues are unlikely to occur. However, that seems to be a lost art.
In the world of public cloud computing, moving information within a cloud…not a problem. However, moving information between clouds or between clouds and on-premise humans or systems, can be problematic.
So, we need a hero. That hero is a Cloud Performance Engineer. He or she is charged with making sure the deployed systems leveraging cloud-based platforms, private and public, are going to meet performance expectations. This means performance modeling, designing with performance in mind, even building performance management within operations.
So, who’s first to apply for this job?