- How do the Spring 3.0 REST features compare to JAX-RS? Definitely also check the comments.
- Wicket IPageStore implementation using Hazelcast ("open source clustering and highly scalable data distribution platform").
Wicket now powers the mobile sites for Wallmart and Wellsfargo. Main reason for chosing Wicket: "... makes it easy to support multiple different types of devices. The walmart mobile application supports different HTML for three categories of devices (L1: iPhones & challengers, L2: BlackBerries, L3: Plain Old Devices). These three experiences are supported by the same Java code on the server side."
Great that the implementers have open sourced their components. Especially interesting is the 'wicket-stateless' component, since Wicket at its core is focused on managing stateful behaviour.
Also great to read is that in Wicket 1.5 support for variable/unknown URLs will be available. In that post you can also read how to do that in Wicket 1.4.
- Great post on how MySpace tested their site live with 1 million concurrent virtual users (mixed with live users) using 800 EC2 instances. For example, the setup generated over 77,000 hits per second, not including live traffic. The article also includes 3 lessons learned.
- A short article on why eCommerce site Zappos (shoes and apparel) re-architected their site from Perl to a Java EE environment. Main reason for them was to better deal with scaling and demands on high performance. The website serves "millions of users/visitors daily and processes between 60-65.000 purchases every day". Includes some best practices, and a more-or-less infomercial on using Dynatrace as their application performance management solution.