How diegopaez2/modamix works
Project Type & Purpose
• A monolithic full-stack web application (Laravel 10) serving as a clothing store (“Tienda de ropa”).
• It includes both a customer-facing storefront (Livewire, Blade) and an admin panel (Filament).
Top-Level Architecture Components
a. Client Tier
– Web browser (JS/CSS assets served via Vite)
– Mobile/Web apps (if present in future)
b. Presentation & HTTP Tier
– Nginx/Apache + PHP-FPM handling HTTP(S) requests
– Routes (web.php, api.php, auth.php) → Controllers & Livewire components
c. Application Tier
– Controllers (app/Http/Controllers)
– Livewire Components (app/Http/Livewire) for dynamic UI
– Filament Admin Resources (app/Filament/Resources)
– Service Layer (app/services/InvoiceService.php)
– Event‐Driven Modules
• Events (app/Events)
• Listeners (app/Listeners)
– Mailers (app/Mail)
– Middleware (app/Http/Middleware)
d. Domain/Data Tier
– Eloquent Models (app/Models)
– Migrations & Seeders (database/migrations, database/seeders)
– Factories (database/factories)
e. Infrastructure & Integrations
– Database (MySQL/PostgreSQL)
– Cache & Sessions (Redis/file)
– Queue (Redis/Database)
– Filesystem Storage (local/S3)
– External Services
• SMTP/Mailgun for transactional emails
• Payment gateways (e.g., Stripe)
• CDN (optional for assets)
Architectural Patterns & Design Principles
• MVC Pattern (Models, Views, Controllers)
• Component-Based UIs (Livewire, Blade components)
• Admin-as-Code (Filament Resources)
• Service Layer (InvoiceService) to encapsulate business logic
• Event-Driven (OrderStatusChanged → OrderCompletedListener)
• Dependency Injection via Laravel’s service container
• Configuration-as-code (config/*.php) for 12-factor compliance
Technologies & Frameworks
– Laravel 10 (PHP 8)
– Livewire (real-time front-end without SPA framework)
– Filament (admin panel scaffolding)
– MySQL/PostgreSQL (RDBMS)
– Redis (cache, queue)
– Vite (asset bundler: JS & CSS)
– Tailwind CSS (styles)
– PHPUnit (tests)