| Excerpt |
|---|
Layered Architecture is commonly using when design J2EE application - it is something like defacto standard and widely known by most architects, designers, and developers. The layered architecture pattern closely matches the traditional IT communication and organizational structures found in most companies, making it a natural choice for most business application development efforts. |
| Gliffy Diagram |
|---|
| name | Layered Architecture Pattern |
|---|
| pagePin | 2 |
|---|
|
website.One of the powerful features of the layered architecture pattern is the separation of concerns among components. Components within a specific layer deal only with logic that pertains to that layer.
| Gliffy Diagram |
|---|
| name | Layered Architecture Pattern |
|---|
| pagePin | 2 |
|---|
|
One of common Layered Architecture is following Following is the example of 4-tier architecture. It can be simplified to 3-tier or 2-tier by the case.
| Gliffy Diagram |
|---|
| |
|---|
| name | 4-Tier Architecture Pattern |
|---|
| pagePin | 1 |
|---|
|
Presentation layer (UI layer라고도 부름)Application layer (service layer라고도 부름)Business logic layer (domain layer라고도 부름)Data access layer (persistence layer라고도 부름)