Stefan Norberg presents Unibet.com’s architecture, the challenges faced and the solutions adopted in order to sustain live and offline betting over an entire continent. They started with a monolithic database and moved towards a finely tuned front-end architecture - XHTML 1.0, CSS 2.1, YUI, caching, compression, image spriting, CDN striping – plus using multiple replicas for scaling out.
This session takes an inside look at successfully delivering from concept to cash, showing the technical aspects of what's required to iteratively build a robust product that always performs, and the skill and discipline needed to deliver high-quality software to production every week. We know this because we wrote one of the busiest entertainment Web sites in the UK from scratch.
This presentation covers how to rapidly evolve a web site that receives over 25 million unique users and 218 million page impressions a month using a "just in time" approach to architecture. The site was guardian.uk with a long history of innovation that has enabled it to lead the market. The "just in time" approach to architecture introduced complexity into the architecture only as needed.
The real world experience building Lombardi Blueprint is used as a case study to introduce the use of GWT, why it was successful and why it has become the platform of choice for other Lombardi products. One goal of the presentation is to argue for the use of GWT as the foundation for RIA development.
A lightweight approach with a rich domain model used directly in web-tier can increase both quality and speed of development. This case study, recorded at Javapolis, looks at a Tapestry+Spring+Hibernate project by Nordija, how it was architected, how testability was introduced, and the level of simplicity achieved using the lightweight approach.
Toronto.Com attracts over 700,000 unique visitors per month, and offers comprehensive and searchable access to business and event listings. Originally built in 1997, the Java/J2EE technology foundation for the site was expensive and time-consuming to maintain, and limited TorStar Digital's ability to share content and functionality between Toronto.Com and other properties.