prova Flashcards
- What are the 3 conceptual layers?
presentation layer, application layer, resource manager layer
- Pros and cons TOP-down approach?
pro: focus on high level goals, addresses functional and non-functional requirements
con: can only be applied if the IS is developed from scratch
- Explain bottom-up approach:
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)
- why is bottom-up a good approach?
Design focuses on integration/reuse of existing (legacy) systems/applications. It is not an advantage to use it, but a necessity
- Name the 4 distribution alternatives (understand them all):
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
- what are the five components of CORBA ?
transactional client, transactional server, recoverable server, object request broker, transactional service (OTS)
- in the corba, which components receive prepare command?
transactional service (OTS) and recoverable server
- what are the 3 approaches for coupling database and programming language?
static embedded sql, dynamic embedded sql, and call level interface CLI
- why is SQLJ binary portable?
java is a platform independent language. The use of SQLJ-precompiler/translator avoids DBMS-SPECIFIC precompiler technology. Therefore, compiled SQLJ application is portable.
- which coupling database approach jdbc uses?
CLI
- Which approaches sqlj uses?
embedded sql with binary portability
- which approach uses early query compilation and is vendor-specific?
static-embedded sql
- explain how the components of db-gw support access to multiple database at the same time:
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 call-level interface (cli) static, and dynamic sql
pros: avoids vendor-specific pre-compiler (binary portable program)
- PROS AND CONS static embedded sql (early query compilation)
pro: performance
con: vendor specific pre-compiler. Code resulting from pre-compiler is not portable
- CONS dynamic embedded sql (late query compilation)
con: vendor specific pre-compiler. Code resulting from pre-compiler is not portable