How inp-net/churros works
Main Components Architecture
Frontend (SvelteKit Application)
• Public Web Interface
• Admin Interface
Backend (GraphQL API)
• Authentication Service
• Core Services
• Integration Services
Infrastructure
• PostgreSQL Database
• Redis Cache
• File Storage
Key Services and Modules
Core Services
• Users & Authentication
• Groups & Organizations
• Events & Ticketing
• Document Management (La Frappe)
• Posts & Announcements
• Forms
• Notifications
Integration Services
• LDAP Integration
• Payment Processing
• Lydia
• PayPal
• Digital Wallets
• Apple Wallet
• Google Wallet
• External Services
Data Flow Relationships
Key interactions:
User Request Flow
• Client (SvelteKit) → API Gateway
• API Gateway → GraphQL API
• GraphQL API → Service Modules
• Service Modules → Database/Cache/Storage
Authentication Flow
• User Credentials → Auth Service
• Auth Service → LDAP Verification
• Token Generation → Client
Specific Implementation Details
Technical components:
Frontend Implementation
• SvelteKit Routes
• GraphQL Queries/Mutations
• PWA Capabilities
Backend Implementation
• Prisma ORM
• GraphQL Resolvers
• Module-based Architecture
Key Interactions to Highlight
• User authentication flow
• Event booking and ticket management
• Document sharing and management
• And organization hierarchy
• Notification system
• Payment processing flow
Deployment Infrastructure
• Kubernetes Clusters
• Database Instances
• Redis Cache
• Storage Solutions
Security Boundaries
Security zones:
Security Layers
• Public Zone (Frontend)
• API Gateway
• Application Zone
• Data Zone