Product engineeringFeaturesTranslations
Translations System Overview
Overview of the custom translation system, architecture, and implementation
👤 Aditya Patle (aditya.patle@creliohealth.in)📅 Updated: Mar 29, 2026📁 Services🏷️ translations🏷️ i18n🏷️ frontend🏷️ backend🏷️ aws🏷️ redis
Translations System Overview
Introduction
Translations play a critical role in ensuring that users across different regions can clearly understand and interact with the platform.
Third-party or browser-based translations often fail to provide accurate or context-aware results. To address this, we use a custom translation system that gives us full control over language rendering and phrasing.
Key Objectives
- Provide accurate and context-aware translations
- Support region-specific language variations
- Allow lab-specific customization
- Ensure high performance and scalability
Supported Modules
- LIMS
- Store
- Patient Portal
- Promotion
Each module supports:
- Default translations (region-based)
- Lab-specific overrides
How It Works
- Load default translations (region-based)
- Apply lab-specific overrides
- Merge both
- Serve to frontend
Storage Strategy
| Type | Storage |
|---|---|
| Default Translations | AWS S3 |
| Lab Overrides | S3 + DB |
| Cached Data | Redis |
Tech Stack
- Frontend: React + i18next
- Backend: Django (Python)
- Storage: AWS S3
- Cache: Redis
- Database: MySQL