The No.1 i-Technology Magazine in the World !
   
 

      ES no BS
       My son's animations and music            training         Twitter            No BS IT podcast

Archives

««Mar 2010»»
SMTWTFS
  123456
78
9
10
11
12
13
14
1516
17
181920
21222324252627
28293031

RSS Feed








Subscribe to these blogs

Top ten ways to screw up an enterprise Java application

posted Thursday, 24 August 2006
Tonight, I’ve attended Java SIG meeting in New York. CameronPurdy of Tangosol was presenting on ten thing that will help you to screw your enterprise Java application. This was a re-run of his JavaOne talk.

#10 To specify your data access model before you understand the granularity
#9 Assuming that container will take care of transactions
#8 Using a stateless architecture
#7 Design the application for deployment on a single server and assume that that server will handle reliability and scalability for you
#6 Using popular technologies such as WebServices for component integration and remoting
#5 Rolling your own frameworks
#4 Distributing of synchronous objects across the network
#3  Design logic and data flow assuming that this is a single user system
#2 Compensate for lack of knowledge of the application domain by maintaining flexibility
#1 Put off the system testing until the application is ready to deploy

It’s always fun to listen to Cameron.

tags:    

links: digg this    del.icio.us    technorati