| Caching Web Content |
[Dec. 19th, 2009|09:51 pm] |
We all know that a gentleman always separates the static content from the dynamic for web apps. A proper setup will normally have an Apache web server, where the static images, css, and js is stored and an application server (tomcat or BEA) where all the java or dynamic content is stored. Normally on top of this layer, the handling of certificates for SSL and the balancing of load takes place with "sophisticated equipment". At my past project they used Nortel Alteons and for my new project they use Oracle Web Cache.
Then because we are "SOA complaint", we need to think about the ESB (Enterprise Service Bus) and how the web services are published. If one of your webservices, consumes another web service from the ESB then the "web cache" is really a pain in the ass. I was getting 10% connection loss when the ESB admin screwed up the configuration. Obviously I had to prove it. Thanks god there is JMeter. After a 20 min test I was able to document the "End Of File" and "socket connection closed" errors.
So be very careful with those "caching technologies"... they tend to get in the way. |
|
|
![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
machingo's Friends Page