An interesting thing happens when you combine toolkits like XAJAX and SAJAX and the ability to perform content-based routing: you can actually achieve function-level load balancing in both cloud-based and traditional architectures.

xajax-logo As you might have discovered from previous posts mentioning it, I still do web application development to support hobby interests in my (very little) spare time. I’m currently in love with the XAJAX library, which has made development of what is supposed to be a very interactive application nearly effortless.

I’m also very much enamored of load balancing/application delivery and cloud computing, specifically how to get the most out of the latter using the former. XAJAX is a perfect example of how the choice of development environment can impact – positively – the ability of an intelligent intermediary to drill-down into sajax-logothe application workload on a functional basis and more efficiently distribute requests to get the most out of an architecture. 

Before someone argues that SAJAX is a better choice I’ll include it, as well, as a “this is a great option, too” for cloud computing environments. XAJAX is strictly for PHP (which is fine for me but not for everyone) while SAJAX supports a broader range of languages and data formats – XAJAX supports only XML, which for purposes of integrating with my BIG-IP via iControl is just fine but again, may not suit everyone’s needs. Both XAJAX and SAJAX pass as part of the data exchange the server-side function being invoked, which is really what’s necessary to accomplish load balancing at the functional layer and what makes both very well-suited to building highly scalable web applications for cloud computing deployment.