Thick Client - Part 1 (Course Introduction)

Thick Client

  1. Introduction
  2. Static & Dynamic Analysis
  3. Reverse Engineering
  4. Automated Security Audits
Introduction to Thick Client:

 

2-Tier Architecture vs 3-Tier Architecture

These are both types of software architecture models used for building client-server applications. Here's a comparison:

🔹 2-Tier Architecture

Structure:

  1. Client (Presentation Layer)

  2. Server (Data Layer + Business Logic)

Diagram:

Client  <-->  Server (DB + Logic)

Explanation:

  • The client directly communicates with the server.

  • The server handles both the database operations and the business logic.

Example:
A desktop app accessing a database server directly.

Pros:

  • Simpler and faster to develop

  • Fewer layers = less complexity

Cons:

  • Harder to scale

  • Tight coupling between client and server

  • Poor maintainability

🔹 3-Tier Architecture

Structure:

  1. Presentation Layer (Client/UI)

  2. Application Layer (Business Logic)

  3. Data Layer (Database Server)

Client  <-->  Application Server  <-->  Database

Explanation:

  • The client sends requests to the application server.

  • The application server processes logic and communicates with the database.

Example:
Web apps (like online banking systems) with frontend, backend (API/server), and database.

Pros:

  • More scalable and maintainable

  • Better separation of concerns

  • Enhanced security (DB is not exposed directly)

Cons:

  • More complex to build and deploy

  • Slight performance overhead due to more hops



Comments

Popular posts from this blog

Burp Suite – Automated Vulnerabilities Findings

Havij - Advanced Automated SQL Injection

SQL Injection Attacks | Shahul Hameed