December 15, 2006
Survivor's Guide to 2007: Application InfrastructureDial XML For Security We're usually picky about using the term SOA security instead of the more generic XML security. But in 2007, you'll see plenty of XML traffic in addition to SOA traffic. If it isn't coming from your internal SOA initiative, then it'll be coming from third-party, packaged applications that use Ajax or SOAP to communicate from browser to server. Problem is, though they're going to be a fact of life in 2007, Ajax and Web 2.0 technologies, such as mashups, lack inherent security mechanisms. Therefore, you'll have to weigh your security options for these technologies carefully. Fortunately, most SOA security vendors are moving to deal with the somewhat unbounded Ajax and mashup technologies already available, and have products ready to ensure that XML messages traveling from browser to server aren't carrying something that they shouldn't be, such as viruses or malicious code. For example, Layer 7 Technologies announced XML Data Screen in October, specifically to deal with non-SOAP XML traffic such as REST (Representational State Transfer), POX (Plain Old XML) and Ajax. In 2007, we'll be taking a look at how well these products can handle the increased traffic and arrival rates of requests that come along with Ajax-based applications. XML-focused networking products have always been hampered by lower throughput than other networking devices, due to the compute-intensive process of parsing XML, but this weakness has always been easily dismissed because of the lack of high-volume XML in the enterprise. Ajax and a robust SOA are set to change that and bring performance of these products back into the forefront as something to consider strongly when making a purchasing decision. You'll need to do some capacity planning in general, as the arrival of AJAX and mashups will likely strain back-office servers, maybe even put a damper on server-consolidation efforts by gobbling most of the processing power on that server you thought you were going to share with another application.
|
|
|||||||||||||||||||
|
|
|
|