Database persistence with Enterprise JavaBeans

The problem of database persistence is well known and well documented. However, with the introduction of the Enterprise JavaBeans architecture new issues have arisen. Now you have the choice of delegating all the work of persistency to the application server, but what effects will this have on performance and stability? If you choose to manage all persistency on your own, will the extra complexity introduced really be worth it? This is the kind of question this thesis will attempt to answer. I have defined a variety of different strategies and evaluated them all. This evaluation will attempt to determine all aspects of any given strategy in order to get an overview of the pros and cons of different solutions. It has not been my intention to find the solution, since this may vary depending on the requirements. Nevertheless, I hope to make it easier for future developers of systems based on the Enterprise JavaBeans architecture to find the persistence strategy that best matches their requirements.Validerat; 20101217 (root