Re: DB - Final Question
- Posted by Irv Mullins <irvm at ellijay.com> Feb 10, 2001
- 461 views
On Fri, 09 Feb 2001, CK wrote: > For my current project, I need a database (Eu or MySQL), front-end (Eu or > ?), and web server (Eu or ?). Right now I'm focusing on the database and > front-end. Here are my options: > > 1. Eu database with Eu front-end > 2. MySQL database with Eu front-end > 3. MySQL database with xx front-end > > Concerns: > a. multi-threads - for multi-user access > b. web serving > c. scalability - for millions of records in multiple databases > d. multi-platform capability - starting w/Linux but client might want a > Windows version in future CK: If you could give more details you could get more definitive answers. I understand you may be withholding info in order to protect your client and/or your future income. If so, some of us would be willing to sign non-disclosure agreements. On the other hand, perhaps your client is being vague regarding his/her needs. That can get you into hot water very quickly - you need to have some serious discussions and draw up some specifications before you get burned. If you want to discuss this privately, feel free to e-mail me. That said, given the limited info above, it should be clear that DOS is out of the question - multi-threading and web serving are not exactly DOS's strong points :) Why develop a db and front-end on DOS if you won't be able to use it later? So, that leaves Linux and Windows. You probably don't want to buy NT server right now, so I suggest you stick with Linux. If you design your project right, you may never need to bother with NT at all. You say you need multi-threads for multi-users, and web serving. Are the users accessing the db via the web server, or are these two different groups of people doing different tasks? (Networked users maintaining the db, and others viewing the data via the web?) Can you meet the UI requirements using nothing more than standard web browsers and forms, or are there some factors that rule this out? Once you thoroughly describe exactly "what" the system is expected to do, the "how" will likely be obvious. Regards, Irv