Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 16 total
Thread EWB And Databases
Mon, Sep 3 2012 10:46 PMPermanent Link

Frederick Chin

Correct me if I am wrong:

If I want to deploy an EWB application to use DBISAM in an internally hosted web server, the DBISAM server needs to be running in the computer hosting the web server for the EWB application to retrieve and update DBISAM tables.

If I want to deploy an EWB application to use DBISAM in a third-party hosted web server, that would not be possible unless the DBISAM server can be run from the server. Instead, I will have to use an alternative database like MYSQL or MSSQL that is typically used by the third party host.

If I decide to use DBISAM now for an internal application, it would be easy (or not easy) to change access to another database should the client require the application to be hosted externally.

Frederick
Mon, Sep 3 2012 11:01 PMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

<<
Frederick Chin wrote:
If I want to deploy an EWB application to use DBISAM in an internally hosted web server, the DBISAM server needs to be running in the computer hosting the web server for the EWB application to retrieve and update DBISAM tables.
>>

The back-end (web service) needs to have access to DBISAM. EWB only talks to back-end server and not to database direct. You can either run the DBSRVR or if you write the back-end in delphi then it can access DBISAM direct.

<<
If I want to deploy an EWB application to use DBISAM in a third-party hosted web server, that would not be possible unless the DBISAM server can be run from the server. Instead, I will have to use an alternative database like MYSQL or MSSQL that is typically used by the third party host.
>>
Same scenario as above. For PHP and especially for non-windows hosting you might be better off using some other DB. EDB for example has PHP version but only on Windows AFAIK. Depending on the app just get a virtually hosted VM so you have full control (though costs would be bit higher than just PHP/MYSql web hosting).

<<
If I decide to use DBISAM now for an internal application, it would be easy (or not easy) to change access to another database should the client require the application to be hosted externally.
>>

If you write the DB access layer generically enough then switching DB's is quite doable.

Note that EWB always talks to back-end web service so there will be no EWB changes required when you switch DB - only back-end needs to be changed.

Raul
Tue, Sep 4 2012 9:01 PMPermanent Link

Frederick Chin

Raul wrote:

/*
The back-end (web service) needs to have access to DBISAM. EWB only talks to back-end server and not to database direct. You can either run the DBSRVR or if you write the back-end in delphi then it can access DBISAM direct.
*/

It would seem that the least amount of work, as far as connecting to databases is concerned, would be to use a common DB for both internal and external hosting environments. EWB would then talk to a web service (probably written in PHP) to update and retrieve data.

I believe EWB is still missing the web service portion for DBs other than EDB with none for DBISAM?

Frederick
Wed, Sep 5 2012 9:51 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Frederick,

<< I believe EWB is still missing the web service portion for DBs other than
EDB with none for DBISAM? >>

First and foremost, EWB was originally not intended to have any external web
services included.  I'm now starting to include them, due to demand, so it
will take a bit of time to get everything in place.

Secondly, I would always recommend running any sort of critical web
application using a virtual server environment that you have control over,
as opposed to a shared host that puts restrictions on what you can deploy
and how you can deploy it.  The latter is cheaper, but you're probably going
to run into a performance or configuration issue eventually that will make
such an option unattractive for reasons besides price.

Tim Young
Elevate Software
www.elevatesoft.com
Wed, Sep 5 2012 10:12 AMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

Frederick Chin wrote:
<<
It would seem that the least amount of work, as far as connecting to databases is concerned, would be to use a common DB for both internal and external hosting environments. EWB would then talk to a web service (probably written in PHP) to update and retrieve data.
>>
Absolutely - using a common DB is simplest and in our case we just exposed our data access using web services  and wrote the whole thing in delphi.

<<
I believe EWB is still missing the web service portion for DBs other than EDB with none for DBISAM?
>>

I would say it another way - EWB database access is complete as of know. The data access layer in EWB is generic and not tied to any specific database.  What's missing is DBISAM side support for web service  + XML but not the other way around. There is nothing that needs to be done in EWB to add dbisam support.

Sorry if i'm saying things that are obvious but it's an important distinction - somebody will come and aks for MS SQL or MySQL support in EWB and asnwer will be same - EWB is complete for those and you need to make changes on the "other end".

Raul
Wed, Sep 5 2012 11:36 AMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

<<What's missing is DBISAM side support for web service  + XML but not the other way around.>>

Should be JSON (not XML)

Raul
Thu, Sep 6 2012 12:05 PMPermanent Link

Frederick Chin

Tim,

/*
Secondly, I would always recommend running any sort of critical web
application using a virtual server environment that you have control over,
as opposed to a shared host that puts restrictions on what you can deploy
and how you can deploy it.  The latter is cheaper, but you're probably going
to run into a performance or configuration issue eventually that will make
such an option unattractive for reasons besides price.
*/

When you say virtual server environment, are you saying running a server in-house?

Frederick
Thu, Sep 6 2012 1:32 PMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

I think Tim means what's called virtual private hosting or VPS - meaning
you have your own virtual server that is completely under your control
so you can install anything you want and run any app you want.

Number of companies provide this including Amazon EC2 and it's become
quite affordable (Amazon EC2 free usage tier is a good way to get
started for example as its free for new customers).

Raul

On 9/6/2012 12:05 PM, Frederick Chin wrote:
> When you say virtual server environment, are you saying running a server in-house?
Thu, Sep 6 2012 3:00 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Frederick,

<< When you say virtual server environment, are you saying running a server
in-house? >>

What Raul said.  It's one of the reasons why we haven't ported our PHP
extension or ODBC driver to Linux.  Most of the shared hosts that use Linux
won't let you install *anything* like that, so it's kind of a waste of our
time to create something that can't be deployed.  And, if you're using a
virtual machine instance (or your own server), you might as well use Windows
and be able to install anything you want (and can create using
Delphi/C++Builder/Visual Studio) on it.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com
Thu, Sep 6 2012 5:34 PMPermanent Link

Steve Gill

Avatar

Hi Tim,

<< Secondly, I would always recommend running any sort of critical web
application using a virtual server environment that you have control over,
as opposed to a shared host that puts restrictions on what you can deploy
and how you can deploy it.  The latter is cheaper, but you're probably going
to run into a performance or configuration issue eventually that will make
such an option unattractive for reasons besides price. >>

It's interesting that you say that because I have been running backend processing apps on hosted Linux servers for over 10 years and have never had a problem.  I guess it depends on who you host with, and what type of systems you develop.  I do agree though that a virtual server is a better option.

Steve
Page 1 of 2Next Page
Jump to Page:  1 2
Image