True or False: Application acceleration solutions teach developers to write inefficient code

Mike, Mike, Mike. Yes, that's true. However, it is rare to see developers in an organization writing down at the protocol level.

 

 

Most enterprise developers code within a framework; a framework which handles all the protocol layer details. In fact, in JavaEE apps deployed in containers, the application doesn't even begin executing until after the HTTP request has been evaluated by the container and routed down the execution chain to the application.

 

 

The same is true in .NET applications. And while it's certainly possible (and sometimes happens) that PHP/ASP developers will play with sockets, the vast majority of them are not dealing with TCP or even HTTP aside from manipulation of cookies/headers.

 

 

Then you have third-party applications which have similar performance problems but cannot be modified by the customer. Sure, you can complain about the performance, but it's not likely to be improved in a time frame such as that it will benefit you.

 

 

Developers aren't writing at that level in general, and there is a need for external improvements in network performance to deal with the inefficiencies inherent in the protocol stacks implemented in OSs and deployment platforms.

 

 

Those developers that are tweaking the protocols should absolutely be more cognizant of what they are doing and how they are doing it and be as efficient as possible.

 

 

Lori