Re: How to handle large number of users

Sandeep Chandra wrote:
I am investigating the possibility to write a server side application to handle a large number of requests. The maximum number of users is estimated to be 10 million.

The application has to update few database tables once a day.

I have never done anything big like this before and was wondering if it would be possible to develop such an application using Delphi(Win32). What technologies would be best suited to handle such a big load?
What database should I use?


10 million users over what period of time? It is not the potential number of overall users your system could have, but how many simultaneous users you should expect, and how many user over what period of time, that is important.

I have written many applications that could support up to 200,000 users over several times per week (100,000 x2TimesPerDays) x7Days=1.4 million per week. Simultaneous user counts could reach 100,000, but usually figure max use at 1/2 that many. System metrics are very important to consider.

Of course the type of application you are building is extremely important. Is this to be a typical Client/Server application or a Web Based Application? Is most of the content delivered statically or dynamically? What is the transaction rate of data per transaction? Is it small, maybe a couple of tables, or is it massive, consisting of many CRUD operations? What is the average amount of data that has to be transfered at one time? This is important, not only from an application perspective, but also from a network latency perspective.

Do you have to interact with other systems? Are these systems real time, mission critical, etc?

Language consideration is important, but not as important as OS used, Database Used, and Network and Hardware infrastructure. But even these questions cannot be answered until you answer the questions above.


Sorry, I cannot give you cut and dried answers, but I do not have enough information to provide adequate answers. One word of caution I would give you; --- do not bite off more than you can chew. If this is a real data intensive Enterprise application that interfaces with mission critical data, the results could be catastrophic!!

Hey, figuring out this stuff is part of my job. That's why I am an EA.

Hope this helps ya.



.

Relevant Pages

  • Re: Limitations to How Many Users can use the same form at the same ti
    ... The standard "split" design calls for one set of data on the backend/server, ... If you really do need to have 300 simultaneous users, ... Server or some other more robust database engine for your backend. ... Created Form to populate information in an Access Database all at the same ...
    (microsoft.public.access.forms)
  • Re: Can I duplicate a record in Access?
    ... though the Jet database engine it uses ... The practical number of simultaneous users depends on the complexity of ... data entry clerks it's worth looking at a more powerful back end than ...
    (microsoft.public.access.gettingstarted)
  • Re: Split Database Pros and Cons
    ... My office has used an application, which I personally developed, in a multi-user environment (with c. 25 simultaneous users at any one time) for about two years now with little to no problems encountered. ... It is not deployed as a FE/BE, rather the linked databases reside on the shared server. ... The largest of about 10 tables in the main database alone contains over 30,000 records, and the main database is linked to a second database on the server so its data can be access through the main database's GUI. ... I, therefore, concur with the MVP's comments, and totally disagree with the author's comment regarding degradation of performance and greatly increased possibility for database corruption. ...
    (comp.databases.ms-access)
  • Could Not Update; Currently Locked
    ... are generally 5 to 8 simultaneous users. ... Record Level Locking. ... This database has functioned properly for about 1 year. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: adding and retriving data from SQL server to VB.net webapp
    ... >> created by VB.net in Visual studio 2003 and a Data base created in SQL ... > preventing it from working that won't be solved by changing database. ... using DAO from VB.Net will likely be ... > many simultaneous users (once you hit more than 10 users at a time you'll ...
    (microsoft.public.data.ado)