No matter what type of cloud computing solutions an organization is adopting, industry professional David Linthicum said at the recent Interop New York 2013 conference that architecture has to be correct from the start. While there are common elements, he said the differences in architecture can show up "in a big way" and it may take more effort to fix it than it would to get it correct from the start. Charles Babcock, InformationWeek editor at large, recently spoke with Linthicum and was told that cloud based services are often not exercised in the best possible way.

To be successful, Linthicum told Babcock he believes effective IT managers need to map out specific goals for their company and find the best road to meet them. There are many areas where organizations may get caught up if they don't have a clear path into the cloud, so he said there needs to be testing and knowledge of where the business wants to go with the technology.

"One hidden bottleneck to look for is the rate of data transfer between storage and the cloud server or between applications within the cloud," Babcock wrote. "The speed of storage systems responding to calls for data and the speed of data transfers from one source to another will have a constant effect on how well a cloud server or set of servers can perform."

Go beyond the normal best practices
Joe Onisick wrote on Network Computing that there are many benefits of cloud computing solutions, but having flexibility is the biggest advantage for most businesses. Infrastructure is the key to this and must be well designed, he said. Organizations should be going above and beyond to have the best possible cloud based services, as hardware and software must be properly built to meet scalability and design principles should be up to date with where the industry is now.

First, he wrote that companies need to dismiss the idea of "best practices" and figure out what works for them.

"The next step is to arm yourself with the most powerful question in data center design: "Why?"" he wrote. "Apply this to every infrastructure decision: Why should you build a 3-Tier network? Why not use DAS? Why virtualize individual servers? Why build a flat mesh network? Why use VLANs for segregation? Why not use more Layer 3? Why use blades? Why use forced air cooling? Why not use blades? Why use DAS? And many other whys."