Re: Multi Tiered ODBC

Steve Croft <steve.croft@enterpriseone.com> writes: > > Michael Leo wrote: > > > Rather, I was referring to the Object/Relational mapping solution. > > This architecture is somewhat like: > > > > Client(Java) RMI Object Server(Java) JDBC RDBMS > > (Presentation) -------> (Business Logic -------> (JSQL running > > and Object to against Ingres, > > Relational mapping) msql, whatever) > > > > To me, this is three tier. The second tier can be partitioned across > > several tiers and servers. All of the tiers can run on 1 to N servers > > as your needs dictate. > ... > > Let me know if you disagree. > > If you are saying (and I think you are) that the business logic is *not* > running on the client, then I agree (that is, the business logic objects > are not downloaded to the client and run). > Agreed. The client merely does presentation. Java's RMI (Remote Method Invokation) makes this very elegant. > You've stated an Object/Relational architecture and I'd consider that > a specific case of three-tier architecture. In general the middle tier > would not *have* to be Java or objects.... > The Object/Relational mapping is NOT the second tier. Business logic is. You may include such mapping into the second tier, or instead, put it on another tier. And nothing ever HAS to be Java. I would suggest the architecture of Java (specifically its Object Serialization) lends itself nicely to Object/Relational mapping. JDBC has much greater potential than ODBC, as it runs on ALL Java platforms equally well, and is simpler. Also, the bad experiences of ODBC were of great benefit when designing JDBC. > steve > Enterprise ONE, Inc. > steve.croft@enterpriseone.com Cheers, Michael Leo Caribou Lake Software