How panoratech/panora works
Main Components
The system consists of several key components that should be represented:
a) Frontend Layer:
• Dashboard Application (apps/webapp)
• Magic Link Application (apps/magic-link)
• Embedded Catalog (apps/embedded-catalog)
• Frontend SDK (apps/frontend-sdk)
b) Backend Layer (packages/api):
• Core Services (@core)
• Vertical-specific Services:
• CRM
• Ticketing
• Accounting
• File Storage
• Marketing Automation
• E-commerce
c) Database Layer:
• PostgreSQL (indicated by prisma schema)
d) Integration Layer:
• Multiple third-party service connectors
• Webhook handlers
• Authentication providers
Architecture Patterns to Highlight
a) Modular Architecture:
• Clear separation between different verticals (CRM, Ticketing, etc.)
• Shared core services
• Demonstrate the plugin-based connector system
b) Service Communication:
• API Gateway pattern for external requests
• Event-driven architecture for webhooks
• Queue-based processing for async operations
Specific Elements
[Frontend Applications]
• ↓ ↑
[API Gateway / Load Balancer]
• ↓ ↑
[Core Services]
• Authentication
• Webhook Management
• Connection Strategies
• Field Mapping
• Sync Services
• ↓ ↑
[Vertical-Specific Services]
• CRM
• Ticketing
• Accounting
• etc.
• ↓ ↑
[Integration Layer]
• Connector Registry
• Provider-specific Adapters
• Webhook Handlers
• ↓ ↑
[External Services]
Additional Details
Annotations for:
• Authentication flows
• Data transformation pipelines
• Webhook processing paths
• Sync mechanisms between services
Infrastructure Elements
Supporting infrastructure:
• Docker containers
• Queue system (indicated by processor files)
• Caching layer (if applicable)
• Load balancers