Persistence Coupling Alternatives (1/2)
A fat client
- all data from the database is located at the client (Calendarium is located at the client too)
- all checks are performed by the client
B thin client
- on every check, the client accesses the Calendarium within the DB
- B1 methods are implemented on the basis of SQL-statements, operating on relational counterparts of the objects, namely the tuples within the DB (Alternative 1)
B2 methods and all objects which are accessed are located within memory (Alternative 3)