The Components of Caché

With three different ways of connecting to Java, Caché is the ideal high-performance database for Java applications. Caché data can be accessed with SQL via JDBC, and Caché classes can be projected as Java classes or as Enterprise Java Beans. Projections are automated, so Java developers can gain data persistence without a lot of tedious coding.

Providing Data Persistence for Java Developers

Java is an extremely popular technology for Web development, but connecting Java applications to a persistent data store can be challenging. Connecting to a relational database often requires manual coding of SQL commands according to the JDBC protocol. Many Java developers prefer to use object-oriented databases, whenever possible. And large distributed systems may benefit from sharing data and functionality in the form of Enterprise Java Beans, managed by an application server. Caché supports all of these approaches for achieving data persistence within Java applications.

SQL/JDBC

Caché’s efficient multidimensional data engine has excellent SQL response – up to 20 times faster than relational databases. Caché includes a Type 4 JDBC Driver, so Java applications that already use SQL and JDBC for connecting to a data store can be ported to Caché without changes.

Java Classes

Developers who prefer to work in an object-oriented environment can use Caché classes – projected as Java classes – directly. Creating Java projections is easy with the Caché Studio, and InterSystems provides a Java class library that allows Java programmers to access Caché.

Providing Persistence for J2EE Applications

Developers of J2EE applications, which use Enterprise Java Beans (EJBs) to share data and functionality across distributed systems, usually face a choice between using Container-Managed Persistence (CMP) or Bean-Managed Persistence (BMP).

Container-Managed Persistence		Bean-Managed Persistence
CMP relies on the application server to generate JDBC persistence methods for EJBs. While this approach removes the burden of manually coding these persistence methods, it increases the processing load on the application server, which can result in poor scalability and slow response times. Through its JDBC interface, Caché can provide ultra-fast database response to applications using CMP.		BMP relies on developers to code and optimize persistence methods for EJBs. It is the only option for developers who wish to access an object (as opposed to a relational) database. BMP requires more work, but can result in better application performance and scalability. Caché provides a wizard for projecting Caché classes as EJBs, automatically generating high-performance persistence methods. Thus, EJB developers gain the excellent scalability and quick response times afforded by BMP, without the need to do a lot of tedious coding.

Caché’s Enterprise Java Beans are supported on the following application servers:

• BEA WebLogic v6.1 (SP3), 7.0(SP1)
• JBOSS + Tomcat v3.0.4, 4.1.12
• Pramati v3.0(SP4)

JDK 1.3 is required for use of JDBC, EJB, or the Caché Java binding.