Is it OK to use Java Application in client/server RDBMS project?

[Anton]

Hello everybody,
I am software developer and was involved in all sort of projects but mostly it was C, C++, MFC for Windows, however it has been some time since my last client/server RDBMS project and there are number of changes in this part of software development. Right now we plan to use Borland JBuilder 5 for Java Application, client side at least. So I have just started to look at it, at samples, etc… Main idea - we want to have platform independent application, not to be dependent on Microsoft platforms and we do not want separated "platform dependant" projects for the same product.
However I have number of doubts about Java. At this stage I found that Java Applications (java client, jdbc, etc...) are less reliable, slow, memory “hungry”. User interface is less comfortable. So far I have not seen and have not heard about good client/server commercial Java Applications and even JBuilder itself (java application too) is not that much impressive.
Please understand me right, I need advice from experienced people about it from technical point of view and do not want to start discussion about personal preference because I am happy to work with any dev. environment if it gives what I want.
So:
- Why would you use Java? (Except “theoretical platform independence”)
- Would you use Java if your project was only for one platform? If Yes, why? If not, what would you prefer?
- Could you confirm and/or argue against my “disappointment” in Java
- Any other ideas on this subject and/or forums/sites where I could get more info.
- Any alternative technology/language/dev. environment for client/server DB Applications. (Once again I would prefer from your real experience)
Thank you,
Anton

 

[svanels]

I do not know java (nor interested), but I use Delphi in some client server apps (windows). There is also kylix (delphi for linux, unix) to consider if you target these platforms.
It is possible to port a M$ Windows based application to Linux, allthough there are limitations.
One of them is that ActiveX is bound to Windows, so this you have to leave-out.

Hope this helps S. van Els
SAvanEls@cq-link.sr

 

[2ffat]

We've used Java for DB apps. Yes, it is slow but so are the VB apps we've used. I personally prefer C++ but I have no problem with Java or Delphi for that matter. Your big advantage is easier cross-platform independence (unless MS succeeds in killing Java on Windows). Just food for thought, no real answers here I'm afraid.
James P. Cottingham

I am the Unknown lead by the Unknowing.
I have done so much with so little
for so long that I am now qualified
to do anything with nothing.

 

[tdatgod]

Hi,
There are 2 standards to code to ODBC and JDBC.

JDBC is an OPEN Java interface to allow it to connect to any Vendors Database product that supports the JDBC protocol.

Basically the same JAVA code should be able to run simply by changing the name of the machine you wish to connect to.

Whether JDBC ( or Java in general ) is slower or less 'comfortable' than MFC and the ODBC interface I couldn't tell you. I have never used either of them.


As for the database server side like I said JDBC doesn't care. it could be oracle, Sql Server, Access, or even NCR's own Teradata ( what I work on )

If you want a full blown FREE copy of Teradata, including a JDBC example you can get one at

http://www.teradata.com/dwdemo

It also has a VB example using ODBC so you can compare the code to see which you think is better.

--

 

[Anton]

Thanks all for some info and ideas, Anton.