How pauliusmilmantas/colabfoldwebserver works
Main Components
a. API Service Layer:
• Subcomponents:
• App Controller
• Ticket Service
• RabbitMQ Service
• Bearer Guard (Authentication)
b. Message Queue:
• Bidirectional connections between API and Worker
c. Worker Service:
• Subcomponents:
• RabbitMQ Controller
• Results Logger Service
• Converters (BLAST Converter)
• Engine Services:
• DIAMOND Service
• SWIPE Service
• Download Service
d. Analysis Engines:
• Two sub-containers:
• DIAMOND Engine
• SWIPE Engine
Connection and Data Flow
• Client → API Service (REST requests)
• API Service → RabbitMQ (Job submission)
• RabbitMQ → Worker Service (Job consumption)
• Worker Service → Analysis Engines (Processing)
• Analysis Engines → Worker Service (Results)
• Worker Service → Results Logger (Storage)
Additional Elements
a. Configuration:
• .env files and configuration components
• Environment-specific settings
b. Infrastructure:
• Docker containers (shown by Dockerfile presence)
• Docker-compose orchestration
Notes
Important notes about:
• Scalability of workers
• Engine independence
• Configuration requirements
• Authentication flow