presentation layer, application layer, resource manager layer
pro: focus on high level goals, addresses functional and non-functional requirements
con: can only be applied if the IS is developed from scratch
1 - define access channels and client platforms
2 - examine existing resources and their functionality (RM layer)
3 - wrap existing resources, integrate them into consistent interface (AL layer)
4) adapt output of AL for client (P layer)
Design focuses on integration/reuse of existing (legacy) systems/applications. It is not an advantage to use it, but a necessity
transaction as unit of distribution, application as unit of distribution, db operation as unit of distribtuion, middleware controls distribution
transaction as unit of distribution pros and cons:
pro: simple and easy solution. works in heterogeneous environments
cons: inflexible, limited scope, transaction restricted to single node
application as unit of distribution. Pros and cons:
pros: locaIIty processing. Supports application reuse.
cons: inflexibility regarding data access operations. Complex program model. db access operations cannot reach across multiple nodes\
db operation as unit of distribution. Pros and cons:
pro: high flexible for data access
con: increase communication onverhead, program model complexity
middleware controls distribution:
pros: high flexible data access,simple and powerful programing model
cons: increased communication overhead, schema integration required
transactional client, transactional server, recoverable server, object request broker, transactional service (OTS)
transactional service (OTS) and recoverable server
static embedded sql, dynamic embedded sql, and call level interface CLI
java is a platform independent language. The use of SQLJ-precompiler/translator avoids DBMS-SPECIFIC precompiler technology. Therefore, compiled SQLJ application is portable.
CLI
embedded sql with binary portability
static-embedded sql
the Driver Manager manages interactions between Applications and Drivers and it is capable of realize n:m-relationship between application and drivers. It loads the drivers for the multiple databases and it maps the data sources to the drivers.
pros: avoids vendor-specific pre-compiler (binary portable program)
pro: performance
con: vendor specific pre-compiler. Code resulting from pre-compiler is not portable
con: vendor specific pre-compiler. Code resulting from pre-compiler is not portable
in orthogonal persistence the persistence is independent of data type, class. Instances of the same class may be transient or persistent. Independence persistence, also known as transparent persistence, the code operating on transient and persistent objects is basicaly the same. There is no impact on the client object when interacting with persistent objects. There is no special codign for implementing persistence.
Bean Manager Persistence (BMP)
CMP
Bean manager persistence - BMP
endpoint