How hopps-app/hopps works
Main System Components
The system consists of several microservices and components that should be represented as distinct blocks:
a. Frontend Layer:
• SPA (Single Page Application) built with React/TypeScript
• Mobile Application
• Keycloak Theme for authentication UI
b. Backend Services:
• Organization Service (app.hopps.org)
• Financial Service (app.hopps.fin)
• Document AI Service (app.hopps.az-document-ai)
• ZugFerd Service (app.hopps.zugferd)
c. Infrastructure Components:
• Keycloak for authentication
• PostgreSQL databases
• Kafka for event streaming
• MinIO for object storage
• Azure AI services integration
Component Relationships and Data Flow
• User interactions flow from Frontend → Backend Services
• Authentication flow through Keycloak
• Event-driven communication between services via Kafka
• Document processing flow:
Frontend → Financial Service → Document AI Service → Azure AI
• Data persistence flows to PostgreSQL databases
• File storage flows to MinIO
Key Architectural Patterns to Highlight
a. Microservices Architecture:
• Clear service boundaries
• Independent deployability
• Inter-service communication
b. Event-Driven Architecture:
• Kafka message flows between services
• Event processing patterns
c. Security Layer:
• Keycloak integration
• Service-to-service authentication
Deployment Architecture
Kubernetes deployment aspects:
• Container orchestration
• Helm charts structure
• Service discovery and routing
Additional Details
• API gateways
• Load balancers
• Monitoring components
• Scaling capabilities
• Environment-specific configurations
Remember to emphasize:
• The AI document processing pipeline
• The event-driven nature of the system
• The security architecture
• The scalability aspects
This will provide a clear understanding of how the system components interact while processing accounting documents and managing organizational data.