The Top Ten Ways to Botch an Enterprise Java Application
Only ten?
If you're planning on heading to JavaOne this year, Cameron Purdy will be presenting what sounds like a very interesting talk on the top ten ways to botch an enterprise Java application. From his blog...
Two of my presentations were accepted for JavaOne, including a new one that I've been working on: The Top Ten Ways to Botch an Enterprise Java Application. I think the hard part will be limiting myself to only talking about ten of the things that I've seen! ;-)
I've given some funny (and unfortunately real-world!) anecdotes as part of some of the presentations that I've done on scalable performance and distributed caching, including the "checking the HR database on each HTTP request to see if the current user got fired since his/her last HTTP request" (one of my favorites). So what is your personal "Top 10 List" for ways to completely botch an application?
Reading through the comments, there are some funny stories and I only wish that I could say I've not seen these myself. One of the best ways to learn about architecture, what works and what doesn't, is to listen to others talking about their experiences. If you're at JavaOne, don't miss this opportunity.
