I have my up in production running fine for about 2 weeks now. I have about 30 concurrent users now. That will increase to about 500 soon at first... and perhaps up to a limit of about 5000 - 10000 concurrent users.
In my app I have several classes ... about 3 business logic classes and about 10 other data access classes within the APP itself.
I have not used COM+ before though I read on it a few times. I know I could have compiled my classes separately into a .NET assembly or DLL (or component) and referenced it from ASP.NET but I chose not to for speed of development!
(did that in VB6 previously)
Now I made sure that I close all my connections religiously each time I open one ..... and actually I only used datareaders and stored procedures for speed .. which has worked great so far.
I have a huge 70Gig server with 4Gig memory. I read ADO.NET automatically uses database connection pooling ..which was one of my biggest reasons for thinking about COM+. Also I run transactions on my ADO.NET connection object a few cases in this app.
So I start to wonder if I need to take out my 13 business and data access classes and compile them separately and host it as a COM+ application. Is it necessary? Thus far the app is running great and I'm wondering if my concern is necessary at all!
The back-end is SQL Server 2000. Does COM+ bring its own problems or complexity too? Or I'm I thinking in the right direction for scalablility?
Will appreciate your comments.
In my app I have several classes ... about 3 business logic classes and about 10 other data access classes within the APP itself.
I have not used COM+ before though I read on it a few times. I know I could have compiled my classes separately into a .NET assembly or DLL (or component) and referenced it from ASP.NET but I chose not to for speed of development!
(did that in VB6 previously)
Now I made sure that I close all my connections religiously each time I open one ..... and actually I only used datareaders and stored procedures for speed .. which has worked great so far.
I have a huge 70Gig server with 4Gig memory. I read ADO.NET automatically uses database connection pooling ..which was one of my biggest reasons for thinking about COM+. Also I run transactions on my ADO.NET connection object a few cases in this app.
So I start to wonder if I need to take out my 13 business and data access classes and compile them separately and host it as a COM+ application. Is it necessary? Thus far the app is running great and I'm wondering if my concern is necessary at all!
The back-end is SQL Server 2000. Does COM+ bring its own problems or complexity too? Or I'm I thinking in the right direction for scalablility?
Will appreciate your comments.