How zenika/skillz works
Main Components
a. Frontend Layer:
• Next.js Web Application (main user interface)
• Key features: Profile management, Skills tracking, Certifications, Admin panels
• Authentication system (Auth0 integration)
b. Backend Services:
• Hasura GraphQL Engine (main API layer)
• PostgreSQL Database
• Slack Bot Service
• Achievement Service
c. External Services:
• Auth0 (authentication)
• Slack API
• Analytics Service (mentioned but separate)
Key Relationships to Highlight
a. Data Flow:
• User interactions through web app → GraphQL queries/mutations
• Hasura → PostgreSQL database operations
• Slack Bot → Hasura GraphQL interactions
• Achievement service → User achievements processing
b. Authentication Flow:
• Auth0 → Web Application
• JWT token validation → Hasura
Specific Architecture Elements
a. Database Structure:
• Main tables: Users, Skills, Categories, Certifications, Topics
• Views for aggregated data
• Relationships between entities
b. API Layer:
• GraphQL endpoints
• REST endpoints for specific services
• Hasura permissions and business rules
[Client Layer]
• ↓ ↑
[Authentication Layer]
• ↓ ↑
[API Gateway/Hasura]
• ↓ ↑
[Service Layer]
• ↓ ↑
[Database Layer]
Important Details
a. Infrastructure:
• Docker containers
• Development vs Production environments
• Migration system
b. Integration Points:
• Slack Bot integration
• Analytics service connection
• Auth0 authentication flow
Specific Implementation Notes
• Environment-specific configurations
• Monitoring and logging points
Remember to include the three main applications (Web App, Slack Bot, and Analytics) while showing how they interact through the shared Hasura/PostgreSQL backend. This will help developers understand both the overall system architecture and the specific components they need to work with.