After spending couple of weeks study the appropriate design of a reusable, highly adaptable framework Too bad I'm still having vague ideas about the actual design it should be. Therefore, decided to find some examples online and found .NET Petshop 3.0 and give it a try. Always, good and bad.
Good things is - This PetShop using ObjectPooling and EnterpriseServices for load balancing issues. This is where the part I can take out and this is also an .NET knowledge area, where I should improve myself. Besides, although they design DAL with the intention of "Extensibility" but it don't really that extensible. Yes, it extensible if there is no major changes in database. If so, bad for you as you will have to do a lot of touch-up works in your class.
So, my friend told me about the Axapta (MBS) way; well, pretty impressive and I think I gonna try it out myself tonight.
Cheers.