How cognitoagent/planbot works
Main Components
a) Client Layer (Frontend):
• React.js application structure
• Key components: Authentication (SignIn.js, Register.js), Admin Panel, Event Creation
• Component hierarchy showing the relationship between parent/child components
b) Server Layer (Backend):
• Spring Boot application structure
• Controllers layer (REST endpoints)
• Service layer (business logic)
• Repository layer (data access)
• Security components (JWT authentication)
c) Database Layer:
• PostgreSQL database
• Main entities: User, Post, Comment, Suggestion, ImageAttachment
d) External Services:
• Google Calendar API integration
• Email notification service
[Frontend Layer]
• ↕ HTTP/REST
[Backend Layer]
• ↕ JPA
[Database Layer]
Detailed Component Breakdown
Frontend (React.js):
• Main components: Authentication, Admin Panel, Event Dashboard, Event Creation
• State management flow
• Routing structure
Backend (Spring Boot):
• Controller Layer: UserController, UserLoginController, HelloController
• Service Layer: UserService, PostService, JWTService, MyUserDetailsService
• Repository Layer: UserRepo, PostRepo
• Security: SecurityConfig, JwtFilter
• Domain Models: User, Post, Comment, Suggestion, ImageAttachment
Integration Points
• JWT authentication flow between frontend and backend
• Google Calendar API integration
• Notification system architecture
• Real-time collaboration features
Data Flow Indicators
• → for synchronous requests
• ⇢ for asynchronous operations
• ⟲ for database operations
• ⟿ for external API calls
Deployment Architecture
A separate section showing:
• Docker containers
• Render hosting
• AWS services used
This system design should emphasize the collaborative nature of the application while showing how the different components interact to provide the core event planning functionality.