Design issues in enterprise applications !!!
1. How to choose what should be there in presentation layer.
2. What should be there in Persistence layer?
3. What should be there in Business layer?
4. What should be there in services layer?
5. What are the deployment issues to be taken care?
6. Design patterns to be used.
Anyother issue plz add/discuss.
I know that all the above are based on the requirements.
You need to be subscribed and logged on to view this session. If you are a subscribed JavaOne Online user, please log on to view this session. If you wish to subscribe, please click here.
TS-3708(USA,2003) - Concurrency Utilities -- Multithreading Made Easy
The Java[tm] platform provides basic primitives for writing concurrent programs, but they are difficult to use properly. Many programs become clearer, shorter, faster, easier to write, and more reliable if, instead of starting from scratch, you use higher-level synchronization and coordination constructs. A comprehensive library of concurrency utilities is being developed under (JSR-166) for planned inclusion in the 1.5 release of the Java[tm] 2 Platform, Standard Edition (J2SE[tm]). This library, known as util.concurrent contains thread pools, queues, concurrent collections, special-purpose locks, barriers, and related utilities. This talk provides you with all the information you need to start using this library, which is already available in preliminary form.