.net performance issues between the OO world and a RDBMS

Performance in .net

[Craig Martin]

We have designed a large scale system using OOAD techniques. Ideally the implementation of this should sit on top of an Object database, however a RDBMS has been selected due to certain commercial issues.

With the large amount of complex composite objects we have developed, the logon prcoedure instantiates around 30-50 object instances. This is really not an issue and modern systems instantiate hundereds if not thousands of the object instances to create and maintain composite objects.

We are however having large performance issues and I was wondering if any of you had some tips within this domain that could benefit. We are implementing c# in .net with a 4 layered architecture. The solution is netcentric and will utlise both browser based as well as client based application and presentation layers.

[wardbekker]

Welcome to WebmasterWorld Craig_Martin!

Did you build your own O/R Mapper or do you use a commercial available package? Did you use concepts like lazy loading and smart object caching?

[plumsauce]

just to find out more ...

do you really need 4 tiers?

are objects really the right answer?