How l1a-crew/zzekak-api works
Main Components
a. Core Architecture Layers:
• API Module (External Interface)
• Core Module (Domain Logic)
• Infrastructure Module (Data & External Services)
• Batch Module (Scheduled Tasks)
b. Key Domain Components:
• User Management
• Appointment System
• Address/Location Services
• Mission System
• Push Notification System
External Clients ─► API Layer
• ▼
• Core Layer
• ▼
• Infrastructure Layer
• ▼
• External Services
Detailed Component Breakdown
a. API Layer (Blue Components):
• REST Controllers
• Security Config (JWT Authentication)
• Exception Handling
• Swagger Documentation
• Health Check Endpoints
b. Core Layer (Green Components):
• Domain Models
• Use Cases
• Repository Interfaces
• Business Logic
• Domain Events
c. Infrastructure Layer (Orange Components):
• Database Repositories
• External Service Integrations
• S3 Storage
• Push Notification Infrastructure
• Entity Mappings
d. Batch Processing (Purple Components):
• Scheduler Configuration
• Push Notification Batch Jobs
• Batch Services
Important Relationships to Highlight
• JWT authentication flow
• Appointment creation and management flow
• User authentication and authorization paths
• Demonstrate push notification delivery system
• Address/location service integration
Technical Details
• Database connections
• External API integrations (for address/location services)
• AWS S3 integration
• Push notification service
• Scheduled batch jobs
Additional Elements
• Security layer showing JWT filter and token provider
• Exception handling flow
• Audit logging path
• Batch scheduling timeline
• Push notification delivery flow
Specific Implementation Notes
• Clean architecture separation between api/core/infra modules
• Domain-driven design approach in the core module
• Demonstrate the repository pattern implementation
• Batch processing schedule and triggers
Remember to:
• Use consistent notation
• Brief descriptions for complex flows
• Version numbers for major components
• Error handling paths