Infrastructure
Application Flow
Complete service flow diagram showing the CrelioHealth application architecture
Application Flow
This diagram illustrates the complete flow of requests through the CrelioHealth infrastructure, from the internet through the CDN, load balancer, and application tier to various backend services.
Architecture Diagram
Component Breakdown
Request Flow
- Internet → CDN - Incoming requests first hit the CDN for cached content
- CDN → Load Balancer - Non-cached requests route to the load balancer
- Load Balancer → Target Group - Traffic distributed across healthy application nodes
- Target Group → Application Tier - Requests reach auto-scaling application servers
Application Tier
- Django/Flask - Main web frameworks handling HTTP requests
- API Services - Python 2 and Python 3 API endpoints
- Static Assets - Served directly from application nodes
- Async Services - Producer/Consumer pattern for background jobs
Data Layer
| Service | Purpose |
|---|---|
| MySQL | Primary relational database |
| MongoDB | Document storage |
| Redis Queue | Async job queue |
| Elasticsearch | Search functionality (Density & Thor clusters) |
| S3 | Object storage |
External Services
- SNS/SES - AWS notification and email services
- Lambda - Serverless functions
- AI Services - Machine learning integrations
Integration Engine
- Mirth - Integration platform for healthcare data exchange
- HL7/JSON - Standard healthcare data formats
- External Apps - Third-party system integrations