Persistence Connecting to Relational DB - Alternative 2

• Separation of DB access and application specific behavior

  • for each persistent problem domain class, n DB classes are implemented, corresponding 1:1 to the DB relations
  • these DB classes realize both, mapping and access to the DB relations

• Disadvantages:

  • inflexible, high maintenance overhead, poor scalability

saveAppt(appt)

: Calendarium

: DBAppointment

: DBManager

appt: Appointment

save (appt)

get Description

makePersistent

Previous slide

Next slide

Back to first slide

View graphic version