How nayelymosquera/registro-de-estudiantes works
Project Type and Purpose
• This is a full-stack monorepo combining:
• A standalone Angular frontend (“frontend-angular”)
• Two Node.js/Express microservices (“estudiantes-service” and “carreras-service”)
• Purpose: provide CRUD operations for students and courses (“carreras”) via REST APIs consumed by the Angular UI.
File Structure Analysis
• Top-level monorepo with three folders:
• frontend-angular: Angular project (with SSR support files like server.ts and main.server.ts, proxy.conf.json for API routing).
• estudiantes-service: Express microservice for student entities (index.js, package.json, CORS enabled).
• carreras-service: Express microservice for course entities (same layout).
• No shared libraries—each microservice is self-contained.
• Proxy config in frontend-angular routes frontend calls to microservices in development.
Key Architectural Insights from README
• Each microservice exposes REST endpoints (CRUD + CORS).
• Frontend communicates with both services to display and modify data.
• No explicit database in the repo—assume each service interacts with its own datastore (in-memory or external DB).