background preloader

Java Server App

Facebook Twitter

Killer Java applications server with nginx and memcached. Last days I worked setting up a new web serving structure for Wine, the largest wine’s e-commerce in Latin America.

Killer Java applications server with nginx and memcached

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. If the response was not found on cache server, then nginx forward the request to Tomcat, which process the request, cache the response on memcached and returns it to nginx.

Tomcat works only for the first client, and all other clients requesting the same resource will get the cached response on RAM. 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.

Jetty Continuations: Push Your Java Server Beyond Its Scalability Limits

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). One solution for improving existing optimal throughput and scalability without adding resources is Jetty Continuations. 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.

Home. Build a Social Intranet eXo Platform is an out-of-the-box social intranet solution.

Home

Rich collaboration features such as wikis, forums, calendars and documents are smartly integrated around activity streams, social networking and workspaces. It is carefully designed to instantly engage users. It runs within the trusted security of an enterprise platform and is highly customizable to adapt when your needs evolve. Learn More Build Social Websites eXo Platform has inherited strong capabilities for managing websites from its portal platform roots. But it is also a fantastic platform for content-centric applications. However, they can also be used in the front end if you need to engage your visitors!

Learn More. Redis - Project Hosting on Google Code. Bored of Apache/LightHTTPD/etc.? Try Mongrel2. October 28, 2010 – 6:09 pm Tags: Web Mongrel is a refreshing approach to web servers.

Bored of Apache/LightHTTPD/etc.? Try Mongrel2

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? It’s language agnostic. It doesn’t have a PHP module, it doesn’t have a Python module, and yet you can still use those languages (and plenty more) with it, with very little effort to integrate new languages. 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. This makes Mongrel special. Yaws. Tomcat On Steroids (with EJB 3) = Apache TomTom. Tomcat On Steroids (with EJB 3) = Apache TomTom Apache TomTom is an opensource, easy to install EJB 3.1 container.

Tomcat On Steroids (with EJB 3) = Apache TomTom

It is lacking CDI, so it is not a full Java EE 6 WebProfile server. The test: Download size (tomtom-6.0.29.313.zip ): 28 MBInstallation = UnzipDisc size: 36,9 MB after installationStartup: same as tomcat: . /startup.shDeployment: copy of the LeanestInterceptor.war into tomtom-6.0.29.313/webapps. Please keep in mind that the LeanestInterceptor is just a Smoke Test The overall impression - good. Posted at 11:11AM Nov 02, 2010 by Adam Bien in Real World Java EE Patterns - Rethinking Best Practices | | Views/Hits: 21. Netty 3.2.3.Final. Location: Trustin Lee - the developer behind Netty NIO client server framework announced today, that the new version 3.2.3 of Netty has been released: Quoting interesting pieces from Trustins announcement: What's new since 3.2.2.Final...

Netty 3.2.3.Final

This release is a stability release which fixes 4 known bugs. Thank you everyone who waited for the fix so patiently! About Upcoming Releases... I am thinking of beginning Netty 4.0 which addresses the fundamental issues such as: upstream/downstream naming confusion OutOfMemoryError caused by too fast writes incomplete HTTP tunneling transport incomplete custom thread naming (DONE) along with the following new features: HTTP file uploads IP-level firewall traffic counter / shaper JMX integration HTTP and SOCKS proxy support on the client side. Jetty Continuations: Push Your Java Server Beyond Its Scalability Limits.

Caucho Resin : Reliable, Open-Source Application Server.