Back end data store/domain model of the form builder plugin

[limcheekin]

Hi there,

There is feedback from you that the current solution of Dynamic Domain
Class plugin as back-end of the plugin is not scalable or practical in
real world production environment.

I tend to agreed on it especially for SaaS app that may have thousands
of users. The current solution is more suit to development use instead
of production use. In fact, it is the imperfect solution before I
found a better one.

Generally, I can see the following solutions:
1. One generic domain class store all data of different forms
2. Each form has it's own domain class to store it's data

I personally opt for solution 2. I did considered solution 1, but I
haven't figure out how to solve performance issues of sort by column,
search by column, row count operations once the form data reach
hundred thousand rows.

What do you think? I'd love to hear your comments.

Best regards,
Chee Kin