Design Network, Applications to Work Together
"Another fundamental shift that has happened as a result of these new
environments is the requirement to look carefully at the intersection between
the application and network," McGuckin said. "In the past, it was
possible to design the network and application solutions independent of each
other. That wasn't the recommended approach, but you could get away with this
in nearly every situation.
"That is no longer true. The application development [and] deployment team can do everything correctly, as can the network architect, but application performance problems will still be the norm in a global real-time business process."
It also must be noted that newer application environments-including browser-based, thin-client interfaces, X M L-based SOA (service-oriented archictecture) and AJAX-are not optimized for the network. Even though these protocols emerged from the development of the Internet, they still must be optimized to run on it, McGuckin said.
"These environments make accessing user clients and resources across the network very simple from an application development perspective. However, making problems go away for one constituency tends to burden others. In the case of these new protocols, the burden falls onto the infrastructure-server and network," he said.
A tactical guideline put forth by Scott and McGuckin was that an IT manager should always evaluate the security and privacy profile of supplier countries, choosing a country and provider only if the manager is certain he or she can specifically mitigate the risks that will be involved.
The Gartner Data Center Conference continues through Dec. 5.