Home

Jetty Continuations: Push Your Java Server Beyond Its Scalability Limits With the phenomenal growth in Internet usage, a Web server's limited scalability often is a bottleneck when handling increased user loads. In fact, scalability is a necessity when business expansion results in more user interaction with your Web applications. These applications include functions such as chat, collaboration, bidding, RSS broadcast, GPS, and real-time data. Two challenges in particular that current Web servers and applications encounter are the thread-per-connection concurrency model and asynchronous JavaScript and XML (Ajax). Jetty Continuations suspend an HTTP request and releases the thread to the thread pool. While Continuations is an obvious solution for such applications, they are also complex to implement. In this article, I will present a use case that explains how to use the Continuations API. Jetty Continuations Use Case: Stock Trading I have chosen a hypothetical case of the trading domain. We need to implement these four tasks in a Web container. Page 1 of 2

Bored of Apache/LightHTTPD/etc.? Try Mongrel2 October 28, 2010 – 6:09 pm Tags: Web Mongrel is a refreshing approach to web servers. We’re all familiar with the Apache server and many of us have used Lighthttpd and Nginx and maybe some others too. So what makes Mongrel special? Simplified overview of mongrel’s architecture When serving a PHP application, a server like Apache processes the HTTP request and then invokes some module – mod_php in PHP’s case – which then processes the scripting language in question and so on. Mongrel? How does it do anything useful then, you ask? So the HTTP request comes to Mongrel, which then processes it and converts it into a sensible format containing the vital info (headers, parameters, etc., in JSON) and gives it to ZeroMQ. Since ZeroMQ is just a message queue, you need to have something listening for messages and replying to them. This makes Mongrel special Herein lies the thing that makes Mongrel special: It’s easy to replace apps and scale. You can have a PHP app. Share this:

Yaws Killer Java applications server with nginx and memcached | Francisco Souza Last days I worked setting up a new web serving structure for Wine, the largest wine’s e-commerce in Latin America. After testing, studying and learning a lot, we built a nice solution based on nginx and memcached. I will use a picture to describe the architecture: As you can see, when a client do a request to the nginx server, it first checks on memcached if the response is already cached. nginx nginx was compiled following Linode instructions for nginx installation from source. % . After install nginx and create an init script for it, we can work on its settings for integration with Tomcat. See the last line inside http section: this line tells nginx to include all settings present in the /opt/nginx/sites-enabled directory. 404: memcached module returns a 404 error when the key is not on memcached server;502: memcached module returns a 502 error when it can’t found memcached server. Java application Now is the time to write some code. web.xml <? That is it!

Caucho Resin : Reliable, Open-Source Application Server