Skip to content

Structure

Jump to bottom
Ernesto Fava edited this page Aug 7, 2025 · 2 revisions

This document outlines the technological foundation and modular composition of the system. The purpose is to provide a clear overview of the stack, its structural conventions, and the architectural vision that guides the development process.

Technology Stack

The system is architected following a clear separation of concerns, enabling scalability, security, and maintainability across all layers.

Backend

  • Runtime: Node.js (LTS)
  • Framework: Express.js
  • Authentication: JWT-based system with role-based access control
  • Database: Relational (MySQL)
  • ORM: Prisma
  • External Integrations: Modular connectors for third-party services (e.g., cloud storage, spreadsheets, etc.)

Frontend

  • Framework: React.js or Next.js (dependent on routing requirements)
  • Design System: Component-based UI with utility-first styling (Tailwind CSS or similar)
  • State Management: Context API or Zustand (subject to module scope)
  • API Communication: Axios or Fetch with structured error handling
  • Visualization: Charting libraries for data analytics and dashboards

Directory Structure (In Progress)

The project adheres to a feature-based folder organization. Each functional unit is isolated, promoting modularity and minimizing coupling.

├── package.json        # Monorepo root configuration (workspaces, scripts)
├── pnpm-workspace.yaml # Workspace declaration (if using pnpm)
├── turbo.json          # Turborepo configuration (optional)
├── tsconfig.json       # Base TypeScript configuration
├── .env.example
├── .gitignore
│
├── apps/               # Executable applications (frontend, backend, etc.)
│   ├── frontend/
│   │   ├── public/
│   │   ├── src/
│   │   │   ├── components/
│   │   │   ├── pages/
│   │   │   ├── hooks/
│   │   │   ├── styles/
│   │   │   └── ...
│   │   ├── package.json # Frontend-specific dependencies
│   │   └── tsconfig.json
│   │
│   └── backend/
│       ├── src/
│       │   ├── controllers/
│       │   ├── routes/
│       │   ├── middlewares/
│       │   ├── services/
│       │   ├── db/
│       │   └── ...
│       ├── package.json # Backend-specific dependencies
│       └── tsconfig.json
│
├── docs/
│   ├── README.md
│   ├── Estructura-del-Proyecto.md
│   ├── Stack-Tecnológico.md
│   ├── Funciones-y-Subdivisiones.md
│   └── ...
│
└── .github/
    ├── workflows/
    ├── ISSUE_TEMPLATE/
    └── ...

Each module contains its own:

  • Controller (business logic)
  • Service (data handling and orchestration)
  • Model (ORM schema)
  • Router (API endpoints)

This encapsulation allows teams to work in parallel and reduces merge conflicts during development.

This monorepo serves as the central forge for all modules, tools and extensions. As the system evolves, it will remain adaptable — able to house additional apps (mobile, admin dashboards, etc.) and internal packages without compromise.

Clone this wiki locally