Network infrastructure clash

Network vendors have focused on elements such as IP addresses and TCP ports to provide a high-performance, secure packet-deliv...

Network vendors have focused on elements such as IP addresses and TCP ports to
provide a high-performance, secure packet-delivery infrastructure. But to
ensure application-level performance and security, application delivery needs
to focus on a different set of key elements the users (who they are and their
role), the application and the nature of their interaction (the session). For
the future, application delivery will leverage, but remain separate from packet
delivery because of these differences in requirements and focus. Its like
refrigerators and ovens just because theyre collocated doesnt mean they
should be integrated.
Most application-performance problems occur because of inefficiencies and
limitations within applications not because of issues with TCP/IP.
Application-performance problems stem mainly from chatty, WAN-inefficient
application protocols stretched over long distances, and they cause long user
wait time (latency). Application-specific optimizations are the only way to
significantly reduce latency. These protocol optimizations, as well as a
comprehensive set of bandwidth-reduction capabilities and business-relevant
application prioritization are possible only through understanding the user,
application and session. Packet-delivery infrastructure understands none of
these things. An application-delivery infrastructure has to.
The evolution of enterprise applications and networks are clarifying the
differences between packet delivery and application delivery and highlighting
the need for separate infrastructures. Most organizations recognize the
different focuses of packet delivery and application delivery, and demand
integration of performance and security at the packet level and separate but
similar integration at the application layer performance and security in a
single device. Just as kitchens dont have "refrigerovens," packet-delivery and
application-delivery infrastructures will remain separate.
Out of the mouths of CIOs
By David Carey, CIO Canada
Its been said a hundred different ways: "Weve got to speak the language of
the business." "Weve got to approach senior management on their own level."
"We cant use technospeak." Or as one former Canadian CEO so bluntly put it,
"Youve got to get the IT lingo right so that the dummies on the board can
understand it..."
No matter how you slice it, it all boils down to the same thing. In the world
of senior business management, tech is a four-letter word.
By now, most foul-mouthed CIOs have gone the way of the dodo (no pun intended).
By foul-mouthed, I mean the ones who wouldnt blush at dropping a giga or a
"SCSI" or an "OLTP" in mixed (read business) company. The rest of you the ones
who still have jobs have learned, in varying degrees, to practice verbal
abstinence when engaged in conversation with corporate management.
Many have even gone so far as to expunge the tech word entirely from their
business vocabulary. In some of our best companies, you will not find an
information technology department it does not exist. Therell be something that
looks like an IT department, that smells like an IT department, that performs
all the functions of an IT department... but it damned well wont be called
one. Youll find it under the name "Information Management" or "Business
Information Services" or some such business-friendly moniker.
Some might scoff at the notion, saying the change is only cosmetic. But
considering the fact that IT is the ugly duckling of enterprise operations,
whatever can be done to spruce up its image has got to be a good thing.
In my view, IT execs who have exhibited religious zeal in eliminating all those
nasty little tech words from their business vocabulary are to be applauded
and emulated. Much as we may think weve bridged the technology/business gap,
there are still far too many business executives who are still convinced that
"IT just doesnt get it." Eliminating the last vestiges of technospeak from our
vocabulary may not get them to change their minds, but its another step in the
right direction.
Shark Tank
By Sharky, Computerworld (US)
Pilot fish gets the job of making sure all changes to production systems are
documented according to ITs procedures. "But I found that most program changes
on our distributed applications were not following the rules," fish says. "When
I raised this issue, it was obvious that the application programming and
network staffs did not comprehend the concept of change management. One
response I got was, All we are changing is executables."
Net admin pilot fish schedules her vacation months in advance and makes sure
her predecessor is available as backup while shes gone. "Imagine my surprise
when I dialed in on my first day of vacation and saw e-mails about some serious
problems at work followed by my predecessors e-mail telling me shed decided
to take off the rest of the week also," grumbles fish. "I canceled my vacation
and went back to work the next day as she left for vacation. Someone obviously
needs to define backup to her."
Help me recover a document, user tells pilot fish. But after many minutes of
trying to find it, fish is baffled. "I finally asked her to go step by step
through what she did," says fish. "Turns out she created the document but was
interrupted and hit close, saying no to the save dialog box. I did my best
not to start laughing but simply explained that a document that was never saved
cannot be recovered."
User calls complaining that when he prints scanned PDF documents, he gets
several copies, but only with PDFs. Show me what youre doing, says support
pilot fish. "I watched him open a document, hit the print icon at the top,
click the next-page arrow, click the print icon, click the next-page arrow and
so on until he got to the end," fish says. "Pretty easy to figure out why he
got four copies of the four-page document."
Network infrastructure clash
packet-delivery doručování paketů
collocated provázaný
inefficiency nedostatek, neschopnost
stem pocházet z, pramenit z
latency doba zpoždění
bandwith-reduction snížení šířky pásma
application layer aplikační vrstva
Out of the mouths of CIOs
bluntly neomaleně, bez obalu
lingo hantýrka, hatmatilka expunge vymazat, vypustit
moniker přezdívka
scoff posmívat se, ušklíbnout se
spruce up vyparádit, vystrojit
vestiges známky, stopy, pozůstatky Shark Tank production system systém výroby
change management řízení změn
imagine představit si
predecessor předchůdce
interrupt vyrušit, přerušit

K tomuto článku není připojena žádná diskuze, nebo byla zakázána.