Day 8 – Enterprise Application Architecture Patterns – Overall consideration


Consider three aspects of technology practice: continuous integration, driving test development and refactoring

1. Start at the domain level

1) Transaction script mode is the simplest, suitable for building on relational database; domain model needs very professional technology, as well as the connection of fish database; table module mode compromise, environment with very powerful recordset support such as. Net is very suitable.

2) In theory, tools can be selected according to architecture; in practice, they can be matched.

2. Deep into the Data Source Layer

1) Transaction script data source:

The alternative database schema is row data entry and table data entry. The choice between the two depends on the convenience of the implementation platform and the future development direction of the system (e.g. tools included in the development platform, such as supporting record collection tools).

2) Data source of table module:

There’s a good recordset framework – > seamless with table data entry mode

3) Data sources of domain models:

If the model is fairly simple (for example, there are only a dozen database-related classes), then the activity record is sufficient.

If you want looser coupling, you can use table data set entry or row data entry.

When more complex, you can consider using a data mapper (work unit pattern fetching)

3. presentation layer

1) If circumstances permit, use HTML instead of fat customer interface as far as possible;

2) If you follow the HTML route, use mvc;

3) net uses page controller + template view, Java uses front-end controller + template view;

4) Document-oriented site, using page controller, in complex cases can consider the use of front-end controller;

5) View Selection: Template View (Server Page), Transform View (XSLT)

4. Some suggestions on specific technologies

5. Other layering methods