How meeio-app/backend works
Main Components
a) Client Layer:
• External clients (mobile/web applications)
• REST API endpoints grouping
b) Application Layer:
• Controllers (organized by domain: Flashcard, Review, Session, Topic, Unit, User, Admin)
• Security components (Authentication, Authorization)
• Message handling system
c) Domain Layer:
• Entities
• Repositories
• Services
• Spaced Repetition Algorithm
d) Infrastructure Layer:
• Database
• Message Queue
• Cache
• External Services
REST API Architecture
• Main resource endpoints (/flashcards, /topics, /units, /reviews, /sessions)
• Authentication/authorization flow
• Rate limiting component
Domain-Driven Design Elements
• Clear separation of domain entities (Flashcard, Topic, Unit, Review, Session)
• Repository pattern implementation
• Service layer organization
Core Features
• Spaced Repetition System (FSRS4Algorithm, Fsrs4_5Algorithm)
• Analytics capabilities
• User management and security
[Client Applications]
• ↓ HTTP/REST
[API Gateway Layer]
• Rate Limiting
• CORS
• Authentication
• ↓
[Controller Layer]
• Resource Controllers (Flashcard, Topic, etc.)
• Admin Controllers
• Security Controllers
• ↓
[Service Layer]
• SpacedRepetitionScheduler
• Resource Services
• Security Services
• ↓
[Domain Layer]
• Entities
• Repositories
• Value Objects
• ↓
[Infrastructure Layer]
• Database (Doctrine)
• Message Queue (Symfony Messenger)
• Cache
Important Relationships to Highlight
• Authentication flow through TokenAuthenticator
• Message handling system for email notifications
• Entity relationships (User -> Topics -> Units -> Flashcards)
• Spaced repetition algorithm integration with review system
Technical Stack Callouts
• Symfony Framework
• Doctrine ORM
• Symfony Messenger
• Docker/DevContainer
• Apache Server
• Supervisor Process Manager
This architecture emphasizes the RESTful nature of the application while showing how the spaced repetition system is integrated into the core business logic.