RE: Java vs .NET was: RPGIII compiler vs Visual Basic

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Walden H. Leverich
> 
> Thought you were talking about "business logic servers", not database
> servers.

Ah, more definitions.  Business logic resides with the database, or at
least it should provided you have enough horsepower in your server.
Application logic can reside in one of three places: client (thick
client), server (thin client), in between (n-tier).

Java can be used for all three application logic pieces.  RPG can also
be a fine application controller.  .NET can be used as an application
controller; I wouldn't use it as a business logic server because I
wouldn't use SQL Server as my database, and I don't like separating my
business logic from my database; the tradeoff between network traffic
and transaction integrity is hideous.


> Again, you're missing my point, or perhaps I'm not being clear
> enough. Steve brought up the question of Java vs. .NET. Now, unless
I've
> missed something really big, neither one is a database server. Your
data
> is in a database server, your apps are written in Java or .NET (or RPG
> or Cobol, etc.) so unless you have stored procs emitting HTML, I think
> the database server isn't really in the conversation here.

I wasn't clear enough about the business logic server as opposed to the
application controller.  The business logic server encapsulates all your
business rules and typically should reside on the same machine as your
database.  The application controller determines what data is displayed
to the user and what data the user sends to the business.

I might consider a .NET appilcation controller, if I were forced to use
Windows as my web application server.  But never for business logic.

Joe