REAL TIME EVENT-TICKETING SYSTEM - W2051853

📍Overview

This real time event ticketing system is designed and implemented to handle advanced producer-consumer pattern with multi threaded process and advanced synchronisation.

Key Features:

• Multi-threaded Producer-Consumer pattern

• Real-time updates on ticket availability

• Advanced Synchronisation

• Dynamic Log Display

🚀 Getting Started

Make sure to follow the below guidelines to properly interact with the system. Follow the instructions to setup both backend and front end of the project.

⚠️ Pre-requisites

Ensure you have properly installed:

• Java 17+ (for backend development with Spring Boot)

• Node.js 14+ (for frontend development with Angular)

• Maven (for backend dependency management)

• MySQL or PostgreSQL (for database management)

• Git (for version control)

⚙️ Installation

Backend Installation

1. CLI is modular from backend.Run the CLI independatly.

2. Navigate to the backend directory.

  cd backend

3. Install backend dependancies using Maven.

  mvn install

4. Run the backend main application: BackendApplication.

5. The backend uses the port http://localhost:8080 .

Frontend Installation

1. Navigate the frontend directory.

  cd frontend

2. Install frontend dependencies.

  npm install

3. Run the Angular application.

  ng serve

4. The frontend will be accessible at http://localhost:4200 .

📌 Features

• Multi-threaded Ticketing : Advanced producer-cinsumer pattern

• Real time Pool Management :Real-time updates on ticket status

• Dashboard : Real-time ticket status with control panel and configuration execution

• Advanced synchronisation

• API: Necessary endpoints for third-party integrations

🧩 Modules

Command Line Interface

• Customer Modules : Manage consumer-related tasks

• Vendor Modules : Manage producer-related tasks

• Ticketing / threads modules : Manage ticketing and threading

• Logging and save to JSon files : Tracks all transactions for real-time monitoring

Backend

• Customer Modules : Manage consumer-related tasks

• Vendor Modules : Manage producer-related tasks

• Ticketing / threads modules : Manage ticketing and threading

• Logging services : Tracks all transactions for real-time monitoring

Frontend

• Dashboard : Displays real time pool status, sold tickets, real-time logs

• Configuration Form: Allows users to configure system parameters

• Add customer and vendor : Add customer and vendor to the system

🧑‍💻 System Architecture

The system allows a microservice architecture with including following components:

• Backend: Spring Boot service with RESTful APIs

• Frontend: Angular-based UI

• Database: MySQL/PostgreSQL

• Real-Time Communication: Perioding Polling for live updates and Rxjs for state management

Backend Components

• Ticketing Service: Handles the ticket pool, synchronization, and updates.

• Vendor Manager: Controls the creation of tickets by vendors.

• Customer Manager: Manages ticket purchases by customers.

• API Layer: Exposes HTTP endpoints for interactions.

• Database: Stores user data, tickets, and transaction history.

Frontend Components

• Dashboard: Displays real-time ticketing information.

• Add-vendor / add- customer : Separate add sections for vendor and customer.

• Configuration Form: Allows the configuration of ticket parameters.

💻 System Workflow

1. Vendors add tickets to the pool.

2. Customers buy tickets, reducing the pool size.

3. Real-Time Synchronization ensures both vendors and customers are aware of ticket availability.

4. The CLI updates the transaction details of ticketing

5. The UI Dashboard updates continuously to reflect changes in the ticket pool.

📂 Repository Structure

├── backend
│   ├── src
|   |   ├──CLI
|   |   |__BackendApplication
│   ├── pom.xml
│   └── README.md
|   ├── records.log
│   ├── save.json
│   
├── frontend
│   ├── src
│   ├── package.json
│   └── tailwind.config.ts
└── README.md