React + TypeScript
What it does: Frontend framework and typed UI layer.
How we used it: Built receptionist, doctor, and admin dashboards with reusable components and strict data models.
Business benefit: Faster feature delivery, fewer UI regressions, and more predictable maintenance.
Node.js + NestJS
What it does: Backend API and domain orchestration layer.
How we used it: Implemented appointment lifecycle logic, patient records workflows, and secure role authorization guards.
Business benefit: Clean module boundaries and scalable service architecture as clinic count grows.
AWS RDS (PostgreSQL)
What it does: Primary transactional database.
How we used it: Stored appointments, patient profiles, treatment history, and structured compliance logs.
Business benefit: Reliable relational consistency for critical healthcare workflows.
Redis
What it does: In-memory data store and cache.
How we used it: Handled short-lived queue states, dashboard counters, and frequently requested schedule snapshots.
Business benefit: Reduced latency for high-frequency operations and better dashboard responsiveness.
Amazon S3
What it does: Secure object storage.
How we used it: Stored reports, attachments, and document artifacts with scoped access rules.
Business benefit: Durable file storage with controlled access and cost efficiency.
CloudWatch
What it does: Monitoring and operational logging.
How we used it: Captured error traces, job health, request anomalies, and API performance metrics.
Business benefit: Faster issue diagnosis and proactive platform reliability management.
SES
What it does: Email delivery service.
How we used it: Sent appointment reminders, prescription notifications, and operational alerts.
Business benefit: Consistent communication workflows with reliable deliverability.