|
Group: StrataFrame Developers
Posts: 3K,
Visits: 2.5K
|
Well, being a SQL Server application, it all depends upon the hardware of the SQL Server. If you're running SQL Server 2005 on a dual processor machine with 2-4GB of RAM, then we're talking around 300-400 fat clients. StrataFrame is designed to house the majority of the business logic on the client computer, so the server is only burdened with executing joins/queries & CRUD processing. With the connection pooling from the client side, you're looking at around 2000+ connections to the server, which the server can handle with that configuration. However, we are working on an application server and a correspoding DbDataSourceItem (hot swappable with the SQL connectivity on the client side) that will consolidate database connections through the application server. Then it becomes a function of hardware, so you could probably get about 200-250 fat clients concurrencly connected to each application server, and each application server would have around 25-50 database connections to the SQL Server.
So, most everything with StrataFrame is a function of hardware, and with its design, your limiting factor is the number of database connections to the SQL Server.
|