OpenEuphoria

Re: DB - Final Question

• Posted by Irv Mullins <irvm at ellijay.com> Feb 09, 2001
• 421 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
> Anybody else, please provide your comments! I'm making a final decision and
> starting work on this project Sunday (Feb. 11, 2001).

CK:

When you say "web serving"  - do you mean the db will be converted to html
and served over the web in read/only mode?  - or does it need to be accessable
as a real, multi-user app with remote client programs reading/writing and
updating the db?

If it's a two way app then you'll need file and record locking. Euphoria
can't do that. 

Nor would an Eu server be appropriate. Apache should be able to handle the
load.  Euphoria cgi's might suffice for managing the communications between the
web  clients and your database. MySQL would probably be a good start, but if
the job is as big as you describe, you'll eventually need to look at Oracle. 

Regards,
Irv