|
|
@@ -1,14 +1,16 @@
|
|
1
|
1
|
<html>
|
|
2
|
2
|
<body>
|
|
3
|
3
|
<p>
|
|
4
|
|
- This is the application layer: code that's needed for the application to
|
|
5
|
|
- performs its tasks. This includes code that directly depends on external libraries
|
|
6
|
|
- such as Hibernate and Spring MVC, implementations of JMS interfaces, remoting and so on.
|
|
|
4
|
+ This is the application layer: code that's needed for the application to
|
|
|
5
|
+ performs its tasks. It defines, or is defined by, use cases.
|
|
7
|
6
|
</p>
|
|
8
|
7
|
<p>
|
|
9
|
|
- This part is very technology-heavy and generally not comprehensible to the domain expert,
|
|
10
|
|
- unlike the domain part. It is thin in terms of knowledge of domain business logic,
|
|
11
|
|
- although it may be large in terms of lines of code.
|
|
|
8
|
+ It is thin in terms of knowledge of domain business logic,
|
|
|
9
|
+ although it may be large in terms of lines of code.
|
|
|
10
|
+ It coordinates the domain layer objects to perform the actual tasks.
|
|
|
11
|
+</p>
|
|
|
12
|
+<p>
|
|
|
13
|
+ This layer is suitable for spanning transactions, security checks and high-level logging.
|
|
12
|
14
|
</p>
|
|
13
|
15
|
</body>
|
|
14
|
16
|
</html>
|