Design Consideration

1. Reqirements? Use case diagrams

2. Choosing application tiers: web-centric design, ejb-centric design

In a Web-centric design, Web tier components using container services such
as the JDBC API can communicate directly with the enterprise information
system resources that hold application data.

In an EJB-centric design, enterprise beans running on EJB servers encapsulate
the enterprise information system resources and the core application logic.

There is a trade-off between the two approaches. The Web-centric approach
can enable a quick start for small applications with few transactional needs, while
the EJB-centric approach is better for building a large-scale enterprise application
where code and performance scalability are prime factors. The Web-centric
approach, while more prevalent, has limitations for building large-scale, complex
applications. Applications built with a Web-centric approach can rapidly become
too complex and difficult to maintain.

3. Choosing local or distributed architecture: local ejbs only, or put them at multiple machines?