高考问答剪纸艺术家李秀芳:有没有关于这篇文章的翻译啊.实在头痛.请教达人!!
来源：百度文库 编辑：高考问答 时间：2024/05/06 05:26:51
Java in the Database
David Ritter
With the release of Oracle8i, IBM's DB2 Universal Database, and similar initiatives from other RDBMS vendors, you can easily treat your database server as an application server. All major relational database vendors now support the use of Java for stored procedures. Using Java, you can put robust business logic straight into the database server, perhaps skipping the middleware issue altogether. Oracle goes as far as to say that you should treat your database as an operating system and let the RDBMS manage your stored data, regardless of its size, format, or use patterns. On the surface, this seems attractive because it removes a number of moving parts from a multitier architecture. Simpler is often better.
If all you have is a hammer, everything tends to looks like a nail. Oracle8i appears to be a very proficient hammer (see Table 1), and from Oracle's perspective I suppose it's only natural for all the data in the world to appear increasingly nail-like. But multitier architecture's central goal is to give you the right tools for the right job. Oracle is attempting to regain some market control by replacing some of the functions of NT, such as the file system. But as developers, we need to carefully distinguish the vendors' marketing messages from real capabilities that meet the needs of our applications. Oracle's addition of operating system features doesn't necessarily make it a better solution for data management problems.
There's good news in the broadening of the architecture and capabilities offered by the latest relational database systems. Standard object technologies such as CORBA and Enterprise JavaBeans (EJBs) are replacing proprietary APIs such as the Oracle Cartridge interface and Informix DataBlades. Java will eventually supplant vendor-specific languages such as PL/SQL. Because we can now use Java at all tiers, developing reusable components on an enterprise scale may finally be practical. The use of these standard technologies indicates that the database vendors are adopting open protocols as they attempt to take over the world. (See Table 2)
But the availability of Java programming in the database raises important questions: How much business logic should you incorporate into your application's database tier? Can you build your systems, as Oracle has suggested, with just a database server and a Web browser? As you might expect, the answer depends on the application requirements.
David Ritter
With the release of Oracle8i, IBM's DB2 Universal Database, and similar initiatives from other RDBMS vendors, you can easily treat your database server as an application server. All major relational database vendors now support the use of Java for stored procedures. Using Java, you can put robust business logic straight into the database server, perhaps skipping the middleware issue altogether. Oracle goes as far as to say that you should treat your database as an operating system and let the RDBMS manage your stored data, regardless of its size, format, or use patterns. On the surface, this seems attractive because it removes a number of moving parts from a multitier architecture. Simpler is often better.
If all you have is a hammer, everything tends to looks like a nail. Oracle8i appears to be a very proficient hammer (see Table 1), and from Oracle's perspective I suppose it's only natural for all the data in the world to appear increasingly nail-like. But multitier architecture's central goal is to give you the right tools for the right job. Oracle is attempting to regain some market control by replacing some of the functions of NT, such as the file system. But as developers, we need to carefully distinguish the vendors' marketing messages from real capabilities that meet the needs of our applications. Oracle's addition of operating system features doesn't necessarily make it a better solution for data management problems.
There's good news in the broadening of the architecture and capabilities offered by the latest relational database systems. Standard object technologies such as CORBA and Enterprise JavaBeans (EJBs) are replacing proprietary APIs such as the Oracle Cartridge interface and Informix DataBlades. Java will eventually supplant vendor-specific languages such as PL/SQL. Because we can now use Java at all tiers, developing reusable components on an enterprise scale may finally be practical. The use of these standard technologies indicates that the database vendors are adopting open protocols as they attempt to take over the world. (See Table 2)
But the availability of Java programming in the database raises important questions: How much business logic should you incorporate into your application's database tier? Can you build your systems, as Oracle has suggested, with just a database server and a Web browser? As you might expect, the answer depends on the application requirements.
参考一下计算机教程吧