Google AppEngine Uses Jetty
Hot on the heels of Google Widget Toolkit(GWT) switching to Jetty, the little server that can has received some more Google luv'n! Google's new App Engine Java service is powered by Jetty! With App Engine, you can build web applications using standard Java technologies and run them on Google's scalable infrastructure.
Initially it is a little difficult to see Jetty in use, but you can see the jetty classes in the SDK download and if your application throws an exception then investigation of the stack trace in the log reveals the Jetty servlet container is used.
Not only that, the stack trace and other documentation show that Google have really exploited the embeddablility and extensibility of Jetty at a number of levels:
- They are using their own RPC style connector to receive requests from their front end web servers.
- They use the google account authentication as the only supported authentication mechanism.
- The HTTP sessions are clustered via the database or memcache
- There is an appengine-web.xml configuration file
- Jetty is embedded in their SDK and eclipse development plugin.
Thus Google have plugged in many new and/or extended components in a way that validates our open, component based architecture. When it comes to application servers we do not believe that one size fits all and strongly encourage such customization for purpose.
We are really pleased that the google App team picked Jetty for their hosting service and welcome them to the ever growing list of Jetty powered projects!
From http://blogs.webtide.com/gregw
- Login or register to post comments
- 7165 reads
- Printer-friendly version
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)










Comments
Madhu Siddalingaiah replied on Fri, 2009/04/10 - 9:32am
Lior Yaffe replied on Mon, 2009/04/13 - 11:51am
Mike P(Okidoky) replied on Tue, 2009/04/14 - 5:11pm
Ever since, well, can't remember, 2000-ish I guess, I use to balk at Tomcat, its error messages, and its code. I found Jetty way cleaner, nicer, more embeddable, more straightforward, better coded. I could never understand for the life of me the hype around Tomcat. I've embedded Jetty in a few home brewed Javascript servers a few times years ago, and it was an absolutely pleasure. Almost all my dealings with Tomcat have been frustrating.
Seeing JBoss pick Tomcat over Jetty (after supporting both) years ago I found just plain weird. Politically driven?
jiji530 replied on Tue, 2009/06/30 - 12:13am
4shveden replied on Mon, 2009/07/06 - 1:14pm
Hello! I do not see a condition of use of the information. Whether it is possible to copy the text written by you on the site if to put the link to this page?
my site Sökmotoroptimering