![]() ![]() ![]() |
![]() |
|
|
![]() ![]() ![]() ![]() ![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Return to Java and Databases Most database systems are designed to be centralized - the database is installed once in a central location and the various applications connect to it. But there are many situations in which a database must be deployed - installed in remote locations, probably without the benefit of a trained database administrator. A deployable database system must be easy to install, require zero management while it's running, and be capable of running on diverse platforms. It must also satisfy the traditional database requirements of standards, performance, and reliability These requirements can be met when the application and database are implemented in Java. Applications that use this architecture can be deployed and yet still retain many of the benefits that centralized database systems were designed to provide. This paper describes the situations in which deploying database applications is desirable, outlines the requirements for a database to be deployable, and describes the aspects of the Cloudscape pure-Java DBMS architecture which make it deployable. It concludes with an example of an application which uses a deployable Java DBMS. DiSC'01 Copyright ©2002 ACM Inc. |