Common Problems in Application Development

The aim of this article is an introductory familiarization with the results of the first case studies dealing with the evaluation of the object-oriented paradigm in collaboration with the data layer [16]. From the conducted survey of ORM Framework possibilities and subsequent consultation with companies implementing these frameworks, various questions have arisen that form the main basis for this article. We focused primarily on whether it is possible to prevent the decrease in performance of applications implementing ORM Frameworks with an increasing amount of managed data [10]. What is the most suitable implementation of an ORM Framework in terms of performance and availability of the resulting software, and how can the required memory for processing large volumes of data be reduced with the help of an ORM Framework. It also explores if it is possible to eliminate the need for custom data consistency checks or validations. ORM issues are often addressed due to their extensive use [5]. [11] investigates the impact of transactional cache and object cache on application performance and application behavior, [13] focuses on ORM issues at the schema level. A description of the underlying ORM issues of Hibernate can then be found in [9], while they also mention issues related to object unserializability, missing access methods, simple paging and more. From the area of design patterns, one can also point to one-to-many antivorms in Hibernate, where each antivor is described including the implications and recommended solution [15].