A travel company is designing an application to allow customers to browse for information on any
flights operating domestically and to place new reservations on any of those flights. The company
makes the following assumptions: significant read volume, in terms of operations the customers
will perform significant overlap, in the search criteria of customers simple processing of each
customer browse/update request What advice can you give this company?
A.
use a two-tier architecture (rich client directly accessing the database) because running
copies of the business logic in each client provides significant advantages in terms of
processing time per request
B.
use a three-tier architecture (thin client -> application server -> database) because executing
business logic remotely on a central location results in better performance per request
C.
use a three-tier architecture (thin client -> application server -> database) because the shared
business server allows them to cache information with high likelihood of cache hits, which
reduces the load on the database
D.
use a two-tier architecture (rich client directly accessing the database) because each client
can operate on its own business objects, independently of others, which provides significant
advantages from reduced latency due to synchronization