The session “Top 10 Patterns for Scaling Out Java Technology-Based Applications” was presented by Cameron Purdy, Vice President, Oracle.  In this discussion, Purdy layed out 10 ways to scale  Java applications.  This session was very good, but the slides were jammed with information.  Purdy said that this was normally a 90 minute discussion crammed into 50 minutes.  He talked very quickly and it was very hard to take notes.  I will try to highlight the 10 “patterns”, but being able to see the slides when they become available will be very beneficial.

10. Understand the problem: Before trying to scale the application make sure that’s really the problem.  A scalability problem exists, if the application is fast for a single user, but slows down as more and more users access the application simultaneously.

9. He blew by this slide so fast, I missed it.

8. Architecture Trumps Technology: Don’t be misled into believing that some technology or language that was selected for the project is causing the scaling problem.  Any technology can be scaled.

7. Understand the Basics: Learn about messaging and distribution instruments and efficient uses of those technologies.

6. Visualize the Network: Understand routing, partitioning, and replication.

5. I missed this one, too … (I told you he was moving fast)

4a. Plan for Overload: Add load balancing where appropriate

4b. Partition for Scalability: Partitioning is the only way to scale in stateful systems.

3a. Plan for Failure: Try to build in fault tolerance.

3b. Replicate for Availability: Replication adds fault tolerance, but it can cost you performance.

2. Tier Where It Makes Sense:

1. Simplify: Unnecessary complexity makes finding problems difficult.

I will post the slides once they become available.