1 |
Need to use mix of approaches -- choosing what is good and what will last
|
2 |
For example develop Web-based databases with Java objects using standard JDBC (Java Database Connectivity) interfaces
-
Oracle DB2 Informix Sybase, Lotus Notes, Object database confusion becomes an issue of performance/robustness NOT functionality
|
3 |
Even better use (Enterprise) Javabeans which are Java's (middle tier) or client componentware offering visual interfaces, containers (here they are consistent with CORBA standard) and standard software engineering interfacing rules
-
e.g. Java Blend is built on top of JDBC to use enterprise Javabeans to store Java Objects in relational databases
|
4 |
Use CORBA to wrap existing applications
|
5 |
Note Middle tier insulates client from backend -- can use one object model for user level and different one for backend
-
specialized object databases getting "overwhelmed" by multi-tier approach with Oracle etc. traditional backends
|