DimitarSD/app-market

• App Market
• Technology Stack
• System Architecture
• Database Schema
• Overview
• Flow & Interaction
• API Endpoints
  • Authentication & User Management
  • Publisher Management
  • Application Management
  • Application Version Management
  • Application Status History
  • Analytics
  • POS Models Management
  • Merchant Management
  • Admin Operations
  • Search and Filter

The architecture diagram shows the interaction between different microservices in the backend, micro frontends in the frontend, databases, and the various roles of users (Admin, Publisher, Merchant, User). The system is designed to be modular, allowing independent development and deployment of each microservice and frontend component.

The database schema diagram provides a detailed look at the relational structure of the database. It includes tables for managing users, applications, application versions, publishers, merchants, and application status histories. The schema is designed to ensure data integrity and efficient querying, with clear relationships between each table.

1. Frontend

   • The Web Application: is the main interface where users, merchants, and publishers interact with the App Market. It's built using React.js and Vite.js, with Ant Design or Material-UI (MUI) for the UI components (TBD). Zustand is used for state management as it's easy to use, setup and scale.

   • The frontend is split into smaller, independently deployable modules (micro frontends) like the Publisher Portal, Apps Dashboard, and Admin Interface. Each module has a dedicated role, making it easier for publishers to manage their applications, for users to browse the market, and for admins to oversee the whole platform.

2. Backend

   • The backend is made up of several microservices built with Node.js and Express.js. Each microservice focuses on a specific domain. This modular approach makes sure each service can be developed, deployed, and scaled independently without affecting the others.

   • JWT (JSON Web Tokens) is used throughout the backend for secure authentication and authorization.

   • Databases: The system relies on PostgreSQL as the main relational database for storing things like user data, application details, and status histories. Elasticsearch is also integrated, handling complex search queries quickly and efficiently.

3. DevOps & Monitoring:

   • Docker The entire application will containerized with Docker to ensure consistency across development, testing, and production environments.

   • CI/CD pipelines will be set up using platforms like GitHub Actions or GitLab CI/CD, depending on which source control system we're using.

   • Monitoring: Datadog is great tool we can use for monitoring the health, performance, and security of the application.

• User Journey: Users, merchants, and publishers all interact with the App Market through the Web Application. Depending on their role, they might access specific micro frontends, like the Publisher Portal for managing apps, or the Admin Interface for approving or rejecting submissions.

• Backend Processing: Every request from the frontend is routed through the Backend API, which coordinates with the relevant microservices to get the job done. Data is stored and retrieved from PostgreSQL, while search queries are handled by Elasticsearch.