How undb-io/undb works
High-Level Architecture Components
a) Frontend Layer:
• SvelteKit-based web application (apps/frontend)
• Desktop application (apps/desktop) using Tauri
• UI components for different views (grid, calendar, kanban, gallery)
b) Backend Layer:
• Core backend service (apps/backend)
• GraphQL API
• RESTful OpenAPI endpoints
• Authentication/Authorization system
c) Database Layer:
• SQLite database
• Storage system for attachments
• Migration system (drizzle)
Core Service Components
a) Core Modules (packages/):
• Table management system
• Record management
• Form builder
• View system (grid, calendar, kanban, etc.)
• Formula engine
• Webhook system
• Audit system
• Authorization system
b) Supporting Services:
• Real-time updates system
• Template system
• Storage service
• Mail service
• Webhook service
Key Interactions
• Data flow between frontend and backend
• Authentication flow
• Real-time update patterns
• Storage operations
• External integrations (webhooks, email)
Detailed Component Breakdown
Create subsections for:
a) Table System:
• Schema management
• Field types
• Relations
• Views configuration
b) Record System:
• CRUD operations
• Filtering
• Sorting
• Aggregation
c) Authorization:
• User management
• Space management
• Role-based access control
• API tokens
Technical Implementation Details
Specific technologies:
• Bun runtime
• SvelteKit
• GraphQL
• SQLite
• Drizzle ORM
• Tauri (desktop)
Deployment Options
Different deployment scenarios:
• Single binary deployment
• Docker container deployment
• Cloud deployment
• Local development setup
Use the following visual elements:
Data flow patterns
This system design should reflect undb's capability to scale from a simple local deployment to a full cloud service while maintaining its core functionality and security features.