Client-side session replication for clusters
using cometd/bayeux
Techniques for replicating session data include distributing: to all nodes in a cluster; to a subset of the nodes in the cluster; to a database; to a cluster server; etc. etc. To this range of solutions, cometd/bayeux now adds the possibility of using the client machine to store replicated session.
20,000 reasons why Jetty scales
Benchmarking Jetty's Cometd Bayeux implementation
I have published a comet Daily article that describes how I have benchmarked Jetty's Cometd implementationof dojox Bayeux protocol to 20,000 simultaneous clients. This blog looks at the same results from a more Jetty centric view point.
Blocking Servlets, Asynchronous Transport
Lies damn lies and benchmarks
The web-2.0 Ajax Comet use-cases have been getting most the attention when it comes to asynchronous features of servlet containers. The Asynchronous features are needed so that a request may wait without a thread allocated while waiting for a comet event to deliver to the Ajax client.
However, there are some compelling use-cases for traditional web-1.0 applications to benefit greatly from asynchronous features. Previously I have looked at how threadless waiting for resources can improve quality of service. In this blog, I look at how an asynchronous servlet container like Jetty can greatly improve the scalability for serving medium and large content. Furthermore, I reveal how your benchmarking is probably not giving you the full story when it comes to scalability.
However, there are some compelling use-cases for traditional web-1.0 applications to benefit greatly from asynchronous features. Previously I have looked at how threadless waiting for resources can improve quality of service. In this blog, I look at how an asynchronous servlet container like Jetty can greatly improve the scalability for serving medium and large content. Furthermore, I reveal how your benchmarking is probably not giving you the full story when it comes to scalability.