How prateekp3108/test works
Project type and purpose
• You have a hybrid architecture:
• A full-stack Laravel “monolith” that serves Blade views and Livewire components (the app/, resources/views/, public/ folders, etc.).
• A microservices ecosystem (under services/…) that handles cross-cutting concerns (authentication, file storage, image processing, notifications, PDF generation, analytics, external integrations, a queue-worker, user profiles).
• A Node-based API Gateway (api-gateway/) that routes API calls to the monolith or the individual microservices.
• The README calls this “Freshman CMS,” built on Laravel Breeze + the TALL stack (Tailwind, Alpine, Livewire, Laravel).
File structure
• Top-level:
• app/, resources/, public/, routes/, config/, database/, bootstrap/ → traditional Laravel monolith
• api-gateway/ → Node.js gateway container
• services/… → each subfolder is a standalone microservice with its own Dockerfile, controllers, routes, config
• Notice that each service:
• Exposes a RESTful API (e.g. routes/api.php)
• Has its own Dockerfile for containerization
• Encapsulates a single domain function (e.g. auth-service, pdf-service, image-service, etc.)
• The presence of queue-worker-service plus Laravel’s job classes in the monolith implies an asynchronous, event-driven pattern.