How devgather/tiary works
Main Components (Top Level)
• TIARY |
Frontend Layer Security Layer Application Layer Infrastructure Layer
Component Details
A. Frontend Layer:
• Static resources (/static/)
• HTML templates (Thymeleaf)
• CSS and JavaScript files
• With controllers through REST endpoints
B. Security Layer:
• OAuth2 authentication
• JWT token management
• Web security configuration
• User details service
• Authentication providers
C. Application Layer (Core):
• Controllers:
• Account management
• Profile handling
• TIL (Today I Learned) operations
• Comment functionality
• Tag management
• Services:
• Business logic implementation
• Data processing
• DTOs:
• Request/Response objects
D. Infrastructure Layer:
• Database:
• JPA repositories
• Domain entities (Account, Profile, TIL, Comment, Tag)
• AWS Integration:
• S3 for storage
• Mail Service
• Exception Handling
User Request → Frontend → Security Filter → Controller → Service → Repository → Database
• ↑ ↑ ↓
• ┴───────────── Response ────────┘
Cross-Cutting Concerns
• Logging filter
• Exception handlers
• Security filters
• Properties configuration
External Services Integration
• AWS S3
• Email service
• OAuth providers
Additional Elements
• Deployment configuration (Docker)
• CI/CD workflow connections
• Database schema relationships
• Cache layers if applicable
Key Architectural Patterns to Highlight:
• MVC pattern implementation
• Repository pattern for data access
• DTO pattern for data transfer
• Filter chain for request processing
• OAuth2 + JWT for authentication
Domain-driven design principles
This design reflects a modern Spring Boot application with robust security, scalable architecture, and clean separation of concerns, as evidenced by the project structure and configuration files.