Research

As Networks and Applications Converge, New Challenges Emerge

The traditional view of an IT environment defines clear lines of responsibility between the network infrastructure and the applications groups. But that's all changing.

By Chris Coffin

February 28, 2006 — CSO —

The traditional view of an IT environment defines clear lines of responsibility between the network infrastructure and the applications groups. Put simply, if the network is running, itâ¬"s running, and if a problem arises with an application, then that problem is one for the applications people.

Web-based applications are putting an end to those simpler times. The ubiquity of the web gives software developers more flexibility and allows them to manage fewer and larger databases. What used to be a discrete, self-contained application on a server is being replaced by large relational databases at the back end and a flexible interface at the front end, connected by middleware. And the basic networks of the past ⬠which connected Point A to Point B ⬠must now be carefully monitored and load-balanced to ensure that data traffic flows efficiently and the applications donâ¬"t crash.

As a consequence, network support teams must address technical issues well outside of their traditional purview. The Open Systems Interconnect Reference Model of the ISO divides the network into â¬Üseven layers,â¬" beginning with layer one (the physical wire) and ending with layer seven (the application), with each layer assigned specific characteristics and protocols. While network people have typically worked up to layers two and three ⬠switches and router tails ⬠theyâ¬"re increasingly being asked to troubleshoot at the application layer.

Because of these changes, network groups are now managing content engines, load balancers, and data traffic to an extent they previously haven't. In a broader sense, this evolution of the network support groupâ¬"s role is forcing closer ties between application developers and the network support group. Most organizations are only beginning to deal with these changing requirements. Some are diverting resources to troubleshooting, while others are locking down on testing requirements. But in most cases, the challenge is only beginning to be recognized.

The long-term solution is to build skills. But having said that, it should be recognized that a skills gap exists, and that at this point applications people tend to be ahead of the curve, with the network people playing catch-up. One approach is to force interaction between network and applications people. However, long-standing barriers and cultural differences ⬠specifically, between the blue-collar network workers and the aristocracy of the applications group ⬠have made effective communication difficult. But itâ¬"s increasingly important that the network perspective be included in technology planning and implementation.

• Email
• Print
• Comments
• Digg This
• SlashDot