I have a data entry web application that acts as a control manager deciding which other webforms to invoke. Typically, these are different data entry webforms for some other applications.
I would like to shift the existing business logic from backend C# code to stored procedures in database (Oracle). Additionally, I would also like to store the controls'(ie textbox, label) properties (ie x-coordinate, y-coordinate, width, height) in the database such that they are painted on run-time on to the webform based on users selection . For example, if a user selects "Product" then the set of controls relating to Product information is printed. If user selects "Employee" then set of controls relating to Employee is painted.
I forsee some problems such as re-painting of controls on each postback, incurring addtional database calls to retrieve the controls' properties, caching of controls' state in web server would potentially be huge if there are multiple controls and users.
Is there a better design to such an approach? Appreciate some opinions. Thank you.