Re: Multi Tiered ODBC
Posted in 1996
Topics: SQL Development & Query Writing, Connectivity: ODBC / JDBC / .NET, Security, Permissions & Auditing
On 17 Nov 1996 17:36:59 GMT, "Bill House" <mail28511@dazsi.com> wrote: >I consider physical 3-tier to mean that the middle-tier box is the only box >actually connected to the database server, and that it totally arbitrates all >of the database access for its clients. This is contrasted with logical >3-tier, where the business logic is housed and maintained on a separate >server(s), but the client still accesses the database via business objects >downloaded from the business object server. Logical 3-tier has the scaling >advantage of distributing the processing and connection overhead to the >clients, while only physically deploying the objects on the business object >server. > >What benefit do you believe there is to pure physical 3-tier, as opposed to >logical 3-tier (if indeed you believe there is one)? There's an obvious security advantage to physical three-tier. This advantage is often oddly compromised by hard-coding usernames and passwords in clear text program code. Funny isn't it? Physical three-tier is also the obvious way to deploy systems where you want to be able to use SQL at the client level, but all the information you can really get out of the top (mainframe) tier consists of canned COBOL reports whose programmers have disappeared into the mists of time, but that can be automagically ftp'd to the middle layer, which can then dissect them and answer queries it receives from the client layer. But I may be talking about a different kind of beast altogether. Gregor [feeling froggy because my JoinBuilder is working better today]