Architecture
| Cut | Description |
|---|---|
| User Interface | Ultra-thin client: Just echos out character by character with no JavaScript or links |
| ↕︎ | UI on Client: Processing is allowed on client side just for displaying; Browser renders static HTML. |
| Application | Client does some processing; Validates forms before submitting |
| ↕︎ | Thick Client: Connects directly to database manager; Has a native look/feel. |
| Data | Cache data on client; Responsive and less network congestion. |
Thin Client Advantages Over A Thick Client
Stateless
Performance
- 1 (expensive) call to get back a ton of data
- Computations on the server side won't slow down the client
Flexibility
- You can update the app without changing the client logic
Robustness
- You can log data at the app level and it won't be presented to the user
Security
- Authentication works better if the user doesn't have access to all the company data
Skeleton 4-Tier
- User Interface
- Presentation Layer
- Business Logic
- Data
Skeleton n-Tier
- User Interface
- Caching
- Presentation Layer
- Business Logic
- Workflow
- Business Logic
- Data