top of page

System Architecture


Presentation Layer (Frontend/UI)



Description: This layer handles the user interface and user interaction. It communicates with the backend to display dynamic content and ensures a seamless user experience.

Technologies:

  • React.js for building interactive and reusable UI components.

  • HTML5/CSS3 for structuring and styling.

  • TailwindCSS for design and layout.

  • JavaScript for functionality and logic.

Key Responsibilities:

  • Display data fetched from the backend.

  • Send user inputs and interactions to the backend for processing.

  • Provide responsive and interactive UI/UX.


Application Layer (Backend/API)



Description: The application layer processes the business logic, handles authentication, and serves as the intermediary between the frontend and the database.

Technologies:

  • Node.js as the server runtime.

  • Express.js for handling HTTP requests and routing.

  • JWT for authentication.

  • RESTful API for communication with the frontend.

Key Responsibilities:

  • Process and validate requests from the frontend.

  • Implement business logic and rules.

  • Manage authentication and user sessions.

  • Expose APIs for the frontend to fetch data or trigger actions.



Data Layer (Database)


Description: This layer manages data storage and retrieval. It ensures data is persisted securely and efficiently.

Technologies:

  • MySQL for relational data storage.

  • PhpMyAdmin for database interaction.

Key Responsibilities:

  • Store application data such as user profiles, transactions, or content.

  • Handle data queries, updates, and relationships.

  • Ensure data consistency and integrity.



System Architecture Diagram


Here’s how the components are interconnected:

  • User Interface (React): Sends requests to and receives responses from the backend.

  • API Gateway (Express.js): Processes frontend requests, applies business logic, and communicates with the database.

  • Database (MySQL): Stores and retrieves data as required by the backend.

Table of content

  • System Architecture

bottom of page