note 46046 deleted from tutorial by philip

Note Submitter: simonpointer at bigi dot co dot uk ---- With such a wide array of choices for web applications, making the right one sometimes seems daunting. I like the hammer analogy, but in my experience there are quite a few who think they need a large hammer like J2EE and java, when a PHP, mySQL solution would work just as well. I mean, it supports 60,000 tables and many terabites of data - how much data and complexity do you think you have? I once worked for a large corporate that chose the J2EE route (a good choice for many reasons). However, we soon found hardware and development costs to be quite high. We found development slower and more complex, and that we rarely needed or used the power afforded by the J2EE solution. In many developments we had to scale back to a simple .jsp solution to make development more cost effective. If your not sharing lots of functionality on an enterprise scale, you probably don't need a J2EE style hammer. Remember once your in one boat, it's not always easy to jump ship mid ocean! Make a good choice to start with. Scaling up is easier and more cost effective, than scaling down.