Hello ,

We are creating an application that requires dynamic creation of objects and their attributes (which may be linked to other objects as well) .We are currently using an EAV model to handle this where they are stored as Attribute-Value pairs . We have also used hibernate dynamic mappings to retrieve these data's from a view(which is again created dynamically). This works fine for us now , but I am not sure about the system's scalability for large volumes of data. We also need to create ad-hoc reports from the stored data ,which may pose to be a challenge.

I was wondering if we could do away with the EAV model and create DDL scripts every time an object / an attribute to that object is created and use dynamic mapping for these newly created tables. Would this be a good design ? Also I saw a post that mentioned that dynamic mappings is in an experimental feature in hibernate. Is it advisable to use hibernate in such a scenario or would it be better if I just stick to the EAV model ?